- Purpose
- Tell an actor about something that happened while they were not looking.
- Operational principle
- If something happens that concerns a member who did not cause it, the system records a notice for them; when they next attend, they find the notice and can follow it to the item it is about.
- State
notified: User -> set Item
- Actions
notify The system records a notice for a member about an item.
- Misfits
- A notice that arrives in the middle of other work costs attention whether or not it was worth it; the concept says nothing about when it is delivered.
- Notices pile up when nothing clears them, and a long backlog is read as noise rather than as a record.
- The same event can reach an actor through several channels at once, each with its own notice.
- A notice about the system itself (planned downtime, an outage) has no item to follow to, and the concept as held here has nowhere to put it.
- Also called
- alert, notification, ping
- Appears in
- Slack, GitHub, Linear, iOS and Android system notifications
Patterns that act on it
- Notification
— delivery, urgency, and timing ahead of a limit; the concept itself says nothing about when a notice arrives