Product 2

Introducing Slack notifications, revisited

ANAna Andersson1 min read

It was the first thing our new hires tripped over. It would let us retire an internal tool nobody wants to maintain.

Before you start

Our ops team has a runbook step purely to work around it. We hit this every Monday during the weekly review. We would stop exporting to a spreadsheet every Friday.

  1. Enable MRR-weighted prioritisation.
  2. Enable vote weighting.
  3. Enable an RSS feed.
curl -sS https://api.example.test/v2/items \
  -H "Authorization: Bearer $BULLETIN_API_KEY"

How it works

Our response times would improve without adding headcount. Two people on the team have independently asked for this. Even a read-only version would unblock us.

What changes

We are working around it with a spreadsheet, which is not sustainable. Right now this costs us roughly two hours a week. It would pay for itself in the first month.

  • widget
6,468 views

Keep reading

  • 2026 Q3 in review: granular email preferences

    It was the first thing our new hires tripped over. Even a read-only version would unblock us. What changes We would move our whole team over if this landed. The workaround breaks as soon as a second…

    LALars Delgado1 min read
  • Hiring: engineers for search

    It would remove the last manual step before we can automate this. Right now this costs us roughly two hours a week. Step by step. It was the first thing our new hires tripped over…

    PRPriya Chen1 min read