# The Not-Anymore List — Debrief

> The review isn't over when something is crossed off — it's over when the stop has held, the trigger is real, and the freed time has a named purpose.
> Use with `the-not-anymore-list-guide.md`. The make-it-safe round at minute 17 is the compressed version; this sheet is the full one.

## How to run this debrief

- Keep the not-anymore list and the one stopped item **visible** while you talk — you are testing a decision, not reopening the argument.
- Push every answer toward the observable: a count, a signal, a date. Feelings don't protect stops.
- Close on the capacity — the stop only pays when the freed time goes somewhere the team chose on purpose.

## Read the list

1. **What failed the test.** Anything marked "wouldn't start today" was standing on habit alone. Look at how much of your week that is.
2. **What was uncomfortable to stop.** Discomfort is usually one person's preference wearing the team's need. Name whose it was.
3. **How big a cut you actually took.** The item you stopped — was it the biggest cost, or the safest one to cut? The safe one is a warm-up.

## The four debrief questions

- Is the bring-back trigger real and observable — "if two people ask for it" — or a feeling — "if it feels needed"?
- What's the trial period, and who owns the call at the end — to make it permanent or bring it back?
- Are you stopping it for everyone, or only for the people in this room?
- What exactly will you do with the time and attention you just freed, and when do you check that it's really gone — and really not missed?

## Failure modes of the debrief

| Failure mode | Why it happens | The rescue |
|---|---|---|
| Nobody wants to let go | Killing feels permanent | Make it a dated trial-stop; the pause usually reveals it was never needed. |
| The list is all other teams' processes | You can only stop what you own | Reframe to what this team can drop alone; hand the rest over as a named request. |
| The trigger is vague | "If it feels needed" is unfalsifiable | Push to a count, a signal, a date — a fuzzy trigger means it comes back by default. |
| The freed time refills itself | Nobody claimed it | Name what the capacity is for before closing, or the stop quietly reverses. |