history Last updated

Operational documents have the shortest read-time budget of anything in IT — often a few seconds, by a tired person. These templates front-load the actionable part and push the background to the bottom, and the postmortem template is deliberately blameless.

  • Development & Release — the deploys and rollbacks an incident is often traced back to.
  • Testing & QA — where a production defect becomes a test that would have caught it.
  • Security & Compliance — for incidents that are security events, and the risks a postmortem exposes.

Linked from

  • Change Request — The approval record for a production change: what, when, risk, backout, and who said yes.
  • Development & Release — Coding standards, review checklists, PR templates, release notes and deployment runbooks.
  • Incident Report — The factual record of an outage: timeline, impact, actions — written during and immediately after, not weeks later.
  • On-call Handover — Live context passed between shifts, so the next engineer does not start from zero.
  • Operational Runbook — What to do when the alert fires, written for someone half asleep who did not build the system.
  • Overview — Copy-paste document templates for IT work, each with a worked example and the mistakes that usually spoil it.
  • Postmortem — Blameless analysis of why an incident was possible, and what change would prevent the class of it.
  • Security & Compliance — Security policies, risk registers, access reviews, vendor assessments and DPIAs.
  • Testing & QA — Test plans, test case specifications, defect reports, UAT plans and summary reports.