Why I Still Slow Projects Down at the Start
Discovery is simply a structured pause
January always makes people want to get moving.
New plans. New initiatives. Lots of energy to get things going.
There’s a sense that progress equals motion and that standing still, even briefly, is somehow risky.
After nearly four decades working around learning, technology, and change, I’ve learned something that still feels slightly counter-intuitive.
Most projects don’t struggle because people make bad decisions. They struggle because everyone moves too quickly before the problem is properly understood.
That rush is rarely careless. It usually comes from good intent. People want to be helpful. Decisive. Seen to be doing something.
That’s why I still put so much emphasis on discovery.
For me, discovery is simply a structured pause. A moment to step back, listen carefully, and make sense of what’s really going on before anyone starts building solutions.
It isn’t flashy. It doesn’t produce instant deliverables. And it can feel uncomfortable, because it exposes uncertainty that was previously hidden.
Why discomfort is useful
It shows where assumptions have been doing the work of evidence. It reveals where people are using the same words but meaning different things. And it creates space for quieter concerns to surface before they turn into bigger problems.
What usually comes out of good discovery isn’t anything dramatic or clever.
It’s clarity.
Clarity about what problem is actually being solved. Clarity about where people agree and where they quietly don’t. Clarity about risks that everyone sensed, but hadn’t quite named. Clarity about what not to do.
That last one is often the most valuable.
Sometimes that clarity leads directly to a learning solution. Sometimes it reveals that training isn’t the issue at all.
Either way, it saves time, money, and frustration later.
I’ve lost count of how many times I’ve heard someone say at the end of a project:
‘I wish we’d done this earlier.’
What they usually mean is not that the work was wrong, but that the thinking came too late.
The fastest route overall
Slowing down at the start is often the fastest route overall.
If you’re starting something new, or trying to fix something that’s never quite landed, it’s worth asking a simple question:
Have we really understood the problem yet?