Skip to content
CyberSafety.lol

Playbook ยท Within a few days

It is over. Now we need to learn from it

Blameless, factual, and ending in a few real changes.

INFOTake a breath. Do these in order.

How you might know

  • An incident has been resolved.
  • The team is tired and wants to move on.
  • Nobody has written down what happened yet.

Do this now

  1. Schedule it within a few days

    Memory fades quickly. Invite everyone who was involved.

  2. Build the timeline from records

    Use logs, messages and tickets, not memory. Write down who knew what and when.

  3. List contributing factors, not culprits

    Ask what made the failure possible. People acted on the information and tools they had.

  4. Note what went well and what was lucky

    Keep the things that helped. Be honest about luck, because luck does not repeat.

  5. Agree on a few actions with owners and dates

    Fewer, better actions. Prefer guardrails that change the system over reminders to be careful.

  6. Share it

    Write a short summary others can read. Review the actions in 30 days.

Do not do this

  • Do not assign blame to individuals.
  • Do not write ten actions you will not do.
  • Do not skip it because nothing terrible happened.

Who to tell

  • Everyone involved
  • The wider team, with a short written summary

What to save before you clean up

  • The timeline
  • The final write-up
  • Links to logs and decisions

In the next 24 hours

  • Create tickets for each action.
  • Book the 30-day review.

What to write in the post mortem afterwards

  • This is the post mortem. Review the actions in 30 days.

Finished this one?

Add it to What I learned and earn 30 Trust. You can open your list from the badge at the bottom of the page.