Project Planning · 3 min read
A better website starts with a clearer brief.
Published October 6, 2026
A website brief does not need to specify every page or technology. Its first job is to make the business problem clear enough that design and development can move in the same direction.
Start with the business need
Describe why the project matters now. Perhaps your services have changed, visitors struggle to find the right information, or your team cannot update the current site easily. Concrete problems are more useful than a general request for a modern design.
Write down what you want the new site to make possible. That gives the project a purpose that can guide decisions when several directions look equally attractive.
Know the people you are designing for
Identify the main audiences and the questions they bring. A prospective customer comparing suppliers needs different information from an existing customer looking for support. Decide which journeys matter most.
- Who is the primary visitor?
- What do they need to understand or evaluate?
- What should their next step be?
- What might prevent them from taking that step?
Bring the content into the conversation early
Collect your service descriptions, product information, brand materials, and relevant work examples. Mark what is ready, what needs revision, and who can approve it.
Content shapes navigation and page design. Knowing what you need to communicate helps the team choose an appropriate layout and avoid filling the site with sections that have no clear job.
Make the practical constraints visible
List the systems the site must connect to, the people who will maintain it, and any important dates. Separate essential launch requirements from improvements that could follow later.
A short brief with clear priorities is a strong starting point. The discovery stage can turn it into an agreed scope, design direction, and delivery plan.