A good brief is a valuable thing. It reflects careful thinking, sets a direction and gives everyone a common starting point. But even the most thorough brief is a snapshot of what someone knows and needs at the time of writing. Projects evolve, and conversations have a way of revealing things that no document quite captures.
In our experience, some of the most useful information emerges not from the brief itself but from the dialogue that follows it. The right question, asked at the right moment, can open up a dimension of a project that changes how everything else is approached. This is what the discovery process adds to a good brief.
A brief tells you what, discovery tells you why
There’s a meaningful difference between a brief and a shared understanding. A brief describes what a project needs to do. A shared understanding tells you why it needs to do it, what problem it is really solving, and what success looks like for the people involved.
A client might come to us asking for a new website. But through discovery, what often emerges is a more specific challenge: visitors are dropping off before they reach the most important pages; the team responsible for updating content has lost confidence in the CMS and so the site has gone stale; a rebrand is underway and its digital outputs need work. A brief rarely surfaces any of that on its own. Good questions do.
The questions that matter most
Discovery sessions are conversations with a direction. Our job is to create the conditions where people feel comfortable being honest with stakeholders who may have not had this conversation together before.
The questions we find most useful tend to be the ones without obvious answers. Who is this website really for, and what are they uncertain about? What does your audience need to believe before they get in touch? If the site disappeared tomorrow, what would your customers miss most? When someone says ‘I’ve never thought about it that way’, or when a question brings a long-standing tension between teams to the surface, those are the moments where the real project begins.
Listening is a design skill
There is a difference between hearing what someone says and understanding what they mean. When a stakeholder says they want a website to ‘feel more professional’, that could mean a dozen different things. Without asking further, you risk designing for a word rather than a need.
We also understand the pressure to move quickly. But in our experience, projects that skip proper discovery do not move faster. They simply encounter their problems later in the process, at a point where they are more disruptive and more costly to resolve.
A note on tools
There is a growing conversation about how AI tools can support early project stages: summarising research, identifying patterns, drafting briefs. Some of this is genuinely useful. But there is a distinction between processing information and asking meaningful questions of the people behind it. The most valuable discovery moments – the pause before an honest answer, the comment that reframes everything – happen between people, not in data.
The brief is an invitation to start asking
A good brief gives us context, constraints and a direction of travel. But the projects we are most proud of have always been shaped by a willingness to engage, question, dig deeper, and make sure we are solving the right problem before we start designing the solution.
If you are thinking about a new project, we would love to have a conversation. You can get in touch with us here.