Some of the most important goals in football history have been scored in injury time — those few added minutes at the end of a match when everyone is exhausted, the result seems settled, and concentration is hardest to hold. Whole tournaments have turned on what happened after the ninety minutes were technically up. There is a reason commentators talk about the last ten minutes as a different kind of test: not of skill, which was established long before, but of concentration, fitness and will when both teams are running on empty. And I have come to believe that the last ten per cent of a project is exactly this — a distinct and decisive phase, governed by different rules from everything that came before, and the place where a great deal of delivery is quietly won or lost.
The middle of a project gets all the attention. That is where the bulk of the work is, where the energy is high, where the visible progress happens. But the end is where projects most often fail to finish properly, because the end has a character all its own, and almost nobody plans for it. The last stretch is not just more of the middle. It is a different phase, and treating it like the middle is one of the most common and costly mistakes in delivery.
The last ten per cent is not like the first ninety
There is a grim joke in software that the first ninety per cent of a project takes the first ninety per cent of the time, and the last ten per cent takes the other ninety per cent. It is a joke because it is true. The final stretch of a project — the integration, the testing, the fixing of the things that only show up when everything comes together, the thousand small details that were deferred as trivial — routinely takes far longer than anyone budgeted, because the work that remains is qualitatively different from the work that came before.
The reason is that the easy, parallelisable, well-understood work tends to get done first, and what remains at the end is the hard, interdependent, fiddly residue — the problems that were left precisely because they were difficult, the integration that cannot be done until the pieces exist, the issues that only emerge under real conditions. The last ten per cent is where the deferred difficulty all comes due at once. Injury time is when the legs are heaviest and the margin for error is smallest, and the project endgame is exactly the same: the moment of greatest fatigue and the moment the hardest remaining problems must be solved. Budgeting for it as though it were just the tail of the easy work is how projects that were on track for months suddenly run badly over at the very end.
Concentration fails exactly when it matters most
The goals conceded in injury time are very often goals of concentration, not ability. A team that has defended well for ninety minutes switches off for ten seconds, and the work of the whole match is undone. The skill was never the problem; the lapse was. And the lapse comes precisely because the end feels close, the result feels settled, and the mind relaxes a fraction too early.
Projects lose their injury-time goals the same way, and it is painful to watch because it is so avoidable. The team that delivered superbly for months relaxes as the finish comes into view. The attention to detail that characterised the whole project slips in the final stretch, exactly when the work is most delicate and the cost of an error is highest. The launch that goes wrong because the last checks were rushed. The handover that fails because everyone had mentally already finished. The quality that held all the way through and then dropped at the very end, undoing some of what the whole effort built. The hardest discipline in the endgame is to hold concentration when every instinct is telling you it is nearly over. The match is not over until it is over, and neither is the project.
Finishing requires a different kind of energy
There is a particular fatigue to the end of a long effort that is not the same as ordinary tiredness. The team has been going for a long time, the excitement of the start is long gone, the end is visible but not yet reached, and there is a strong pull to coast in on the assumption that the hard part is behind you. This is the most dangerous moment, because the hard part is often ahead, and the energy required to finish well is a different and scarcer kind of energy than the energy that carried the middle.
The good manager understands that finishing is its own act requiring its own reserves, and they manage the team’s energy accordingly — not spending everything in the middle, keeping something back for the closing stretch, recognising that the run-in demands a deliberate second effort rather than a gentle coast. The leader who has driven the team flat out for months and has nothing left to ask for the finish has mismanaged the energy of the whole campaign. The finish is foreseeable. It comes at the end, every time. Planning for it means arriving at the last ten per cent with something still in reserve, and asking for the deliberate final push that the endgame, uniquely, requires. Coasting in is how good projects finish badly.
The finish is what people remember
There is a final reason the endgame matters out of all proportion to its size, and it is about memory. A match remembered for a last-minute winner is remembered as a triumph, whatever happened in the dull first hour. A project remembered for a botched launch is remembered as a failure, however well the middle went. The end disproportionately shapes how the whole thing is judged, because the end is what people carry away. The last impression overwrites a great deal of what came before.
This is not entirely fair, but it is entirely real, and a wise leader plans for it. The quality of the finish — the smoothness of the launch, the cleanness of the handover, the care taken with the final details — will colour how the whole project is remembered far more than its proportion of the work would justify. It is worth protecting the endgame for this reason alone: not only because the hard work concentrates there, but because the finish is the part that lasts in people’s minds. Pour your remaining care into the last ten per cent, because that is the ten per cent everyone will remember.
What to take into your own finishing
The endgame is a distinct phase that deserves distinct treatment. A few things to carry across:
Budget the last ten per cent as its own hard phase. The deferred difficulty comes due at the end. It is not the tail of the easy work; it is the concentration of the hard.
Hold concentration when it feels nearly over. The injury-time goal is a lapse, not a lack of skill. The cost of a slip is highest exactly when the mind most wants to relax.
Keep energy in reserve for the finish. Do not spend everything in the middle. Finishing well requires a deliberate second effort, and you have to arrive with the means to make it.
Protect the finish because it is what people remember. The last impression overwrites much of what came before, fairly or not.
The match is not over when the ninety minutes are up, and the project is not over when the bulk of the work is done. What happens in the final stretch — the concentration held or lost, the energy reserved or spent, the care taken or skipped — decides a remarkable amount of the result, and almost all of how that result is remembered. Treat the last ten per cent as the distinct and decisive phase it is, and finish the way the best teams do: still concentrating, still organised, still with something left, right up to the final whistle.
This piece sits alongside Momentum: Why Projects, Like Matches, Are Won in Phases and How World Cup Organisers Manage Fixed Deadlines.
Ben Webb is a Sydney-based project leader and former Australian Project Manager of the Year, sharing practical lessons from major projects, events and complex stakeholder environments.
Leave a Reply