Design Brief

A design brief turns a vague request such as “make our website look modern” into a shared decision framework. It typically identifies the problem to solve, intended users, business goals, brand constraints, required pages or assets, technical requirements, timeline, responsibilities, and approval process. A strong brief distinguishes essential constraints from optional stylistic preferences.

For a local repair business, the brief might prioritize clear mobile call actions, an easy estimate form, readable service pages, and a design that can be maintained by a small team. It should document which existing content and brand materials are available, who signs off on wireframes, and how accessibility will be evaluated. Referencing competitor sites can clarify preferences, but copying a competitor's layout is not a proper goal.

The brief should guide discovery and revisions rather than pretending that every detail is fixed before research. If the team finds that users cannot understand the quote process, the brief may need an approved update. Record scope changes so timing and cost implications are visible. A design brief differs from a content brief, which usually directs a particular article or asset, and from a formal statement of work, which governs commercial commitments. All three can support one project without being interchangeable.