# Exit Ticket — Debrief

> Ninety seconds of paper, read fast, used immediately. Here is how.
> Use with `exit-ticket-guide.md`. Collecting at the door and "read the questions" is the compressed version; this sheet is the full one.

## How to run this debrief

- Sort the questions first; they are the most actionable paper you will collect all week.
- Count repeats, do not average — three people asking the same question is a gap, one person asking twice is one person.
- Open the next session by answering one question from the pile out loud. It teaches the room that the ticket is real.

## Read the three lines

1. **One thing you learned** — the landed list. If the same idea keeps showing up, that is what taught. If they scatter, you covered too much.
2. **One question you still have** — the live confusions. This stack is your opening for the next session, verbatim.
3. **One thing you will do next** — the transfer signal. Specific and doable is a plan; vague is a wish — follow it up next time.

## The three debrief questions

- Which question came back most often — can you answer it at the top of the next session?
- Do the learned lines cluster around what you meant to teach, or scatter? If they scatter, what are you cutting next time — not adding?
- How many of the next moves are specific and doable? The vague ones point at a barrier you have not removed yet.

## Failure modes of the debrief

| Failure mode | Why it happens | The rescue |
|---|---|---|
| Slips into a drawer | Collected, never used | Open the next session with the questions from the pile |
| Read as a grade | The slip gets treated as scored homework | Keep it anonymous and unscored — the moment it counts, it becomes performance |
| A fourth prompt appears | Anxiety to know more | Three lines is the door's ceiling; completion collapses past it |

## What this is not

It is a ninety-second pulse check, not an assessment and not a graded task. It shows you what to fix tomorrow; it is not a score of anyone today.