The postmortem writes its first draft

Incident notes and timeline compiled into a postmortem draft while the details are still fresh

  • Runs while your laptop is closed
  • Reports in Littlebird and by email
  • Free plan includes 5 routines
Routines
Incident Postmortem Drafter
Weekly on Monday at 8:30 AM

You had two incidents last week, and a postmortem draft is ready for each.

  • Login outage, Tuesday 2:10 to 2:55 AM: an expired certificate blocked sign-ins. The draft covers the timeline, cause and three follow-ups.
  • Slow search, Thursday afternoon: an index rebuild ran during peak hours. The fix and two action items come from Friday's review meeting notes.

The problem

Postmortems decay by the hour. By next Tuesday, the timeline is reconstructed from chat scrollback and memory, and the honest 2am details have been politely forgotten.

The document everyone agrees is the most valuable in engineering is the one nobody has time to write properly, right after the week they can least afford it.

What it does

This routine compiles the incident's notes, timeline, and chat record into a structured postmortem draft: what happened, when, why, and what follows.

You edit for nuance and blamelessness. The skeleton, the part that takes hours, is already standing.

Try the prompt

Copy it into a new Littlebird routine, then set the days and times that fit your schedule

  1. Open Littlebird and go to Routines. Open the menu next to New Routine and choose Set up manually.
  2. Paste the prompt into Instructions, then set the days and time under Run.
  3. Littlebird runs it on schedule from then on. You can pause or edit it anytime. Auto-pause is on by default and pauses it if reports go unread.

You can also choose Create with Littlebird and describe the routine in chat.

Configure routine
Name
Incident Postmortem Drafter
Instructions

Every Monday draft postmortems for any incidents from the past week using meeting notes and context

Run
Weekly on Monday at 8:30 AM
EmailSend an email when a report is ready
Auto-pausePauses when reports go unread

Why make it a routine?

You can fake this with a chat skill and enough copy-paste. Most people keep it up for a week, then stop, because the copy-paste is the actual job.

A routine removes the choreography: the context is already there, the schedule is already set, and the output shows up where you need it.

And it is private by design: SOC 2 Type II, GDPR and CCPA aligned, and your data is never sold.

Frequently asked questions

When should it run?

Every Monday by default, covering the past week's incidents. You can also run it by hand right after an incident closes, while everything is fresh.

Does it assign blame?

No. It compiles facts and timeline. The culture of the document stays with the humans.

Which tier is right for one person?

Basic is free and includes routines. For more usage, Plus is $17 a month ($20 month-to-month) after a 14-day free trial.

Is support included in the price?

Yes. Plus at $17 a month ($20 month-to-month) covers the product, routines, and help when you need it.

More routines like this one

Put Littlebird to work

Littlebird is free to start, and your routines also work on the web, iPhone and Android

Download Littlebird

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Close