Rapid retrospectives¶

A rapid retrospective is a fifteen to twenty minute reflection held immediately after an exercise, incident response session, or tabletop. It captures learning before it disperses.

The premise is simple: insight decays quickly. A team that runs a purple team exercise and resumes normal work without reflection has had an experience but has not necessarily learned anything durable from it. The rapid retrospective is the mechanism that converts the experience into something that changes practice.

When to use it¶

After any bounded activity where something worth learning happened: a detection exercise, a tabletop scenario, a real incident, a planning session that surfaced unexpected friction. The session works best when held immediately, while the experience is fresh and before the team has had time to construct a polished narrative about what happened.

The structure¶

Gather the team. Fifteen to twenty minutes is enough if the questions are kept tight.

What went well, and why? Not just what succeeded, but what specific decision or action produced that outcome. The “why” is what makes the learning transferable.

What did not go as expected? This is different from “what went wrong.” Some things that did not go as expected went better. Others went worse. Both are worth naming.

What would we do differently? One or two concrete changes, not a general commitment to improvement.

What are we carrying forward? A specific thing to watch for, try, or avoid in the next activity.

Record the responses briefly. The record does not need to be polished. Its purpose is to make the learning retrievable.

Connection to the fuller retrospective¶

The rapid retrospective sits alongside the temperature reading retrospective as a lighter-weight companion. The temperature reading is the right tool for longer cycles, significant incidents, or any situation where the team’s experience of events needs to be examined alongside the events themselves. The rapid retrospective is for the end of an afternoon’s session.

They are not alternatives. A team that uses both develops a continuous reflection practice, where short cycles feed into longer ones and learning compounds rather than evaporates.