Turn what went wrong into a checklist for next time

You had a bad week. A launch slipped, a supplier didn't turn up, an update took something down. Someone wrote a report. It's in a folder.

Next time, the same thing happens, because nobody opened the folder.

The fix is a short checklist you run beforehand. The report has what you need. You just need it shorter.

Below is a write-up of something that went wrong. Turn the lessons into
a pre-flight checklist for the next time we do [THIS KIND OF THING].
- Maximum 10 items. Each is a yes/no question someone can answer in
  under a minute, like "Has the supplier confirmed the date in writing?"
- Put them in the order we'd do them.
- For each, add one line saying which part of the incident it comes from.
- Leave out anything that's just "communicate better". If it can't be a
  yes/no question, say what's missing from the write-up.
- List anything from the write-up that needs a decision, not a
  checkbox.

Write-up: [PASTE]

A yes/no question can be answered. "Ensure good communication" can't. The line saying where each one came from means someone who never heard about the original problem still knows why it's there. And ten is a hard limit on purpose, because past that, nobody runs it.

Incident write-ups often name people and customers, so use a tool that's approved for that, or take the names out first.

Use the checklist on the next several jobs, and then review it. An item that always passes might be useless, or it might pass because the check is being done, so ask which before you drop it. And if something goes wrong that the list didn't catch, add it. After ten or so uses you've got a list that's been tested on real work.