A redesign is easier to direct when the business questions are answered before visual exploration begins. The goal is not to write a perfect brief; it is to give the project enough commercial and operational context to make good decisions early.

Bring the business context into the room

• Name the audiences the site must serve and the questions each audience needs answered before taking action.
• Map the services, offers, locations, or capabilities that need a clear place in the information architecture.
• Collect the proof that can be published: approved outcomes, credentials, project examples, team expertise, and client permissions.
• Identify the systems the website must connect to, including CMS ownership, forms, analytics, booking, locations, or customer workflows.
• Define the decision process: the people who approve scope, content, design, release readiness, and launch timing.

Use the preparation work to reduce ambiguity

A website can only represent what the team has decided to communicate. When audiences, proof, content ownership, and approvals are unresolved, the project carries those decisions into design and engineering. Addressing them first creates a more useful brief and a more dependable route to launch.

A useful first question

Ask: what must be clearer, easier, or more trustworthy for the people we most need to serve? The answer becomes a better foundation than a request to make the site look more modern.