Where the curator decides what the exhibition is about, the interpretation and exhibition developer decides how a visitor actually experiences that decision — the physical and narrative path through the gallery, the words on every label, the interactive that lets a ten-year-old understand a scientific process an academic paper would take pages to explain. The distinct contribution, and what separates this role cleanly from the curator's, is that the developer's expertise is in the visitor, not the collection: writing at the right reading level, testing whether a label actually communicates before it goes on the wall, and designing physical or digital interactions that make abstract or specialist knowledge graspable in the ninety seconds a typical visitor spends in front of any single case.
The daily texture is writing and testing, over and over: draft a label, read it aloud to a colleague who doesn't know the subject, watch how a test visitor actually moves through a mock-up gallery layout, and revise based on what genuinely confused them rather than what the writer assumed would be clear.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
The single hardest skill in this job is not writing well — it is writing *briefly* well, to a strict word count, for an audience standing up, tired, and reading a hundred other labels that day. Museum interpretation writing has real, well-studied constraints (visitors read a small fraction of gallery text on average), and a developer who cannot cut a beautifully researched paragraph down to forty words that still carry the meaning will produce work that looks good on a laptop and fails completely on the wall. The role also sits at genuine risk of being folded into a curator's or designer's job description at smaller, underfunded institutions rather than existing as its own post, which is part of the field's broader precarity.
There is no single dedicated degree; entrants arrive from museum studies, exhibition design, heritage interpretation postgraduate programmes, or from a writing/journalism/UX background that pivots into museums specifically. A portfolio of actual interpretive writing — label copy, exhibition text, a mock interpretive plan for a real or imagined collection — is the strongest hiring signal, alongside experience gained through internships, museum studentships, or volunteering in front-of-house or learning teams where the practical reality of visitor attention becomes obvious firsthand.
AI drafts a serviceable first-pass label; the hardest, most valuable part of the job — cutting it to forty words a real tired visitor will actually read — is a human feedback loop no deployed tool replicates, and post-backlash caution now demands more visible human review, not less.
AI becomes a standard first-draft and translation tool; the testing-and-cutting craft and ownership of final wall copy remain the career-defining, human skill.
People drawn to Interpretation & Exhibition Developerare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.