Preparing the next view without exposing private workflow data.
System design · Phased project
Design notification delivery around preferences and receipts
A fictional collaboration tool sends email and in-app notifications. Duplicate alerts and preference changes reveal that the design has no single definition of delivery.
Practice brief · Version 5
Project scope
10 tickets / 3 phases
Total focused work estimate
31h 30m + setup
Suggested stack
TypeScript · PostgreSQL · Provider interfaces
Recommended next step
Start with ANOTIFY-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Practice asynchronous contracts, preference timing and delivery uncertainty.
What the team gains
Review a notification design that controls nuisance, disclosure and recovery.
Before you start
Create synthetic recipients, events and fake delivery providers.
Do not send real email or messages.
Delivery agreement
Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.