A website brief can look complete while leaving the important decisions open. “Modern design, better leads, easy to update” describes hopes. It does not tell a designer which customers matter most, what the business can support, or what must wait.
Before approving a brief for a new site or redesign, look for these planning gaps. Settle the decisions you can and make the remaining unknowns visible.
Mistake 1: agreeing on an appearance without a business purpose
Explain why the project is happening now. Perhaps the current website describes services you no longer offer, or prospects cannot tell which kind of work you take on. Name the business problem the project should address.
Choose a primary audience and a useful next step for that audience. If you serve several groups, explain where their needs differ rather than assuming one page can give every message equal weight.
If the team is guessing about customer needs, use our customer-task discovery guide before turning those guesses into requirements.
Mistake 2: hiding the trade-offs
Budget, timing, content readiness, and business capacity place limits on a project. Put those limits in the discussion early. A designer cannot make a sensible recommendation around a constraint they have not been told about.
For example, a fictional business may want to announce a new service at a trade event, but the service details are not yet approved. The team needs to decide whether to launch the confirmed core site first, adjust the date, or complete those decisions before proceeding. A polished placeholder does not resolve the missing information.
Record what may change and what cannot. If feature choices are the main issue, use the separate guide to deciding which website features to build first.
Mistake 3: assuming the business can fulfill every website promise
Consider what happens after someone takes the proposed next step. Can the business offer the appointment, assess the job, or provide the information the page promises?
A fictional repair company might want visitors to “book a repair” even though each job needs an initial assessment. Before design begins, decide whether the website should invite an assessment request instead. The wording and process should reflect how the service actually works.
This is a business decision to resolve in the brief, not something to leave for a designer to infer from a button label.
Mistake 4: treating an unknown as an approved requirement
Separate confirmed decisions, assumptions to check, and open questions. A requirement such as “connect the booking system” needs more detail if nobody has confirmed which system, whether it supports the needed connection, or who can provide access.
For each open question, note what it affects, who will investigate, and when the answer is needed. If the answer could change the structure or scope, resolve it before approving dependent work. For detailed role boundaries, see working with a website designer.
End with a decision-ready brief
Read the brief back as a set of decisions: why the project exists, who it serves, what the next step means, which limits apply, and which questions remain open. Include the trade-offs the team has accepted so they are not rediscovered halfway through design.
Preparing the actual copy, images, and business information is a separate task. Our website content checklist covers that handoff.
Bring the decisions and unresolved questions to a conversation about Imbark’s custom web design. An honest brief gives the project a firmer starting point than a confident list of assumptions.
