Stop Starting, Start Finishing

Sir Alex Ferguson told his players one thing in the dying minutes of a match:

“Get the next goal. Then the next. Then the next.”

He didn’t say “score the most valuable goal.” He didn’t say “prioritise the goal with the highest strategic alignment.” He said: get the next one.

This is why Man United were lethal in the final minutes. They weren’t paralysed by the scoreboard. They were trained to win the next moment.

Most delivery teams do the opposite.

The Start Order trap

Every team I’ve worked with has a Start Order — a prioritised list of what to begin next. They weigh the cost of delaying a start obsessively.

Almost none of them have a Finish Order. They never weigh the cost of delaying a finish.

Here’s the thing: an unfinished item delivers exactly zero value. Whether it’s 20% done or 95% done, the business gets nothing until it crosses the line.

And every unfinished item is:

• Consuming someone’s attention
• Creating a dependency for something else
• Taking up space in execution
• Rolling over into the next cycle, consuming more capacity

The cost of delaying a finish is almost always higher than the cost of delaying a start. Yet we keep starting more.

What this looks like in practice

I’ve seen it in every organisation I’ve worked in: ten things at 80%, nothing at 100%. A clogged execution pipeline. Rising pressure to start even more work because nothing seems to be shipping.

Bryan Finster nailed it: “It’s much better to finish 80% of the things we plan, than to have everything at 80%.”

The compounding effect is brutal. Unfinished items from this sprint become carryover in the next sprint, which consumes capacity, which means even more items stay unfinished. The cycle feeds itself.

One simple change

Before every standup, ask “what can we finish today?” before asking “what should we start?”

If someone finishes their item and others are blocked, the finish-first response is: go help unblock the blocked item, don’t start something new. Swarming on blockers to get close-to-done items over the line is more valuable than starting fresh work.

The instinct to “stay busy” by pulling new work is exactly the behaviour that creates the problem in the first place.

Why this connects to behaviours

This is a behavioural problem, not a process one. The teams that finish well share specific behaviours:

• They protect focus. When something is close to done, they resist the pull of new, shiny work.
• They swarm on blockers. If one person is stuck, others help rather than starting their own thing.
• They celebrate finishing, not starting. The energy in the room shifts when something crosses the line.

The teams that don’t finish share different behaviours: constant context switching, individual heroics over team coordination, and a culture that rewards being busy over being effective.

In The First Red, the coach Declan Maguire watches for exactly these signals — the behavioural patterns that tell you whether a team is set up to finish or set up to stall. The scoreboard hasn’t moved yet, but the behaviours have already written the result.

Does your team have a Finish Order?