Three questions the changelog should answer
DMDmitri Reyes1 min read
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 weekly review. The workaround breaks as soon as a second person is involved.
Next steps
We would stop exporting to a spreadsheet every Friday. It would remove the last manual step before we can automate this. It was the first thing our new hires tripped over.
- Enable dark mode.
- Enable CSV export.
- Enable an RSS feed.
curl -sS https://api.example.test/v2/changelog \
-H "Authorization: Bearer $BULLETIN_API_KEY"
Step by step
This has come up in three separate customer calls this month. This is table stakes in every competing product we evaluated.
- Enable Zapier triggers.
- Enable an audit log.
Limits
We have a Zapier hack doing this today and it breaks weekly. The workaround breaks as soon as a second person is involved. It would pay for itself in the first month.
- security