Level definitions need consistency across products to avoid different meanings
Aliases: alarm consistency · urgency governance
What it is
Cross-product alarm semantics requires a given urgency level to convey comparable response deadline, impact, and ownership across products, devices, and teams—not merely a shared label or color. People working across interfaces must be able to transfer learned priority.
Why it happens
Semantic inconsistency forces relearning and lets “high” in one product be treated as “routine” in another. Shared audio without shared action rules is equally risky: sound-triggered expectation conflicts with actual workflow.
Studying it
Ask cross-product users, without documentation, to choose deadline, owner, and action from alerts. Compare transfer error and training cost. Audit teams’ event definitions, routing, and escalation records for same-named levels with different treatment.
Where it stops holding
Consistency does not erase business difference. Products may retain local causes and detail, but must state how they map to the shared response layer.
Applying it
- Maintain a shared level dictionary: deadline, impact, default route, sound features, and downgrade rules.
- Create explicit mappings for exceptions rather than privately reusing a name.
- Recheck semantic consistency in design review, asset libraries, and operational retrospectives.
Related
Cards in the same group
- D2.03.1Urgency should be expressed through pitch, speed, and repetition
- D2.03.2The number of urgency levels should not exceed discriminable range
- D2.03.3If every sound is equally urgent, none is
- D2.03.4Three to four urgency levels are common; too many become hard to distinguish
- D2.03.5Each level needs stable timbre and rhythm combinations, not arbitrary mixes
- D2.03.6Long-unhandled alarms should escalate to a higher level of expression