I built BlamelessPostmortem after getting tired of post-incident writeups turning into political documents instead of learning tools.
After incidents, teams usually have: - chat logs - timelines - scattered notes
Turning that into a clean, executive-safe postmortem takes time and careful wording, especially if you’re trying to keep things blameless and system-focused.
BlamelessPostmortem takes raw incident notes and generates a structured postmortem with: - Executive summary - Impact - Timeline - Blameless root cause - Action items
You can regenerate individual sections, export everything as Markdown, and copy the full document into tools like Confluence, Notion, or Docs.
There’s a small free tier, then it’s $29/month if it’s useful. I built it as a solo project and wanted to see if this solves a real pain for other engineers.
I’d love feedback on: - Whether the output matches how you write postmortems - Where the language feels off or too generic - What would make this trustworthy enough to use after a real incident
Happy to answer questions or explain how it works.
markus_zhang•1mo ago
> If you break the build then your ass is grass and I’m the lawn mower.
jabelburns•1mo ago
I don’t think blameless postmortems mean “no accountability” or “nothing bad happened.” They’re more about separating learning from discipline.
In my experience, the postmortem is the wrong place to assign consequences — once people feel personally on trial, the document becomes defensive and you lose signal about system failures.
You can and should still hold people accountable elsewhere, but the writeup itself should be boring, factual, and focused on how the system allowed the failure. This tool is opinionated in that direction, which definitely isn’t universal.