---
title: "Discussion on \"How I Write Postmortems\" | Hashnode"
description: "Discussion on \"How I Write Postmortems\". A blameless, step-by-step way to turn an incident into fixes and lessons\nThis series is built on postmortems. Every story in it starts as a write-up of something that broke, or a decision that mattere"
url: "https://hashnode.com/posts/how-i-write-postmortems/6ac76fa1c9a9a606377f2f0d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I Write Postmortems](https://edwardoboh.hashnode.dev/how-i-write-postmortems?utm_source=hashnode&utm_medium=feed)

A blameless, step-by-step way to turn an incident into fixes and lessons This series is built on postmortems. Every story in it starts as a write-up of something that broke, or a decision that mattere

Oct 8 · 10 min read · edwardoboh.hashnode.dev  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#sre](https://hashnode.com/tag/sre)
-   [#incident-management](https://hashnode.com/tag/incident-management)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)
-   [#cloud](https://hashnode.com/tag/cloud)

## Written by

[Edward Oboh](https://hashnode.com/@edwardoboh)

@edwardoboh

  
[View profile](https://hashnode.com/@edwardoboh)

Cloud Infra | Senior Software

whatever topic pulls my curiosity: distributed systems, security, blockchain, cryptography or cloud infrastructure.

## Responses 2

Markdown supported · ⌘↵ to post

[Mike Dabydeen](https://hashnode.com/@firelinks)

[Oct 8](https://hashnode.com/posts/how-i-write-postmortems/6ac76fa1c9a9a606377f2f0d/comment/6ac77badee328d7c10fcc07a)

I'd add one closing rule to step 9: a detect or mitigate action is done when someone has seen it work, not when the PR merges.

Your certificate alert is a good example. It can ship, pass review and still never page anyone, because it reads the wrong secret store or routes to a channel nobody watches. Issuing a 10-day certificate in staging and confirming the page reaches on-call is a short exercise, and it gives the action item something to link when it closes: the alert that fired.

That link pays off later too. When a future incident lists a missing alert as a contributing factor, and an older postmortem already has an action item for that alert, the closing evidence tells you whether it was tested or only merged.

[Edward Oboh](https://hashnode.com/@edwardoboh)

[Oct 8](https://hashnode.com/posts/how-i-write-postmortems/6ac76fa1c9a9a606377f2f0d/comment/6ac77badee328d7c10fcc07a#reply-6ac780584e3f063320f1c285)

Thanks Mike, great point. An alert can pass review and still never page anyone, and nobody finds out until the day it is needed. Linking the action item to the alert actually firing is a simple fix. I will add it to step 9 and add a verified column to the template. Thanks again.
