Introducing Slack notifications, revisited
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.
- Enable MRR-weighted prioritisation.
- Enable vote weighting.
- 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