The reality of small teams
Many exhibits are made by a handful of people: a part-time curator, a manager who also handles finance, a few volunteers and perhaps an occasional contractor. Skills vary widely, availability is uneven and people may come and go. This is a normal way of working for community museums, local history groups and many cultural organizations, and it can produce excellent work, provided plans match capacity.
The central challenge is not enthusiasm but continuity. A project that relies on one keen volunteer’s evenings can stall when that person is unavailable. The suggestions below aim to reduce that fragility.
Scope to what you can sustain
Start with an honest account of who can do what and for how many hours a week. Then choose a project that fits. A single, well-finished screen or audio point is often better than a sprawling plan that is half-complete.
Useful ways to keep scope manageable:
- Choose simple formats. Slide-style presentations, audio guides, short videos and straightforward touch screens generally need less specialist work than sensors or custom hardware.
- Reuse before creating. Existing photographs, recordings and text may be adapted, provided rights are clear.
- Plan in stages. Open a small first version, then add content later. Build the exhibit so that new material can be added without rebuilding.
- Limit languages and variants at launch, while designing so more can follow. Good exhibit translation takes time, so choose carefully.
Many small museums report that clear, modest goals make the difference. The broader benefits and constraints for them are discussed in writing about small museums.
Match tasks to people
Rather than asking who is available, ask what each task needs and who enjoys or is able to do it. Common tasks include:
- researching and writing text;
- scanning documents and photographing objects;
- recording oral histories;
- editing audio or video;
- testing the exhibit with friends, family or visitors;
- cleaning and checking equipment each week;
- keeping records and organizing files.
Break tasks into pieces that can be done in a few hours, with clear instructions and an expected result. Short, bounded jobs suit volunteers who can give irregular time. Larger responsibilities, such as technical decisions, are better assigned to someone with an ongoing commitment, or to a paid contractor.
Be careful not to treat volunteers as free labor for tasks that require professional accountability, such as legal clearance or safety checks. Know where specialist help is needed.
Support volunteers well
People stay and do good work when they feel clear and valued.
- Give a written role description with purpose, tasks, time expected and who to ask for help.
- Offer short training. A one-hour session on how to photograph objects, record audio or follow your style guide saves many hours of redoing work. Practical guidance on object photography and oral histories is a helpful starting point.
- Provide templates and checklists. A text template, a file-naming rule and a simple checklist reduce variability in quality.
- Pair people. Two volunteers working together, or a volunteer with a staff member, spread knowledge and cover absences.
- Give feedback and thanks. Acknowledge contributions publicly where people wish it, and respect those who prefer not to be named.
- Respect boundaries. Do not push people into tasks they are uncomfortable with, and be clear about expected commitment so that people can say no.
Keep decisions and records simple
Small teams benefit from lightweight structure.
- One decision-maker per area. Decide who has the final word on text, on design and on spending.
- A shared place for files. Use a single, backed-up location with clear folder names. Avoid important material sitting only on personal devices.
- A short decision log. A page noting what was decided, when and why helps people who join later.
- Regular, short check-ins. A thirty-minute meeting every couple of weeks, in person or online, keeps tasks visible.
A brief that sets out audience, goals and limits is particularly helpful when many hands are involved, since it provides one reference for everyone.
Choose technology that suits your skills
Pick tools your team can learn and maintain. Descriptions of exhibit tools may help you consider the options, but avoid anything that only one person understands. Prefer common hardware that can be replaced easily, and keep the setup as plain as is reasonable. If a contractor builds part of the work, ask for training and documentation as part of the agreement. Guidance on media players explains why standard, replaceable equipment is often a wise choice for teams with limited technical support.
Plan for turnover and absence
Because people may leave, make knowledge portable. Write down procedures, keep source files in the shared location and ensure at least two people know how to start, restart and update the exhibit. The ideas in documentation and handover apply just as much to a volunteer-run project as to a large institution, perhaps more so. Build a short maintenance plan with weekly checks that a volunteer can carry out using a written guide.
Protect people from burnout
Enthusiastic individuals often take on too much. Watch workloads, share tasks and be prepared to say that something will wait. A realistic project schedule with buffer helps, and it is better to announce a later opening than to exhaust the team.
Know when to seek outside help
Some tasks justify paying for expertise: accessibility review, structural or electrical work, complex software and legal advice on rights. A small, well-targeted contribution from a specialist can protect the whole project. Seek advice on grants and shared services, or consider partnering with a local school, library or university, while being clear about each partner’s expectations and what they will deliver. Where outside suppliers are involved, the principles of procurement in proportion to the size of the project still apply.
Celebrate and learn
When the exhibit opens, thank everyone, and gather the team to talk about what worked and what did not. These notes will make the next project smoother, and they build the shared experience that helps a small team keep growing in capability.