Richard Newton Brown has built his career in Toronto around a single, unfashionable argument: a project is not finished when the deliverables ship, it is finished when the ending is handled properly. That argument, and the closing phase of project management it centers on, has become the clearest expression of how he works.
Picture the final week of a project: the deliverables are built, the milestones are checked off, and still the work does not feel finished. An invoice sits unpaid. Nobody can say for certain whether a stakeholder ever signed off on the last revision. The instinct, for many project managers, is to treat this stretch as a formality, a bit of housekeeping wedged between the real work and the next assignment.
For Richard Newton Brown, a project manager based in Toronto, Ontario, this stretch is the opposite of a formality. It is the part of the job that determines whether everything that came before it actually holds together. Within a field that spans initiation, planning, and execution, Brown has built his standing on the phase most people are eager to move past: closure.
The Last Chapter
Brown’s clearest way of explaining the idea rests on a comparison to reading. He describes project closure as the final chapter of a book: the point where every subplot needs to find its place and every loose thread needs to be gathered before the story can be called complete. Readers do not remember a novel for its opening pages alone, he points out. They remember whether the ending paid off everything that came before it. Projects, in his account, work the same way. It is a habit of mind, he suggests, that separates competent execution from work people actually remember.
That comparison carries a second implication Brown returns to often: time management. A story that rushes its final chapters leaves readers unsatisfied no matter how strong the earlier pages were, and a project mismanaged in its closing weeks leaves the same impression, regardless of how smoothly the middle stretch went. Pacing a project properly, in his account, means protecting time at the end rather than letting it evaporate under deadline pressure. Hurried oversights stacked on top of one another in a project’s final days are what turn competent work into a disappointing finish.
But Brown is careful to separate closure from mere tidiness. It is not only about tying off loose ends, in his telling. It is also the one sanctioned moment in a project’s life to pause and take stock of what a team accomplished. After weeks or months of planning, coordinating resources, and monitoring progress, closure is where the effort finally gets acknowledged rather than folded straight into the next deadline. Toronto, a city Brown describes as defined by diverse industries and fast moving businesses, is the setting he most often points to as proof that this kind of discipline can take root anywhere projects get built.
The Five Reasons Closure Matters
Brown organizes his thinking around five specific functions closure serves, functions he argues are frequently skipped or rushed through under deadline pressure.
- It ensures completion. A project with unresolved tasks, in his framing, is like a puzzle with missing pieces: technically assembled, but incomplete in a way that eventually causes problems downstream.
- It celebrates success. Brown compares finishing a project to crossing the finish line after a long race, an occasion meant to acknowledge effort rather than slide past unmarked into the next assignment.
- It hands over deliverables properly. He likens the handoff to giving a carefully chosen gift: the final output should match what the client actually envisioned, not merely what was contractually specified.
- It closes the financials. Every contract, payment, and outstanding cost gets reconciled, an exercise Brown compares to balancing a checkbook before walking away from it for good.
- It captures lessons learned. Every project, in his view, is a trove of information about what worked and what did not, and closure is the only phase built to extract that information deliberately.
Taken individually, none of these five is unusual advice. Taken together, and treated as mandatory rather than optional, they form what Brown considers the basis of a properly closed project, one that leaves nothing unresolved for the next assignment to inherit.
The Conductor’s Job
If closure has a specific shape, Brown argues, someone has to be responsible for imposing it, and that responsibility falls on the project manager. He compares the role, in this final phase, to an orchestra conductor: someone not playing any single instrument, but responsible for making sure every part resolves together into a coherent finale.
In practice, that means the project manager becomes a liaison first. Stakeholders need to leave the process feeling heard and satisfied, not simply informed after decisions have already been made. It is a small distinction, Brown argues, but one that shapes whether a client returns for the next project or quietly looks elsewhere. It means preparing documentation thorough enough to serve as a record of the project’s entire trajectory, not just its final outcome. It means leading a lessons-learned session that treats the exercise as genuine reflection rather than a box to check before moving on. And it means stepping into the role of mediator when disputes or misunderstandings surface late, since unresolved disagreements at the end of one project, in Brown’s assessment, tend to carry over and poison the start of the next.
None of these tasks is glamorous, and Brown does not pretend otherwise. He describes the project manager’s job at this stage as an unsung one, steering a project so it concludes on a high note even when nobody outside the immediate team notices the effort it took to get there.
Balancing the Books
Brown treats financial oversight as inseparable from the rest of closure, not a separate administrative chore tacked onto the end. Every project generates a trail of vendor contracts, payroll obligations, and miscellaneous costs, and clearing them, in his description, resembles tidying up after a large feast: satisfying in the moment, but only truly finished once every last dish has actually been washed and put away. Nothing about the process is complicated, in Brown’s telling; it simply requires the discipline to finish it rather than leave it for someone else.
The stakes, in his view, extend beyond bookkeeping. Transparent financial closure builds trust with stakeholders who want assurance that the numbers reflect reality, and it establishes a culture of accountability that carries forward into future projects. Left unresolved, sloppy financial closure tends to resurface later as disputes or difficult audits, undoing goodwill that took months to build in the first place.
For Brown, prudent financial management is not paperwork bolted onto the end of a project. It is what allows a project manager to catch potential pitfalls before they compound, and to confirm that resources were actually used the way they were meant to be used.
Richard Newton Brown’s Next Chapter
Brown’s broader argument is that project management, as a discipline, tends to overvalue its early and visible stages, initiation, planning, execution, while undervaluing the quieter discipline of finishing well. His own practice has been built on reversing that emphasis, treating the closing phase and its financial counterpart as the two pillars that determine whether a project’s success actually holds up once the team disperses and moves on to the next assignment.
As organizations increasingly run projects that stretch across departments, vendors, and timelines, that argument seems likely to gain relevance rather than lose it. Richard Newton Brown’s case, built around the discipline of closure and financial clarity, is that an ending is not an afterthought to be planned around. It is the part of the work most likely to determine what a project is actually remembered for, long after the deliverables themselves have been handed over. For Richard Newton Brown, that is less a prediction than a working principle, one he applies to every project that crosses his desk in Toronto.
