What risk means here
In a project, a risk is something that might go wrong, or might turn out differently than planned, and that would matter if it did. It is not the same as a problem, which has already happened. Managing risk means thinking about possible problems early enough to reduce their likelihood or soften their effects.
Exhibit projects are especially exposed because they combine several moving parts: collections and research, creative design, software, physical construction and a fixed opening date. A delay in any one tends to affect the others.
Common risks in exhibit media projects
The list below is general. Each project has its own.
Late or changing content
Text, images, audio and video often arrive later than planned, or change after being approved. Research may reveal a new fact, a rights holder may refuse permission, or a donor may ask for a change. Because software and layout depend on content, late changes can force rework. Content production and exhibit translation both take time that is easy to underestimate.
Hardware delays and shortages
Displays, computers and custom parts may arrive late, arrive faulty or be discontinued before the order is placed. Lead times vary, and suppliers can run short of stock. Ordering early and confirming delivery dates helps, as does choosing common, widely available equipment when possible.
Unclear scope and approvals
If it is not clear who approves content or design, decisions drift and requests expand. Without a written brief, people often assume different things. A steady flow of small additions, sometimes called scope creep, can consume budget and time without any single decision feeling large.
Key people becoming unavailable
A small team may depend on one developer, one curator or one technician. Illness, resignation or competing work can stall everything. This is particularly relevant for small museums and for projects that rely on volunteers.
Technical problems
Software may behave differently on the real hardware than on a developer’s laptop. Touch sensitivity, sound levels, lighting and network conditions in the gallery may cause issues that were not visible earlier. Problems with touch calibration and screen glare are classic examples that only show up on site.
Site and installation issues
Power may be in the wrong place, walls may not support a mount, or building work may overrun and block access. Installation windows can be short, leaving little time to fix mistakes.
Visitor and accessibility problems
An exhibit may be confusing, hard to reach or unusable for some visitors. Finding this at the end is costly. Early testing reduces this risk.
Funding and cost changes
Prices rise, grants arrive late, or a quote proves incomplete. Without contingency, small overruns become crises.
Ongoing operation
Even a successful launch can fail later if nobody is responsible for upkeep, or if parts and software age out of support. Planning for a maintenance plan and for technology obsolescence reduces this risk.
A simple method
Teams do not need heavy tools. A modest routine works for most projects.
- Identify. Early in the project, gather the team and brainstorm what could go wrong. Ask people from different roles, since the installer sees risks the curator does not.
- Rate. For each risk, estimate how likely it is and how serious it would be, using simple scales such as low, medium and high. These are judgments, not precise measurements, so avoid false precision.
- Decide a response. For each important risk, choose one of: reduce it (act now to make it less likely), prepare for it (have a plan if it occurs), transfer it (for example, through a contract or insurance), or accept it knowingly.
- Assign an owner. One named person watches each risk and raises a flag when it changes.
- Review regularly. Revisit the list at each milestone or monthly. New risks appear, and old ones fade.
Record this in a short table, often called a risk register, with columns for the risk, its likelihood, impact, response, owner and status.
Practical ways to reduce common risks
- For late content: agree a content deadline well before build completion, and use temporary stand-in text and images so design and testing can proceed. Build the interface so that text can be replaced without developer help.
- For hardware delays: order long-lead items first, choose supplier options with stock, and plan a fallback display or computer model that your software can also run on.
- For scope creep: keep a written brief, route requests through one decision-maker, and keep a list of “later” ideas rather than adding everything now.
- For single points of failure: make sure at least two people understand each critical component, and keep documentation up to date.
- For technical surprises: test on real hardware, in the real gallery, as early as possible. Visit the site before finalizing designs.
- For visitor problems: use paper prototypes and early prototype testing to find difficulties while they are still cheap to fix.
- For cost changes: include contingency in the exhibit budget and agree in advance who can approve its use.
Plan for the schedule
Risk and time are closely tied. A schedule with every task running back to back has no room for trouble. Building in buffer near the end, and avoiding unrealistic opening dates, is one of the most effective responses. The approach is described further in the discussion of the project schedule.
When things go wrong anyway
Some risks will materialize despite planning. When they do, communicate early. Tell stakeholders what has happened, what options exist and what each would cost in time and money. Decide whether to reduce scope, extend the schedule or add resources. It is often better to open a smaller, polished exhibit than to open a larger, unfinished one. After opening, note what happened and why, so the next project benefits from it.
A light touch
Risk management should be proportionate. A small touchscreen in a single gallery needs a one-page list, not a formal program. The aim is to prompt useful conversations early, not to produce paperwork.