Project & Development
Mistake Recovery Playbook: The First 30 Minutes and Preventing a Repeat
Intermediate | 1 whiteboard page · Task board: 5 columns (5 parent tasks, 13 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
The Mistake Recovery Playbook is a template for a first-year employee who made a serious mistake at work, covering the first response, the report to a manager, five whys analysis, and prevention. The whiteboard holds how to face a mistake, a five-step flow for the first 30 minutes, the five points every report needs with phrasing that avoids excuses, a five whys analysis, and a prevention log. The kanban runs from just happened to done in five columns, with five parent tasks and 13 subtasks already written and untouched - first response, separating fact from impact, reporting, finding the cause, and preventing a repeat. Because the words for the report and the next move are decided in advance, you start moving instead of hiding the mistake, and you end up with a safeguard that stops it happening twice.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Mistake Recovery Playbook
How to use: 1. Stop what you are doing 2. Follow the 30-minute flow 3. Ask why five times 4. Log the fix
1. How to Face a Mistake
- Where you want to be by tonight e.g. The damage is stopped today, and you can walk through the fix at tomorrow morning stand-up.
- The first two promises 1. Do not hide it, do not dress it up 2. First report within 30 minutes
- Do not do this - Quietly fix it, then report - Wait until you know the cause
- Go easy on yourself What costs you is hiding it, not failing. Save the self-blame for the trip home; right now, keep your hands moving.
2. The First 30 Minutes (stop → facts → impact → report → record)
- 1. Stop (0-3 min) Put the work down and stop anything that spreads the damage. No deleting, no overwriting, no resending from here.
- 2. Get the facts (3-10 min) Write what you did and when, with times. Keep the screens and emails as evidence, and keep guesses separate.
- 3. Size the impact (10-18 min) Put numbers on who, how many, and how much. Where you do not know yet, write still checking.
- 4. Report (18-25 min) Give your manager a 30-second first report (the five points in section 3). If you cannot reach them, go one level up and brief your manager afterwards.
- 5. Record (25-30 min) Turn the instructions and deadlines you were given into cards. From here, switch your head to finding the cause.
3. Five Points Every Report Needs
- Apology (one line only, then straight into the facts)
- Facts (what happened, at what time, and how far you have confirmed)
- Impact (12 wrong recipients, 3 of them outside the company)
- What you are doing now (sending stopped, recall request being drafted)
- The call you need (whose name the apology goes out under)
4. Say It Without Excuses
- Instead of: I was not told → say: I sent it without checking the steps
- Instead of: It is probably fine → say: Not confirmed yet. I will confirm by 3 p.m.
- Instead of: Sorry, um... → say: Headline first. I sent the email to the wrong people
5. Ask Why Five Times (five whys, example: wrong company name on an invoice)
- Why 1 Copied last month's invoice and sent it without swapping the client name
- Why 2 There is no blank template to start from, so copying became the norm
- Why 3 Everyone builds invoices their own way and there is no written procedure
- Why 4 Nobody but the person who made it ever looks at the contents
- Why 5 Invoicing is still a one-person job, with no named checker
6. Prevention Log (what happened, why, and did the fix work)
| What happened | Cause (the fifth why) | Fix and whether it worked | |
|---|---|---|---|
| Aug 3 - wrong name on invoice | Invoice for Company B went out addressed to Company A Amount correct, name wrong | Invoicing is still a one-person job with no named checker | Split into an issuer and a checker Confirmed it worked on the Aug 17 invoice |
| Aug 10 - schedule change missed | Forgot to tell 3 attendees the time had moved 2 turned up at the old time | Change notices rely on one person remembering No owner for updating the calendar | Update the calendar first, then tell people Checked Sep 1, nothing missed since |
| Aug 17 - file overwritten | Overwrote a file in the shared folder and wiped out a senior colleague's edits | No rule for telling old files from new and no shared steps for restoring them | File names now carry the date Restore steps on the desk, effect still being checked |
Task board contents
Just happened 18 items
Set up your playbook
You cannot write a procedure while the mistake is unfolding. Read this on a calm day, so on the day itself you only have to follow the board.
List 3 key contacts
Write three numbers on paper - your manager, a senior colleague, and the client contact - so you can reach someone even without your work laptop.
Read the 30-min flow
Read the five steps of the first-response flow out loud once, so the order is in your body before you need it.
Sort facts vs impact
Mixing opinion into facts makes the report wobble. Done when what happened, what is still unknown, and who is affected are written separately.
Time-stamp the facts
List only facts you can back up with logs or email - what you did at what time, and when you noticed.
Size the impact
Put a number on it - how many recipients, how much money. Without numbers your manager cannot decide.
Flag what is unknown
For anything still being checked, add a deadline, such as still confirming, will report by 3 p.m.
Tell your manager
Every minute you sit on it turns into more damage. Done when the first report is out and you have your next instruction.
Build a 30-sec brief
Say three things only - what happened, how far the impact reaches, and what you are doing right now.
Pick 1-2 decisions
Narrow what you cannot decide alone down to one or two calls, and take only those in.
Agree who apologizes
Agree with your manager whose name the apology goes out under and when, and never send it on your own judgment.
Ask why five times
Stop at your own carelessness and the same mistake comes back. Done when you reach the procedure, the check, and the system behind it.
Chain five whys
Dig under I forgot to check, and fill all five levels of the five whys on the board.
Add outside factors
A squeezed deadline or a missing procedure counts too - if it is a fact, it is material for prevention.
Make the fix stick
I will be careful is not a countermeasure. Done when the fix works by itself next time and you have checked that it did.
Pick one safeguard
Choose exactly one thing you can do from tomorrow without fail, such as reading the address line aloud before you send.
Log it in one line
Record date, event, cause, and fix in the log, written so you a year from now and the next new hire can both follow it.
Check it in 2 weeks
See whether the fix actually fired in the same situation, and reshape anything that did not stick.
