Mistake Recovery Playbook: The First 30 Minutes and Preventing a Repeat

プロジェクト管理・開発

Mistake Recovery Playbook: The First 30 Minutes and Preventing a Repeat

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.

0 いいね 0 コピー 作者: WeProcess
mistake recovery first response reporting up prevention first-year survival
無料登録してこのテンプレートを使う

無料登録すると、マーケットプレイスからこのテンプレートをコピーして使えます

ホワイトボード プレビュー

プレビュー表示中 Mistake Recovery Playbook: The First 30 Minutes and Preventing a Repeat
無料登録してこのテンプレートを使う

ホワイトボード プレビュー

1. How to Face a Mistake 2. The First 30 Minutes (stop → facts... 3. Five Points Every Report Needs 4. Say It Without Excuses 6. Prevention Log (what happened, why... Mistake Recovery ... How to use: 1. St... Where you want to... Steps to follow Do not do this Take this forward Where you want to be by tonighte.g. The damage is stopped today, and you can walk through the fix at tomorrow morning stand-up. The first two promises1. Do not hide it, do not dress it up2. First report within 30 minutes Do not do this- Quietly fix it, then report- Wait until you know the cause Go easy on yourselfWhat costs you is hiding it, not failing.Save the self-blame for the trip home; right now, keep your hands moving. 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. 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) 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 T... 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 What happened Cause (the fifth ... Fix and whether i... Aug 3 - wrong nam... Invoice for Company B went out addressed to Company AAmount correct, name wrong Invoicing is still a one-person jobwith no named checker Split into an issuer and a checkerConfirmed it worked on the Aug 17 invoice Aug 10 - schedule... Forgot to tell 3 attendees the time had moved2 turned up at the old time Change notices rely on one person rememberingNo owner for updating the calendar Update the calendar first, then tell peopleChecked Sep 1, nothing missed since Aug 17 - file ove... Overwrote a file in the shared folderand wiped out a senior colleague's edits No rule for telling old files from newand no shared steps for restoring them File names now carry the dateRestore steps on the desk, effect still being checked
100%

ドラッグで移動・ホイールで拡大縮小

タスクボードの内容

Just happened 18件

Set up your playbook
Sort facts vs impact
Tell your manager
Ask why five times
Make the fix stick
List 3 key contacts
Read the 30-min flow
Time-stamp the facts
Size the impact
Flag what is unknown
Build a 30-sec brief
Pick 1-2 decisions
Agree who apologizes
Chain five whys
Add outside factors
Pick one safeguard
Log it in one line
Check it in 2 weeks

First response 0件

Reported 0件

Prevention in progress 0件

Done 0件