At a glance
- State the need, the evidence and the limits before specifying a solution.
- Separate firm requirements from assumptions that the project should test.
- Revise the brief when research changes the understanding of the problem.
A project brief is a shared account of what a piece of work is meant to achieve. Its value lies in giving people enough clarity to move together, while keeping the unanswered questions visible. A brief can be precise about the purpose without deciding every detail of the solution in advance.
This matters whenever the person commissioning the work and the people carrying it out see different parts of the problem. One may know the budget, another the audience, and another the practical obstacles. The brief is where those perspectives begin to meet.
Begin with the need behind the request
The Design Council’s Double Diamond offers a useful reference. It describes a process of understanding a problem, defining it, exploring responses and testing solutions. In particular, its discovery stage encourages learning from the people affected before assuming the problem is already understood.
A brief benefits from that distinction. A request for a new website, a larger room or a shorter video may already contain a proposed answer. The underlying need might be easier access to information, a better way to use existing space, or a clearer explanation for a particular audience.
Those needs can lead to different decisions. Writing them down does not invalidate the initial request. It gives everyone a way to ask whether the proposed answer is serving the purpose.
Leave the hypothesis visible
Consider a hypothetical community cinema that wants to redesign its booking page. The first brief says that the page needs a modern appearance. That may be a worthwhile design goal, but it does not explain where the present experience falls short.
A more useful brief could identify the intended audience, the steps involved in booking and the questions visitors need answered before choosing a screening. It could also record the assumption that people struggle to find accessibility information. That assumption then becomes something to investigate, rather than something the team silently treats as fact.
The project might reveal a navigation problem, missing information or confusing language. It might also show that the original assumption was wrong. Either outcome is useful if the brief leaves room for the findings to influence the work.
The cinema is invented to illustrate the approach this essay describes; it is not an account of any real project.
Give constraints a clear place
Room for discovery still needs boundaries. A team should know the available budget, the intended delivery date, the people who will make decisions and any requirements that cannot be changed. Otherwise, an invitation to explore can become an invitation to work without an endpoint.
One practical structure is to separate the brief into three parts: what is known, what is required and what remains to be learned. A confirmed deadline belongs in the second part. A belief about audience behavior belongs in the third unless there is evidence behind it.
The distinction also makes disagreement easier to discuss. People can question an assumption without appearing to disregard a commitment. They can explain the cost of a requirement without losing sight of why it exists.
Make revision part of the work
The Design Council’s framework for innovation describes a process that can revisit earlier questions as learning develops. A brief can follow the same spirit. It should remain readable, dated and open to deliberate revision when the evidence changes.
Revision need not mean constant changes of direction. Keep a short record of what changed, why it changed and who agreed to it. That protects the project from both extremes: clinging to an early assumption and treating every new suggestion as a reason to start over.
A good brief gives the work a center of gravity. It allows people to explore, judge what they find and return to a purpose they can explain together.
Sources & further reading
These sources support the facts in this essay. The framing and the examples are the editorial team’s own.
- Design Council — The Double Diamond
Primary explanation of discovery, definition, development and delivery in the design process. Checked October 29, 2026.
- Design Council — Framework for Innovation
Context for revisiting questions and using learning throughout a project. Checked October 29, 2026.
From the editorial desk
Written by the Curt Dewitz Conversations Editorial Team. This essay is editorial commentary: it does not describe Curt’s own experiences, and its views should not be read as his.
Read our editorial approach