Week 9: Failure

Week 9 — why not every mistake deserves its own signal, even once the vocabulary can support one

19 April 2027

A one-button game doesn’t fail more simply than any other kind — it just has fewer channels to explain the failure through. That’s exactly why failure had to wait until week 9: with only one mechanic active, there’s only one way to lose, and a single failure state barely needs designing. Once release-timing, sequence-breaking, and momentum-decay can each go wrong independently, failure becomes something to design on purpose rather than something that just happens.

The trade-off is restraint, not coverage. Giving every possible mistake its own distinct signal sounds thorough, but a player tracking five different failure states is tracking a system, not learning from a mistake. The design skill here is choosing which failures are worth making legible — usually the ones a player is likely to repeat — and letting the rest stay a plain, unremarkable loss.

Outline#

• why failure had to wait until the vocabulary was rich enough to fail in more than one way
• legible failure as a choice about which mistakes deserve a distinct signal, not all of them
• retry cost as the other half of legibility: what a mistake teaches, not only what it costs