Most website briefs begin too far downstream. They list pages, competitors and visual references before agreeing on the behavior the experience is meant to create.
Understand what the visitor already knows, doubts and calls the problem.
Decide what must become clearer or more believable by the end of the visit.
Navigation, proof and motion should support the behavior — not lead it.
Understand the starting state.
What does the visitor already know? What are they skeptical about? What language do they use for the problem? These answers shape content far more than a generic page list.
The brief becomes stronger when it describes tension instead of just audience demographics: what is slowing the decision down, and what evidence could remove that friction?
A useful brief describes the change you want in the visitor, not just the pages you want on the website.
Define the confidence shift.
Strong websites move people from one state to another: confused to clear, interested to convinced, browsing to ready to talk. That shift becomes a useful test for every section.
This makes proof easier to place. Case studies, process, testimonials and pricing each earn a position because they answer a specific uncertainty.
Then choose the interface.
Once behavior is clear, navigation, proof, motion and CTA design stop being decoration. Each decision has a reason and can be evaluated against the same objective.
The result is usually a simpler brief and a more distinctive website because the team is solving a real communication problem instead of assembling familiar sections.