We plan our arrivals with great care and our departures with almost none. So we often leave in a way that quietly unwinds the good we came to do.
Watch how a program begins. A careful assessment, a detailed design, a budget broken down to the line, a timeline with milestones, a theory of how the work will change a situation. Months of thought go into the entry. Now watch how it ends. The grant runs out. The final report is written. The team moves to the next response. The handover, if there is one, is improvised in the last weeks, a scramble to pass things to a local partner or a public service that may or may not have the capacity or the funding to carry them. We design the entrance like architects and treat the exit like the end of a lease. And the people we served are left standing in whatever we left behind.
This is not a failure of care. Everyone wants the work to last beyond their presence. The gap is structural, and because the structure is shared, it is ours to rebuild together. Our funding is organized around the project, a defined period with a beginning and an end, and it pays for delivery during that period. It rarely pays for the long, unglamorous work of sustainable handover, because handover happens after the project that funded it has closed. So the exit falls into the same gap that the project cycle leaves everywhere: the moment that matters most is the moment no budget covers.
Why we are built to arrive and not to leave
The deeper issue is that we are rewarded for starting and rarely held to account for how we finish. A launch is visible, fundable, and easy to celebrate. An exit is quiet, costs money that the closing grant no longer holds, and produces no photograph. So our energy pools at the beginning. We can describe in detail how a program will start. We can rarely describe how it will end in a way that leaves something standing, because no one was funded or measured on that question.
There is a measurement blind spot too. We assess a program against what it delivered while it ran, not against what survived after we left. A water system built and handed over counts as a success on the day of handover. Whether it was still running a year later, whether anyone had the funds and the skills to maintain it, is rarely measured and almost never tied back to the original design. So we never learn that the way we exit determines whether the work was real or temporary. We close the file before the answer arrives.
Designing the exit from the start
The fix is to treat the departure as part of the design, planned and funded at the beginning rather than improvised at the end. A few moves make that concrete.
Design the exit on the day you design the entry. Build the handover into the original plan, naming who will carry the work, what they will need, and how they will be resourced, before the program starts rather than after it ends. A program that does not know how it will leave does not yet know how it should begin.
Fund the leaving, not only the doing. Make sustainable handover a resourced stage of the work, with its own budget and its own time, rather than a task squeezed into the final weeks of a grant that is already closing. Funders gain directly, because a handover that holds protects the entire investment that came before it.
Build the capacity to inherit from the first day. Where local actors or public services will carry the work, strengthen them throughout the program rather than turning to them at the end, so that on the day we leave they are ready rather than surprised. Handover is a process that takes the whole project, not an event at its close.
Measure what survived, not only what was delivered. Track whether the work was still standing and still useful after we left, and feed that back into how the next program is designed. What we measure after the exit is what teaches us how to exit well.
We assess a program by what it delivered while we were there, never by what survived after we left, so we never learn that the leaving was the test.
None of this asks us to stay forever, which would itself be a kind of failure. The aim of good work is to become unnecessary, to leave behind something that lasts without us. It asks only that we plan our leaving with the seriousness we bring to our arriving.
The test is simple and rarely applied. If a program falls apart soon after we go, then we did not finish the work, we merely paused it at our own convenience. Leaving well is part of doing the work well, and it is a discipline we can choose to build now, starting with the next program we design.