Rehearsal Is Not Performance
metaphor
Source: Theatrical Directing → Learning and Development, Software Engineering
Categories: arts-and-culturesoftware-engineering
Transfers
In theatrical directing, rehearsal and performance are categorically different activities, not points on a quality spectrum. Rehearsal is where the director and actors explore, experiment, fail, try again, and discover what the scene needs. Performance is where they execute what they have discovered. A director who treats rehearsal like performance — demanding polish before understanding, punishing wrong choices, insisting on a single right answer — destroys the exploratory process that rehearsal exists to serve. The distinction is not about readiness; it is about the mode of work.
Key structural parallels:
-
Different modes, not different grades — rehearsal is not a rough draft of performance. It is a different activity with different rules. In rehearsal, an actor might try playing a scene five different ways, each one “wrong” in the sense that it will not appear in the final production, but each one useful for discovering what the scene requires. When this transfers to software, it frames staging environments, prototypes, and spikes as spaces with their own integrity. A staging deployment is not a defective production deployment; it is a different kind of deployment with different purposes and different rules about what constitutes failure.
-
Safety enables discovery — the rehearsal room works because actors know that mistakes will not reach an audience. This safety is structural, not merely psychological: the doors are closed, no tickets are sold, no reviews are written. The director’s job is to protect this space. When this transfers to organizations, it argues that psychological safety is not enough — you need structural safety: environments where failure literally cannot reach production. Feature flags, staging environments, canary deployments, and blameless postmortems are all structural rehearsal-room mechanisms.
-
The transition must be deliberate — opening night is a specific event. The company does not gradually drift from rehearsal into performance. There is a dress rehearsal, a final notes session, and then the curtain goes up. The metaphor argues that the transition from exploration to execution should be a conscious, marked event — not a gradual blurring. In software, this maps onto the distinction between “we’re still experimenting” and “this is the design we’re committing to.” Teams that never make this transition explicitly end up in permanent rehearsal; teams that never rehearse end up performing without preparation.
-
The director’s role changes — in rehearsal, the director asks questions, suggests experiments, and creates conditions for discovery. In performance, the director is absent — the actors own the stage. This transfers to management: the leader who is useful during the exploratory phase (asking “what if?”, protecting the team from external pressure, encouraging divergent approaches) may need to step back during execution and let the team perform. The metaphor names this role shift as a structural feature of the process, not a personal failing.
Limits
-
Theater has opening night; software has continuous deployment — the theatrical metaphor assumes a hard boundary between rehearsal and performance, enforced by a date on a calendar. Modern software development often operates in continuous deployment where changes flow to production constantly. The clean binary breaks down: every commit is simultaneously a rehearsal for the next one and a performance for the current users. The metaphor provides no framework for this continuous mode.
-
Theatrical rehearsal is genuinely private; organizational rehearsal rarely is — when actors make mistakes in rehearsal, no audience sees them. When a startup runs a beta test, a government agency launches a pilot program, or a company soft-launches a product, real users interact with the rehearsal. Their experience, even if labeled “beta,” is real. The theatrical metaphor overstates the privacy of organizational exploration.
-
The metaphor can excuse under-preparation — “it’s just rehearsal” can become a license for sloppy work. In theater, rehearsal has discipline and standards; actors learn lines, show up on time, and commit fully to each run-through. The metaphor can be misused to justify low-effort exploration that produces nothing useful — messing around rather than rehearsing.
-
Not everything benefits from rehearsal — some activities are better learned by doing them for real at low stakes than by simulating them. A street musician does not rehearse; they perform at low stakes and improve through real performance. The theatrical metaphor assumes that a separate rehearsal space is always beneficial, but for some activities, the overhead of maintaining the separation exceeds its value.
Expressions
- “Staging environment” — the software industry’s primary structural rehearsal room, a non-production space for testing changes
- “This is just a rehearsal” — invoking the permission-to-fail principle, sometimes legitimately, sometimes as an excuse
- “Dress rehearsal” — the final practice run under performance conditions, mapping onto pre-production review or UAT
- “Opening night” — the transition to production, launch day, go-live
- “We’re still in rehearsal mode” — signaling that the team is in exploration, not execution, and that critique should be constructive rather than evaluative
- “Blameless postmortem” — a rehearsal-room principle applied retroactively: treating production failures as learning events rather than performances to be judged
Origin Story
The principle that rehearsal requires a different psychology than performance is a foundational tenet of modern directing, articulated by practitioners from Stanislavski through Peter Brook to contemporary directors like Frank Hauser and Russell Reich. Hauser’s Notes on Directing (2003) emphasizes that the director’s primary job is to create conditions for discovery, not to dictate results — and that this requires protecting the rehearsal room from the pressures of performance.
The metaphor transferred into software engineering through the concept of staging environments (formalized in the 1990s), into organizational psychology through Amy Edmondson’s work on psychological safety (1999), and into Lean/Agile methodology through the practice of spikes and prototypes. In each case, the transfer carries the theatrical insight that exploration and execution are different activities requiring different conditions, and that confusing them degrades both.
References
- Hauser, F. and Reich, R. Notes on Directing (2003) — the rehearsal-performance distinction as a directing principle
- Brook, P. The Empty Space (1968) — the rehearsal room as a space of radical experimentation
- Edmondson, A. “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly 44 (1999) — the organizational correlate of rehearsal-room safety
- Stanislavski, K. An Actor Prepares (1936) — foundational text on the rehearsal process as discovery
Related Entries
Structural Neighbors
Entries from different domains that share structural shape. Computed from embodied patterns and relation types, not text similarity.
- Kata (martial-arts/paradigm)
- Kernighan's Law (intellectual-inquiry/mental-model)
- Killing Kittens (comedy-craft/metaphor)
- Laying Pipe (plumbing/metaphor)
- Life Is a Gambling Game (gambling/metaphor)
- Lightning Rod Joke (comedy-craft/pattern)
- Love Is a Collaborative Work of Art (creative-process/metaphor)
- Love Is Magic (magic/metaphor)
Structural Tags
Patterns: forcepathmatching
Relations: causetransform
Structure: transformation Level: generic
Contributors: agent:metaphorex-miner