Why a brief matters
An exhibit media project usually involves people who see the work from very different angles. A curator thinks about the story and the objects. A designer thinks about the visitor’s path and the screen. A developer thinks about what can be built and kept running. An operations manager thinks about cleaning, power and staffing. Without a shared written starting point, each of them fills the gaps with their own assumptions, and the differences tend to surface late, when they are expensive to fix.
A brief is that shared starting point. It is a short document, often a few pages, that says what the project is for, who it is for and what limits it must work within. It does not need to be elaborate. It needs to be specific enough that two people reading it independently would picture roughly the same project.
The core sections of a clear brief
There is no single required format, but most useful briefs cover the same ground.
Purpose and background
Start with a short paragraph on why the exhibit exists. What gallery, collection or story does it support? What prompted the project? This helps anyone joining later, including outside suppliers, understand the context without a long meeting.
Audience
Describe who the exhibit is mainly for. A general description such as “mixed-age visitors, many arriving in family groups” is more useful than “everyone”. If the audience includes groups with particular needs, such as young children or older adults, say so here, because those needs shape decisions about height, text size, pacing and input. Naming the audience also gives you something to test against later.
Goals
State what you hope visitors will do, understand or feel. Keep goals modest and observable where possible. “Visitors can explain, in their own words, how the object was made” is easier to check than “visitors will be inspired”. Writing goals in a form you can evaluate pays off later, when you plan evaluation goals and decide how success will be judged.
Content scope
List what content exists, what must still be created and who owns it. This is where many projects quietly go wrong: the brief assumes finished text and images, but the material is still being researched, translated or cleared for use. Be honest about the state of each item. If rights are unresolved, note it, since image permissions can take longer than expected.
Experience and format
Describe the kind of experience you imagine without locking in a technology too early. You might say “a single-visitor touch experience of about two minutes” or “a shared display that groups can use together”. If you already know you need a particular format, say why. Leaving room for the design process to propose options is often wise, especially at the earliest stage.
Space and physical constraints
Note the dimensions of the gallery area, ceiling height, available power and network, lighting conditions, nearby exhibits that make noise, and any conservation limits on what can be installed near collection objects. A brief that ignores the room invites a design that cannot be installed.
Accessibility and inclusion requirements
State the standards or commitments your institution follows, in general terms, and what you expect from the project. Raising this in the brief is far cheaper than retrofitting. A simple accessibility checklist attached to the brief gives suppliers and staff a common reference.
Budget and timeline
Give a realistic range or ceiling and the key dates, such as an opening date and any fixed events. Include what the budget must cover beyond the build, such as testing, documentation and ongoing upkeep. If the budget is not yet certain, say what is assumed.
Roles and decision making
Name who approves content, who approves design, and who has the final say when opinions differ. Unclear approval paths are a common source of delay. A short list of roles and a named point of contact for each is usually enough.
Operations and after opening
Say who will run and maintain the exhibit once it is open, and what skills and time they have. A brief written only for the build phase often produces something the museum cannot sustain. Mentioning upkeep early also prompts conversations about a maintenance plan and about records for later teams.
What to leave out
A brief is not a design. Avoid specifying screen layouts, colors or button positions unless there is a firm reason. It is also not a full technical specification; those details belong in later documents and, where outside suppliers are involved, in the requirements used during exhibit procurement. Keep the brief focused on needs and constraints rather than solutions.
Using the brief during the project
A brief is most valuable when people actually return to it. A few habits help.
- Share it widely at the start. Ask each stakeholder to read it and note anything they disagree with. Disagreements found in week one are cheap.
- Treat changes as decisions. When scope changes, update the brief and note the date and the reason. This keeps a trail and makes it easier to explain later why something was dropped.
- Check proposals against it. Whether the work comes from an internal designer or an outside team, compare ideas to the stated audience, goals and constraints.
- Test against it. When you run prototype testing, the audience and goals in the brief tell you who to recruit and what to look for.
A small illustration
Imagine a hypothetical local history gallery that wants a screen about a river crossing. A weak brief says, “We want an interactive about the bridge.” A clearer brief says the audience is mixed-age visitors including school groups, the goal is that visitors can describe two ways the crossing changed the town, the content is a set of archive photographs with cleared permissions and a short text still to be written, the space has one wall socket and no network, and the staff can spare one person for an hour a week to check it. The second version already rules out several approaches and points to a simple, low-maintenance design.
When the brief is short on answers
Sometimes you cannot answer every section at the start. That is normal. Mark open questions clearly, give each an owner and a date by which it must be settled, and treat unresolved items as risks. Early research, such as front end evaluation with likely visitors, can answer questions about audience and content before money is committed.
A good brief is revised, not frozen. Its purpose is to keep a group of capable people pointed in the same direction, and to give them a clear, written reference when memories and opinions differ.