01
Start with the business change
“We need a new website” describes an output. It does not explain why the work matters now. A useful discovery starts by understanding what has changed: a new market, an outdated offer, weak lead quality, a manual booking process, or a business that has outgrown its current presentation.
The commercial goal should be concrete enough to guide trade-offs. More enquiries is not the same as better-qualified enquiries. More bookings is not useful if the team cannot fulfil them efficiently.
- What is happening in the business that makes this project important now?
- What should become easier, faster, or more credible after launch?
- Which result matters most if the project must prioritise one thing?
- What would make the project feel unsuccessful even if the website looks polished?
02
Understand the audience and its decision
An audience is more useful when described by its situation than by a broad demographic label. What brought this person here? What do they already know? What are they comparing? What risk are they trying to reduce?
The website should help that person move from uncertainty to a confident next action. That means identifying the questions that must be answered before an enquiry, quote, purchase, or booking feels reasonable.
- Who is the highest-value visitor and what triggered their search?
- What alternatives are they likely to compare?
- What concern could stop them from acting?
- What is the smallest useful next step for them?
03
Collect evidence, not adjectives
Words such as quality, reliable, innovative, and customer-focused are easy to claim and difficult to believe. Useful content replaces them with evidence: a specific process, visible expertise, real work, clear terms, operational detail, or a concrete difference in the customer experience.
This is also where content gaps become visible. A design cannot compensate for missing project examples, unclear service boundaries, poor product information, or photographs that do not support the promise.
- Which completed work can be shown and described honestly?
- What does your process make safer or clearer for the customer?
- Which practical details demonstrate expertise?
- What content already exists and who owns the missing material?
04
Expose operational and technical constraints early
The website rarely lives alone. Leads may need to reach a CRM, reservations may depend on availability and pricing, content may need several languages, and the existing domain may carry valuable search history. These realities shape the solution.
Budget and timing belong in the conversation because they affect scope and sequence. They should not be used to force an arbitrary package; they help identify the smallest coherent release and what can follow later.
- Which systems, people, or manual steps must connect to the website?
- What data is sensitive, regulated, or operationally critical?
- Which legacy URLs or content must be preserved?
- Who approves decisions and who maintains the result after launch?
Next step
A brief is a starting point, not a contract with your first idea.
Good discovery changes the shape of a project. A page you assumed was essential may disappear; a hidden operational dependency may become the priority. That is progress, not scope failure.
You do not need every answer before the first conversation. Bring what you know, mark what is uncertain, and let the work begin with the questions that have the greatest effect on the outcome.