A smaller brief can make a bigger difference

Name the decision

A brief often arrives as a list of deliverables. A website, an identity and a campaign may all be necessary, but they do not explain the decision that the work must help someone make. We ask what a person should understand, feel or do differently when the project is complete.

Separate needs from assumptions

Some constraints are real: an event date, a production process or an accessibility requirement. Others are inherited assumptions about how a solution should look. Making that distinction early opens room for better ideas without ignoring the practical conditions.

Choose what success means

Clear success criteria help teams evaluate work without reducing design to personal preference. They can be qualitative as well as numerical. A new visitor understanding the offer or an internal team publishing independently are meaningful outcomes. The criteria should match the project rather than a generic dashboard.

Keep the brief alive

We return to the brief at every major review. If a new requirement changes the central problem, we discuss its effect on scope and timing openly. A concise brief is not a restriction on ambition. It is a shared reference point that makes ambitious work possible.