Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Inventory of every notification the product sends
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most products send far more messages than anyone on the team can list: welcome emails written at launch, a push someone added for a growth test, receipts from the billing system, digests nobody remembers turning on.
First tasks
- Export the list of active email templates from the delivery provider
- Search the codebase for every call to the push, email and SMS send functions
- Ask support, billing and marketing which tools send messages to users on their behalf
- Ask the agent to merge the lists into one table with trigger, channel and owner columns
- Re-run the inventory and reconcile it with the previous version @recurring(yearly)
Notification volume and engagement baseline
Without a baseline, every argument about whether users get too many messages is an opinion. Measuring sends per active user per week by channel, alongside open or tap rate, unsubscribes, push opt-outs and spam complaints, shows where the volume really sits and gives later changes something to be compared against.
First tasks
- Pull last month's send counts by channel from the provider dashboards
- Divide sends by weekly active users to get messages per user per channel
- Record the 30-day unsubscribe, complaint and push opt-out rates
- Refresh the baseline figures in the metrics log @recurring(monthly:4)
Notification categories and the rules attached to each
A password reset, a comment reply, a weekly summary and a promotion for a new plan should not live under the same rules, yet many products treat them identically. Sorting every message into a small set of categories, such as security and account, transactional, activity, product updates and marketing, decides which ones users can switch off, which respect quiet hours and which need marketing consent.
First tasks
- Draft five to seven category names with one example message each
- Tag every row in the notification inventory with a category
- Write the opt-out, quiet-hours and consent rule for each category
- Review the mixed-purpose messages with your privacy adviser