We think discovery should reduce uncertainty, not postpone action.
One week. The right people. The decisions that actually matter.
Discovery should give a project direction, not become the project.
More discovery doesn't always mean more certainty
The instinct at the beginning of a project is understandable: learn everything. Interview everyone. Map every journey. Document every requirement. Remove as much uncertainty as possible before committing to a direction.
But there is a point where additional discovery stops producing better decisions. Questions become increasingly hypothetical, documentation grows faster than understanding, and decisions that could have been tested through actual work remain trapped in presentations.
Digital projects are especially resistant to certainty. Priorities change. Users behave differently from how teams expect. Ideas that sound convincing in a workshop can fall apart as soon as they become an interface. A longer discovery phase doesn't remove those realities — it just means you encounter some of them later.
Compress the conversation.
A focused week changes the nature of discovery. Instead of treating every possible question equally, we concentrate on the decisions that will materially shape the work: what we're trying to achieve, who we're trying to reach, what already exists, where the constraints are and what success should look like.
That means getting the right people involved early. Stakeholders don't need to spend weeks moving through a workshop programme. They need to bring the knowledge only they have, challenge assumptions and help us establish the boundaries within which the team can move quickly.
By the end of the week, we want a shared definition of the problem, clear priorities, an initial direction and enough confidence to begin making. The output isn't a giant discovery deck designed to prove discovery happened. It's a useful foundation for the work that follows.
Discovery doesn't stop when the week ends.
The biggest misconception about shorter discovery is that it means doing less thinking. It doesn't. It means moving some of that thinking closer to the decisions it informs.
Once strategy becomes creative, content becomes structure and requirements become working interfaces, new information appears. We can respond to something real rather than trying to anticipate every eventuality at the beginning of the project.
That makes discovery continuous rather than front-loaded. Strategy can sharpen as the work develops. Assumptions can be tested. Priorities can change when the evidence says they should. The initial week gives us direction without pretending the direction can never move.
Four weeks of discovery can absolutely be appropriate for a genuinely complex problem. One week isn't a rule for every engagement. It's our default because most projects benefit from momentum more than they benefit from another week discussing what might happen.