Rob FrascaAll ideas

Stamp and Repeat: Turn Every Debrief Into a Tool.

The debrief finds the lesson. The tool keeps it.

FrameworkCreator's JourneyLeadershipPerformance

The Creator's Journey · Chapter V, What the Losses Taught

Every flight I flew ended in a debrief. What went wrong? What could we do better? What do we carry into the next flight? I have debriefed everything I have done since. It is not a talent. It is a habit, practiced until it runs on its own.

But a lesson that lives only in your memory fades. My father was a manufacturing engineer. He used to say it is easier to build a tool that makes something over and over again than to make it by hand each time. Stamp and repeat.

LOSSDEBRIEFFINDS THE LESSONTOOLSTAMP AND REPEAT
The debrief finds the lesson. The tool keeps it.
From the book
The debrief finds the lesson. The tool keeps it.
Rob FrascaThe Creator’s Journey (forthcoming)
From the research
Under conditions of complexity, not only are checklists a help, they are required for success.
Atul GawandeThe Checklist Manifesto, 2009

So every debrief should end with a tool. A checklist. A rule. A process. A question you will ask before every raise, every launch or every hire. When I debriefed Internet Venture Works, one tool that came out of it was a rule: treat easy money as a warning sign, not a compliment.

Run the debrief well

  1. Do it soon, but not immediatelyGive people a few days to let the adrenaline settle. Wait much longer and memories rewrite themselves into more flattering versions.
  2. Facts before opinionsBuild the timeline first: what happened, in what order, and what each person knew. Most debrief arguments are disagreements about facts.
  3. Let rank go quietAsk the people with the least authority to speak first, so they are not echoing the boss.
  4. End with an ownerOne person leaves the room responsible for turning the lesson into a tool, with a date when it will exist.

The evidence for the humble tool

Atul Gawande made the case in The Checklist Manifesto. In a study across eight hospitals around the world, his team’s surgical safety checklist cut deaths and complications by more than a third. Google’s engineers built the same habit into software. Their site reliability teams write blameless postmortems: find the contributing causes, assume everyone acted in good faith with what they knew, and change the system so the failure does not repeat.

This matters even more with AI. The temptation is to just use the tool and hope for the best. The leverage comes from building the framework first, the checklists and processes your experience has taught you, and then letting AI work inside it so it performs repeatably and reliably. A loss you have debriefed and turned into a tool becomes part of the machine. A loss you have only survived is just a scar.

Quick answers

What does “stamp and repeat” mean?

A phrase from Rob Frasca’s father, a manufacturing engineer: it is easier to build a tool that makes something over and over than to make it by hand each time. Rob applies it to debriefs. Every debrief should end with a tool, such as a checklist, a rule or a question.

How do you run a blameless debrief after a loss?

Rob Frasca’s rules: hold it soon but not immediately, build the timeline of facts before opinions, let the people with the least authority speak first, and end with one owner who turns the lesson into a tool by a set date.

Sources

  1. Rob Frasca, The Creator’s Journey (forthcoming), Chapter V, What the Losses Taught.
  2. Atul Gawande, The Checklist Manifesto: How to Get Things Right (Metropolitan Books, 2009). Quote as reproduced by Farnam Street. Source
  3. “Surgical safety checklist drops deaths and complications by more than one third,” Harvard Gazette, January 2009, reporting Haynes, Gawande et al., New England Journal of Medicine. Source
  4. Google, “Postmortem Culture: Learning from Failure,” in Site Reliability Engineering (O’Reilly, 2016). Source
Open the interactive version