Skip to content
On-Call — Incident Command for Platform Engineers
0%
Program 15 / 16

Module 4 · After

Postmortem assignment

Project 2 h

Write the postmortem for the game-day outage in Markdown or PDF. Peer and tutor review.

Write the blameless postmortem for the game-day outage you commanded in module 3 (or for the outage simulator scenario, if you missed the drill).

Requirements

  • Use the template from the resources of this topic, in Markdown or PDF.
  • Timeline in UTC, from the first trigger to the all-clear, at least 8 entries.
  • Impact in numbers: duration, share of requests affected, error budget consumed.
  • At least three contributing factors, none of which names a person.
  • At least four action items, each with an owner, a due date and a type (prevent, detect, mitigate). At least one must be detect or mitigate.
  • Maximum 1,200 words plus the timeline.

Review

Your postmortem is reviewed by one peer from your cohort and by a tutor. Expect comments within three working days. Status Changes requested is normal: most postmortems need one more round.

Rubric

CriterionExcellent (3)Adequate (2)Needs work (1)
Timelinecomplete, precise, sourced from the scribe logcomplete but vague timesgaps or reconstructed from memory
Impactquantified, linked to the SLOpartly quantifiedqualitative only
Contributing factorsseveral interacting conditions, systemica few, some point at individualssingle "root cause" or blame
Action itemsspecific, owned, dated, balanced typesspecific but missing owners or datesgeneric ("be more careful")
Toneblameless and readable by the whole orgmostly neutraldefensive or accusatory

Maximum score: 15 points. Passing: 10.

Hand in your work

In the full app you upload your files here and your tutor replies in a feedback thread. File upload is not part of this demo yet.

Downloads

Demo resets hourly

You are logged in as a demo student. Everything you do is wiped every hour.

Open the admin panel ↗

Other demos