FAFake Co
Sign in
Engineering

Postmortem: the Monday outage

BRBruno Okafor1 min read

We raised this during the pilot and it is still the main gap. A rough first version would already be a big improvement. The current flow takes six clicks; it should take one.

Step by step

The workaround breaks as soon as a second person is involved. Happy to test a beta build if that helps. Screenshots are attached in the thread below.

  1. Enable Zapier triggers.
  2. Enable internal notes.
  3. Enable keyboard shortcuts.
  4. Enable a Linear two-way sync.

Next steps

We would move our whole team over if this landed. A rough first version would already be a big improvement. We raised this during the pilot and it is still the main gap.

Step by step

We are working around it with a spreadsheet, which is not sustainable. Our ops team has a runbook step purely to work around it. It would remove the last manual step before we can automate this.

  1. Enable CSV export.
  2. Enable an audit log.
  3. Enable an RSS feed.
  • billing
721 views

Keep reading

  • Engineering

    Hiring: engineers for the mobile web app

    Even shipping it behind a flag would let us validate the approach. We hit this every Monday during the weekly review. What changes. It would let us retire an internal tool nobody…

    FAFake Co Owner1 min read
  • Engineering

    What we shipped in 2025 Q4

    Even a read only version would unblock us. A rough first version would already be a big improvement. Two people on the team have independently asked for this. Limits. This is the…

    FAFake Co Owner1 min read
  • Engineering

    Three questions the changelog should answer

    It would pay for itself in the first month. Our response times would improve without adding headcount. What changes It would pay for itself in the first month. We hit this every Monday during the…

    DMDmitri Reyes1 min read