Key Principle
Everything affecting participant experience is a designable surface. The designer's role is not to author stories but to create conditions -- storyworlds, characters, mechanics, social frames -- from which meaningful stories emerge through participant co-creation.
Why This Matters
Without this principle, designers treat only runtime as their domain and default to inherited conventions. Unexamined surfaces still shape experience, but accidentally. The Nordic tradition's defining move was treating the boundary of "what counts as design" as itself a design decision -- expanding scope from runtime to the full participant lifecycle (announcement through post-larp memory).
Core Frameworks
The Mixing Desk of Larp: Thirteen adjustable faders replacing aesthetic tradition ("this is how we've always done it") with explicit parameters. Externalizes implicit assumptions as movable settings, forcing designers to confront choices they were making unconsciously.
Three Meanings of Larp: A larp exists as script (written), runtime (played), and community memory (remembered). Design work that stops at the script misses two-thirds of where meaning is made.
Bespoke Design: Each larp is designed from scratch rather than using a universal system. Only rules that serve specific themes survive -- this is why Nordic larp stays thematically precise.
Inter-Immersion: Collective pretense generates felt reality. Players are immersed not only in their own character but in sustaining everyone else's fiction. "You cannot play a king unless others play your subjects."
First-Person Audience: Each player is simultaneously performer and audience, seeing only what their character sees. The designer can never see the larp as any player sees it.
Alibi: Layered permission enabling non-standard behavior. From weakest to strongest: (1) the fiction itself, (2) the character, (3) interpersonal trust. The third layer enables play that no amount of worldbuilding can unlock alone.
Steering and Transparency: Players guide characters toward interesting situations (steering) using information the designer provides (transparency). Together they solve the problem that no central author controls the story.
Good Examples
- The fishwife problem (1990s): Writing better female characters didn't fix gendered agency gaps because players brought patriarchal norms into play. Only when design scope expanded to include promotional imagery, fictional gender systems, and workshop exercises did the problem yield.
- The Mixing Desk was developed through the Larpwriter Summer School (2012-2017), training approximately 50 students from 20 countries.
- Jeepform principle: "Start out with the game being completely transparent, and only hide things if you think it will be an improvement." (Tobias Wrigstad, Ch. 3:1:2)
Counterpoints
- "Everything is designable" is paralyzing without triage. The heuristic: rank decisions by impact on play experience weighted against cost to team wellbeing, and work down from highest impact.
- Even poorly designed larps usually work because embodied role-playing is inherently powerful and players actively fix problems -- this is both reassuring and a trap that masks design failures.
Key Quotes
"Anything and everything affecting player behaviour and participant agency in a larp is seen as a designable surface." (Introduction)
"This is the magic trick that makes the fiction come alive: when everyone pretends that it is real, it starts to feel real." (Ch. 1)
"The full duration of your larp is forever, or at least until the last person who remembers it has died." (Ch. 1)
"Nothing is as practical as good theory; a good map is easier and faster to understand than the terrain it models." (Part 1)
Rules of Thumb
- Design the full lifecycle, not just runtime -- every communication from announcement to post-larp debrief shapes the experience
- Default to transparency -- add secrecy only when it demonstrably improves the experience
- Treat trust as a design material, not a social nicety
- Engagement depth is gated by permission strength (alibi), not production quality
- The designer bears moral responsibility for how participants treat each other
Related References
- Rules of Thumb: Design Heuristics Across All Domains -- Heuristics derived from these principles
- Narrative Design: Stories, Structure, and Transparency -- Transparency and steering applied to story
- Workshop Design: Gap Analysis and Culture Building -- Building the social frame before runtime
- Safety, Opt-Out, and Calibration Mechanics -- Consent as continuous process