Active ExperimentProcesses

The Pre-Mortem Experience Review

What becomes visible when a team assumes the experience has already failed and works backward to understand why?

Last updated: August 2026
The Pre-Mortem Experience Review

Hypothesis

"If design teams imagine a specific service experience has already failed, trace the conditions that produced that failure, and design both prevention and recovery responses, they will identify risks and affected participants that a conventional design critique is likely to miss."

The Problem Space

Traditional design reviews usually evaluate whether the intended experience is understandable, usable, and visually complete. They are less effective at examining what happens when information is inaccurate, systems disagree, technology becomes unavailable, responsibilities are unclear, or users behave differently than expected. These conditions often determine whether people trust an experience, yet they may remain unexamined until after launch.

Current Approach

I’m developing a structured pre-mortem method for reviewing service experiences before launch.

    The first test environment is hotel digital check-in. The intended journey appears simple: verify the reservation, confirm arrival, receive a room assignment, and access the room. In practice, the experience depends on room readiness, identity verification, payment authorization, property-management systems, digital-key technology, accessibility requests, staff coordination, and a clear recovery path when any part fails.

    The review begins with a specific future statement:

    “It is three months after launch. Digital check-in has damaged guest trust, increased operational work, and created inconsistent arrival experiences.”

    The team then works backward through six stages:

    1. Describe the failure
    Define what happened, who was affected, and what evidence shows the experience failed.

    2. Trace the conditions
    Identify the information, decisions, dependencies, policies, assumptions, and behaviors that made the failure possible.

    3. Locate early signals
    Determine what could reveal the failure before it reaches the guest or becomes widespread.

    4. Assess the impact
    Examine severity, likelihood, detectability, reach, and reversibility without presenting the scores as precise predictions.

    5. Design prevention
    Change the experience, workflow, responsibility, or system condition that contributes to the failure.

    6. Design recovery
    Define what the guest and employees should experience when prevention does not work.

    The experiment will compare risks and interventions generated through a conventional design critique with those generated through the pre-mortem review.

    The goal is not to predict every possible failure. It is to make assumptions, dependencies, warning signals, and recovery responsibilities visible early enough to influence the design.

Iteration Timeline

December 2025

Failure-Backwards Review

The original method asked teams to imagine that a product had already failed, identify possible causes, and work backward to the design decisions that allowed those failures to occur.

January 2026

From Brainstorming to Facilitation

An open-ended failure brainstorm could generate interesting risks without producing actionable decisions. The method needed clearer prompts, prioritization criteria, ownership, and defined outputs.

August 2026

Prevention and Recovery

The framework expanded beyond preventing failure. Because prevention will never be perfect, every significant scenario must also include detection signals, ownership, and a recovery experience.

August 2026

Digital Hotel Check-In Selected

Hotel digital check-in was selected as the first test environment because the guest-facing experience depends on room readiness, identity verification, payment, accessibility information, staff coordination, digital-key technology, and multiple hotel systems.

In Progress

Six-Stage Review Method

The current iteration structures the review around describing failure, tracing contributing conditions, locating early signals, assessing impact, designing prevention, and designing recovery.

Planned

Review Method Comparison

The same digital check-in concept will be evaluated through a conventional design critique and a pre-mortem review. The risks, participants, dependencies, and interventions produced by each method will then be compared.

Still evolving...

Current Insight

A resilient experience is not one that never fails. It is one that detects failure early, limits its impact, gives people a clear way forward, and helps employees recover without inventing a workaround in the moment. Designing the recovery path is part of designing the product—not an operational task to solve after launch.

Still Evolving

Open questions we're exploring:

  • How specific should the initial failure statement be without limiting what participants discover?
  • How can the method encourage honest risk identification without turning the session into unstructured pessimism?
  • Which risks require design changes, and which require policy, training, staffing, or technical intervention?
  • How should likelihood, severity, detectability, reach, and reversibility influence prioritization?
  • How can teams distinguish a plausible failure from an imaginative but extremely unlikely scenario?
  • When should the pre-mortem occur during the design process, and when should it be repeated?
  • How can frontline employees participate safely when they identify risks created by leadership decisions?
  • Can the method work effectively for a solo designer, or does it depend on cross-functional knowledge?
  • How should unresolved risks be documented and assigned after the review?
  • How can prediction accuracy be evaluated without judging the method only by whether a failure eventually occurs?

Artifacts & Resources

Framework — In Development

Pre-Mortem Experience Review

A six-stage method for describing failure, tracing conditions, identifying early signals, assessing impact, and designing prevention and recovery.

Scenario — In Development

Digital Check-In Failure Statement

A future-state scenario in which hotel digital check-in has damaged guest trust, increased operational work, and created inconsistent arrival experiences.

System Map — Planned

Digital Check-In Dependency Map

A map connecting the guest experience with identity verification, payment, room readiness, accessibility requests, digital keys, hotel employees, and supporting systems.

Review — Planned

Conventional Design Critique

A baseline review of the digital check-in concept focused on clarity, usability, consistency, task completion, and the intended guest journey.

Workshop — Planned

Pre-Mortem Review Session

A structured review focused on failure conditions, affected participants, warning signals, operational dependencies, prevention, recovery, and ownership.

Canvas — In Development

Failure Scenario Canvas

A reusable worksheet documenting the failure, contributing conditions, affected people, early signals, impact, prevention, recovery, and responsible owner.

Comparison — Planned

Critique vs. Pre-Mortem Findings

A side-by-side analysis of the risks, dependencies, participants, and design interventions uncovered by each review method.

Library — Future Iteration

Service Failure Pattern Library

An evidence-based collection of recurring failure patterns added only as they are identified through completed reviews and documented cases.

Facilitation Guide — Future Iteration

Pre-Mortem Workshop Guide

A practical guide covering preparation, prompts, timing, psychological safety, prioritization, documentation, ownership, and follow-through.

Related Experiments

Experiment Meta

Status

Active Experiment

Category

Processes

Last Updated

August 2026