WorkNotification Center and Task Center
Notification Center and Task Center: owning a platform feature end to end
No team owned this problem, so I wrote the product spec myself, designed the system behind it, and designed the interface. The Task Center became the most used feature on Scrut's platform. For the first time, every user could see in one place what they needed to do next.
The decision
One inbox or two
A notification says something happened. A task says you need to do something. Most products mix them, and important tasks get lost among updates.
One combined inbox
Lower build effort at first. The main risk: tasks buried under updates, then muted.
Separate centers, one shared system Chosen
Notifications fade; tasks stay until done, with deadlines. Two screens on one shared system, each with its own rules.
What I did
Spec, system, interface
- Wrote a small Phase 1 spec and took it to the Head of Engineering and the product team. Months of discussion became agreement in one meeting.
- Built a notification plan, a grid of every notification type against each channel, that became the roadmap.
- Designed the grouping rules: by action, by module, and over a moving 10-minute window, so a burst becomes one notification.
- Designed the interface by role and to-dos rather than by module, with urgent items easy to spot.
The study in one picture
Read the full case study
Password protected. It has the trade-offs in full, the results and how they were measured, and what I would do differently.