The Project Brief That Fits on One Page
A one-page project brief clarifies purpose, audience, limits and the next decision, helping a small creative project begin with a workable direction.
A one-page project brief can stop a promising idea from turning into a list of unrelated tasks. Before you buy materials, invite collaborators or open a design app, use a short written brief to clarify what the project is for, who it serves, what limits it must respect and what decision comes next.
The page is not a miniature project plan. It is a shared reference for making early choices. The right version depends on what is uncertain: purpose, audience, scope, collaboration or permission to begin.
What should a one-page project brief contain?
Keep the brief small enough to read at a glance, but specific enough to guide a choice. These headings provide a useful starting structure:
- Purpose: What change, experience or understanding should the project create?
- Audience: Who is it for, and what do they need from it?
- Result: What will exist when the project is ready to share?
- Limits: What boundaries shape the work, such as available time, space, materials, access or permissions?
- Open question: What must be decided before the next piece of work can begin?
Use plain language rather than polished slogans. “Make a display that helps visitors understand how these objects were repaired” gives more direction than “celebrate making”. A brief can include unknowns, too. Mark a point as undecided instead of filling the page with guesses.
Limits should guide choices, not merely document inconveniences. A display intended for a narrow hallway has different needs from one designed for a table in a community room. Name the relevant conditions, then use them to judge possible formats.
Which situation describes your project?
Is the idea exciting but hard to explain?
Begin with purpose and result. Write one sentence about what the project should help someone do, notice or understand, then name the thing you intend to make. If the two sentences do not connect, narrow the idea before planning tasks.
Are several audiences possible?
Choose the primary audience for this version of the project and describe what they already know. A project can reach other people later, but trying to serve everyone at once often makes its language and format vague. Note secondary audiences only if they change a real decision.
Are the limits shaping the project?
Give constraints their own short section when space, access, materials or permissions affect what is feasible. Separate fixed boundaries from preferences: a required venue rule is different from a hoped-for colour scheme. That distinction keeps negotiable choices from being mistaken for barriers.
Will other people make decisions with you?
Include collaborators’ roles and the choices they can make. A brief for a shared project should clarify who decides the purpose, who handles particular work and how unresolved questions will be settled. This prevents a simple task from becoming an unclear chain of approvals.
How much detail belongs on the page?
Include information that changes what you would do next. Leave out background that does not affect the audience, format, limits or decision. A compact brief is useful because its omissions are deliberate, not because every project has only a few moving parts.
Say you want to create a set of illustrated cards for a local reading group. The initial idea is to make cards about books, but the audience and use are unclear. You write that the cards should help new members start conversations, that they will be used at meetings, and that the group needs to choose between discussion prompts and book recommendations. The next decision is now visible: ask the organisers which use would better support a first meeting. The brief has not designed the cards; it has identified what to learn before doing so.
Keep supporting material elsewhere. A mood board, reference images, detailed schedule or list of suppliers can help once the direction is clearer, but putting them all on the brief makes the central choice harder to find. If a link or small sketch explains a point quickly, include it only when it earns its space.
How can you tell whether the brief is clear?
Read it as someone who has not heard the original pitch. Can they tell who the project is for, what it will produce and which limits matter? Can they identify the next decision without asking you to translate a phrase such as “make it engaging”?
Replace broad adjectives with observable intentions. “Welcoming” might mean that a first-time visitor can understand where to begin; “simple” might mean that a participant can use the object without a demonstration. The brief need not specify every design detail, but it should make the desired experience discussable.
Check that the proposed result matches the purpose. If the purpose is to invite conversation, a finished object that can only be viewed from a distance may not fit. This is a useful moment to revise the format rather than carry a mismatch into production.
What should happen after the brief is written?
Use the open question to choose a modest next action. That might be asking a prospective audience member to clarify a need, checking a venue’s requirements, or deciding who has authority over a shared choice. The action should answer the question, not create activity for its own sake.
Revise the brief when a meaningful decision changes the project. Do not polish it after every small adjustment; a living document is helpful only if people can tell which version reflects the current direction. For a collaborative project, agree where the shared copy lives and who updates it.
A one-page project brief works best when it gives the next decision a clear home. Keep the purpose, audience, limits and result visible, then let later plans carry the detail they actually need. If an important choice still has no owner or answer, the page has done useful work: it has shown where the project should pause and what to resolve before it grows.
