Activity 5 · Build failure immunity

Failure Reframe

You're going to fail sometimes — that's not a bug in the plan, it's how prototypes work. This exercise turns failures from things you carry into things you harvest: sort them, learn from them, and let most of them go.

Why do this?

Designers expect to fail early and often — it's how you find what works. But un-processed failures pile up as shame and second-guessing. Sorting them does two things: it shrinks the ones that don't deserve your energy, and it squeezes a usable lesson out of the ones that do. Do this once or twice a month and failure stops being scary.

How it works

  1. Log a few recent times you messed up — this week, this month, or your all-time hits.
  2. Sort each one into a type (below).
  3. Harvest a lesson from the ones worth learning from, and write the tiny next-time action.

The three types

ScrewupA simple slip. You normally get this right.→ Acknowledge, apologize if needed, move on.
WeaknessA repeat failure from an abiding shortcoming.→ Work around it; avoid the triggers.
Growth opportunityA failure you could fix next time.→ Learn the lesson and improve.

An example

One entry, worked through:

What happened: Called a client, launched straight into my agenda, and she got upset.
Type: Growth opportunity — not a screwup (it was a pattern, not a slip) and not a weakness (I'm normally good on client calls).
Lesson: Always do a human check-in before business.
Next time: Open every call with “What's new since we last talked?”

Your failure log

Key insights

Looking across your entries, what's the one thing worth carrying forward?

Everything saves automatically in this browser — nothing is uploaded.