Tag: notification-design
-
Operator Brief: Test an Unanswered Notice
Run four synthetic cases through a notification workflow and check whether explicit answers stay distinguishable from delivery failures and timeouts.
-
Intel Report 084: Silence Is Not a Response
A timed-out workflow can record that no reply arrived. It cannot explain why without further evidence. Keep delivery, action and default outcomes separate.
-
Field Note 086: The Unanswered Notice
A blue receipt says the traveler accepted the station decision. Mara finds that nobody pressed accept: the response window simply expired.
-
Operator Brief: Test a Notice Chain
Use synthetic cases to trace a notice from issuance to response, including inaccessible accounts, duplicate alerts, fallback privacy, and recovery.
-
Intel Report 072: Notice as Infrastructure
Notice is part of a service, not an accessory to it. Examine the tradeoffs between reachability, privacy, acknowledgment, and the opportunity to respond.
-
Field Note 074: The Unread Decision
A fictional transit review exposes the gap between issuing a decision and giving its recipient a usable chance to respond.