The most common cause of a disappointing website is not bad design. It is a structure decided in Figma. Layout came first, content and journey second, and by launch the whole thing quietly stopped answering the question it was built for.
Structure first is the opposite
Before any visual work, three documents exist on paper: a sitemap, a page-by-page purpose sheet and a decision map for the primary audience. None of them need to be pretty. All of them need to be true.
Sitemap
Every URL the site will have at launch, grouped into no more than five top-level sections. Anything more than five is not a sitemap, it is a filing cabinet, and users will not use it.
Page purpose sheet
One line per page describing who the page is for, the single question it answers, and the one action it invites. Pages that cannot pass this test are cut before they are ever designed.
Decision map
A short list of the questions the primary audience arrives with, in the order they ask them, matched to the page that answers each one. This is where most sites quietly break: the questions are answered, but not in the order the visitor actually asks them.
Structure work is unglamorous
It also removes most of the arguments that normally surface during design. Once the structure is agreed, design becomes an act of expression rather than an act of decision-making, and the project moves faster and quieter than anyone expects.
Take it into the brief
A practical checklist.
- A sitemap with no more than five top-level sections
- A one-line purpose statement for every page
- A decision map showing what the primary audience asks, and where each answer lives
- A written list of pages you are choosing not to build at launch
- One named owner for the site after launch
Continue the conversation
Have a related piece of work?
Bring the process, source material and constraints. We can discuss the right starting point.
Start your brief ↗