← Working Together, in Practice
When it goes wrong · 152 of 161
After a failure, write what happened, not who
Expert guidance
Do this
- The event flopped: few came, the projector failed. Wait a day, then meet.
- Write what happened, in time order, without names where you can.
- Ask: “What made this easy to get wrong?” Nobody told the second class? There was no checklist.
- Agree on what to change. Give each change a name and a date.
- Put it in the club file.
Why it helps
Google’s engineers write blameless postmortems after failures. They assume everyone meant well, since people who fear blame hide problems. “You can’t fix people,” they say, “but you can fix systems and processes.” Blameless doesn’t mean nothing changes. Expert guidance, from a workplace.
Try it today
Think of a small failure of yours. Write what made it easy to go wrong. Three minutes.
Where these facts come from
- Postmortem culture: learning from failure, Site Reliability Engineering, Google.
General information, not professional advice. No page can fit every situation. You use it at your own risk: see our terms. Spotted a mistake, or know something better? Tell us.
