Interactive graph
Fail on Paper First
Table of Contents
Before you commit, imagine the launch failed - name why, then fix the plan while rollback is cheap.
Key Concept
- Fail on paper first is counting cost before the wall stops mid-air - failure on paper beats surprise in production.
- Risk Management without failing on paper first is optimism wearing a spreadsheet.
Level 1 - Recognize
Fail on paper first is imagining the launch failed, naming why, and fixing the plan while rollback is still cheap.
Level 2 - Explain
Ask what would make this birthday party flop before you send invites - cheaper to fix on the whiteboard than in tears Saturday.
Level 3 - Use
The room assumes the project died - list causes, then patch the plan before anyone ships.
Level 4 - Connect
Pairs with Reversibility and Rollback Principle - failing on paper first asks what triggers the revert before users feel pain.
Level 5 - Create
Build a premortem that names likely failure paths, early signals, owners, and rollback triggers before the launch makes each fix expensive.
Examples
- Glad we fixed DNS docs and scope before go-live when we listed three ways the client would call angry about the static site.
- Team assumed the tournament format failed - whiteboard showed scheduling was the killer; we moved pools before registration opened.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Count the Cost | Faith lane names honest cost before vows |
| contradicts | Ship It | when ship-now beats fail-on-paper first |
| extends | Decision Quality | Visible failure modes improve the call |
| extends | Reversibility | Failing on paper first designs the undo before the commit |
| extends | Risk Management | Named risks beat hoped-away risks |
| extends | Rollback Principle | Know the revert trigger before deploy |
