Key Principle
Post-play is a designable surface. The period after runtime is where memories form and meaning is assigned. Post-play processes happen whether designed or not -- the designer's choice is not whether these processes occur but whether to guide them.
Why This Matters
"Much of what the participants will remember and feel about the experience is decided here." (Ch. 4:1:1) A well-designed debrief can reframe a mediocre runtime; an unmanaged post-larp narrative can undermine brilliant design. Memory is not a recording of what happened but a narrative shaped by post-runtime design.
Core Frameworks
The Real-but-Not-True Paradox: "What happens in larps is not true, but quite a lot of it is real." (Section 4:1) Actions in a fictional frame are culturally "not true," yet the embodied experience -- emotions felt in the body, social bonds navigated -- is real. This paradox is what makes post-play processing necessary.
Three Goals of Post-Play:
- Reconnection -- separate player identity from character; interact as primary selves
- Reflection -- name and process what was felt; establish shared understanding with co-players
- Recuperation -- self-care and mutual care after intensity
Moral Hangover (Eirik Fatland): The fictional frame permits morally transgressive actions, but embodied performance generates real emotional residue. The body does not distinguish between performed and authentic moral transgression.
Larp Wrap / Epilogue: Players narrate their character's story briefly. This orders chaos -- including retroactively attributing motivation to impulsive in-game choices. Gets the story "out of their system" before deeper processing begins.
Six Feedback Motivations Taxonomy (honest self-assessment required):
- Improvement -- most constructive, hardest to obtain
- Unfiltered truth -- anonymity helps but players remain reluctant
- Retention -- customer satisfaction, best served by anonymous surveys
- Affirmation -- valid emotional need but incompatible with honest feedback
- Narrative control -- selective framing through question design
- Appearance of professionalism -- not a valid reason
Feedback/Debrief Separation: "Don't mix the feedback round (which is for you) with the post-larp debrief (which is for the participants)." (Ch. 4:1:2) Schedule a break between them. Make feedback voluntary with easy opt-out.
Good Examples
- Minimal Feedback Protocol: (1) Silent reflection on "what worked well" and "what worked less well," (2) round-robin sharing with deaf applause for agreement, (3) pre-prepared specific questions, (4) thank the players. Optimal group: 5-10 players. Requires a dedicated note-taker.
- Deaf applause: Silent hand-waving to signal consensus without verbal pile-on, preserving airtime equity.
- Post-play design heuristic: two questions govern all decisions -- (1) What do players of this larp need, due to its content? (2) What do players as human beings need, after their experience?
Counterpoints
- Bleed is real as experience but metaphoric as description. Since a larp character is a conceptual structure, nothing literally transfers between two identities. All feelings during and after larp are the player's own. Debrief processes that ask participants to "separate character feelings from player feelings" attempt an impossible task.
- Free-floating trust between co-players after a larp can rapidly become meaningful friendship or feel awkward and alienating. Residual emotions from fictional relationships, left unresolved, can cause real interpersonal conflict.
- "If negative feedback would crush you and make you never want to organise another larp, better not ask for feedback at all." (Ch. 4:1:2)
Key Quotes
"As they will occur whether or not you design their framing and facilitation, integrating post-play activities into your design is good practice." (Ch. 4:1:1)
"When asking for feedback, you are using their time and tapping into their own design skills -- make sure that it matters!" (Ch. 4:1:2)
"Don't mix the feedback round (which is for you) with the post-larp debrief (which is for the participants)." (Ch. 4:1:2)
"All the feelings, thoughts, and actions are the players'." (Ch. 1.1.2)
Rules of Thumb
- Post-play activities should be opt-out (expected) rather than opt-in (volunteered)
- Never combine feedback collection with emotional debrief
- Identify your actual feedback motivation before choosing a method
- Feedback question design is narrative design -- questions determine what gets remembered
- Moral hangover from playing villains requires structured processing, not dismissal
- Two questions govern all post-play design: what does this larp need, and what do humans need
Related References
- Core Framework: Designable Surfaces and the Mixing Desk -- Three meanings of larp (written/played/remembered)
- Safety, Opt-Out, and Calibration Mechanics -- Calibration extending into post-play
- Implementation Playbook: Full Lifecycle Design Process -- Post-play in the full lifecycle
- Inclusion and Equity: Fun Tax, Accessibility, and Identity Design -- Processing identity-related intensity