Incident postmortem
Timeline, impact, causes and follow-ups, written without blame.
Engineering · 8.7k uses
Problem first, proposal second, open questions in a list someone owns. Reviewers sign the decision log at the bottom, so nobody asks “did we agree on this?” in the next sprint.
TEdited by TheoEngineering22.1k uses25 min to fill
Juniper & CoTemplatesSpec: Rate limits for the public API
One paragraph, no jargon: what is broken and who feels it.
Three customers sent more than 40,000 requests a minute last week. The API slowed down for everyone else, and support answered 26 tickets about it.
More like this
Teams who use this template usually keep these three next to it in the sidebar.
Browse all 24 in the galleryTimeline, impact, causes and follow-ups, written without blame.
Engineering · 8.7k uses
Bets for the quarter in one table, as a timeline for the all-hands.
Product · 11.9k uses
Context first, then feedback sorted by what it asks the designer to do.
Design · 9.6k uses
Free for personal use. Your team can start on Plus with a 14-day trial, no card needed.