The Starting Illusion
The pattern in which starting work creates the appearance of progress while reducing the organisation’s capacity to actually finish it.
IN ONE LINE
Starting something is not the same as making progress on it.
Three minutes.
What it is
A new piece of work arrives and everybody agrees it matters.
There isn’t really capacity for it, but saying that creates a difficult conversation. Something already underway would need to stop. A stakeholder would need to wait. Two priorities would need to be compared openly and one would have to lose.
So the organisation does something much easier.
It starts.
The work gets a name. Someone estimates it. Meetings begin. It appears on the roadmap. A project manager is assigned. Status reporting starts. The stakeholder can see movement and the immediate pressure subsides.
But the organisation hasn’t necessarily created the capacity required to deliver anything.
It has created another thing to manage.
That is the Starting Illusion.
Starting work can relieve pressure long before it creates value.
That relief matters because it helps explain why the pattern is so persistent. Saying we’ve started resolves today’s conversation. Saying we cannot start this unless something else stops creates one.
When that happens repeatedly, the started pile grows faster than the finished pile.
And starting isn’t free.
People attend planning sessions, estimate work, produce updates, manage dependencies, answer questions and keep stakeholders informed. Technical specialists who could be finishing existing work are pulled into conversations about work that may barely move for months.
Eventually, the organisation is consuming an increasing amount of its delivery capacity maintaining the appearance that everything is underway.
What creates it
Starting is easier than choosing. Genuine prioritisation means deciding not only what matters, but what matters more. Starting everything postpones that decision.
Stakeholder pressure. A stakeholder waiting for work wants evidence that something is happening. Starting provides it, even when meaningful progress remains a long way away.
Approval without subtraction. New initiatives are authorised without explicitly deciding what existing work will stop, slow down or move.
Progress is measured through activity. Roadmaps, milestones, kick-offs and status reports make commencement highly visible. The capacity consumed by work that barely progresses is much harder to see.
Consequences arrive later. The benefit of saying yes is immediate. The cost appears gradually, dispersed across delays, switching, meetings and unfinished work.
No single decision has to be unreasonable.
The illusion emerges from repeatedly making the individually reasonable choice to begin.
How to recognise it
There is much more work in progress than work being completed. The started pile keeps growing while the rate of completion barely changes.
Everything is underway. Ask whether an important initiative has started and the answer is almost always yes. Ask when it will finish and the answer becomes less certain.
Projects spend long periods technically alive but barely moving. They still have owners, meetings, reporting and plans, but little meaningful progress.
People doing the work spend significant time accounting for work they aren’t doing. Planning, estimation, governance and status management consume capacity that could otherwise be used for delivery.
New work is regularly added without anything explicitly leaving. The portfolio expands through addition rather than choice.
The organisation is permanently busy and permanently behind. There is no obvious lack of activity, yet completion consistently falls short of expectation.
A useful question is surprisingly difficult for organisations caught in this pattern to answer:
Of everything currently in flight, what are we actually going to finish?
If the answer is unclear, the problem may not be how quickly things are moving.
It may be how much has been allowed to start.
What it gets mistaken for
A prioritisation problem.
Prioritisation is certainly part of it, but that description misses something important.
The organisation often knows which things matter. The difficulty is accepting that importance does not create capacity.
Five initiatives can all be strategically important. That does not mean the organisation can progress all five effectively at the same time.
So the work gets prioritised on paper while remaining simultaneous in practice. Everything is important, everything has a sponsor, everything has a business case and everything has technically begun.
The result isn’t simply too many priorities.
It is too many promises being kept alive at once.
It can also look like a resource problem. More people may help in some circumstances, but additional resource does not automatically remove the coordination, governance, decision-making and switching costs created by a large amount of simultaneous work.
The started pile itself has become work.
Why it persists
Because starting creates a genuine sense of movement.
A kick-off happened. A team was formed. The board approved the programme. The roadmap exists. The status is green.
Those things are not imaginary. Work really has happened.
The illusion is believing that this activity is equivalent to movement towards the outcome.
Meanwhile, saying yes to starting has solved an immediate organisational problem. The stakeholder has been answered. The commitment has been acknowledged. Nobody has had to make the harder decision about what should give way.
The cost is deferred.
Eventually, that deferred cost appears as slow delivery, missed milestones, rising overhead and teams stretched across too many things.
By then, the organisation is under even greater pressure to demonstrate progress.
So it starts something else.
The starting is eating the finishing.
What becomes possible
The alternative isn’t an organisation reluctant to begin anything.
It is an organisation that treats starting as a commitment of capacity rather than a signal of intent.
That changes the conversation before work starts.
Do we have the people required to progress this meaningfully? Who needs to make decisions? What other work will compete with it? What happens to the things already underway? Are we genuinely committing to this, or simply making it visible?
Some initiatives may wait.
Others may move dramatically faster because the people working on them are no longer spreading their attention across a growing portfolio of nominally active work.
And completion starts to matter more than starting.
A shorter list of things genuinely moving can produce more progress than a long list of things officially underway.
Where to start
Don’t begin by reprioritising every initiative.
Start with the next request to begin something.
Before agreeing to start it, look at what is already underway and ask:
ASK THIS
If we start this now, what are we willing to finish later?
If the answer is nothing, make that visible.
Who will do the work? What will they stop doing while they do it? Which existing commitment will move? What additional overhead will starting create before meaningful delivery even begins?
The point isn’t to make starting difficult.
It is to make the choice real.
Because every new beginning consumes something, whether the organisation acknowledges the trade-off or not.
Don’t just decide what deserves to start.
Decide what deserves the capacity to finish.
Last updated October 2026
