Mentions, assignments, and observed events need different default intensities

What it is

Role-sensitive notification priority assigns default intensity from the recipient's relation to an event. An assignment usually signals an obligation awaiting confirmation, a mention requests attention or response, and an observed update provides ambient awareness. Giving all three the same sound, badge, and implied deadline destroys that distinction.

Why it happens

Notification intensity allocates interruption cost. Missing a direct obligation is often costly, while observed updates are numerous and less time-sensitive. Amplifying everything produces alert fatigue; muting everything hides commitments. Role supplies an initial priority, which urgency, reversibility, and current availability must then qualify.

Studying it

Manipulate event relation and delivery channel, measuring response latency, misses, inappropriate interruptions, switching cost, and priority judgments. Scenarios should separate actual urgency from sender-applied labels so sender preference is not mistaken for objective importance. Role-stratified analysis can reveal whether defaults concentrate coordination burden.

Where it stops holding

A mention may be ceremonial, while an observed change may alter a critical dependency. Event labels cannot replace context. A pending assignment must not be rendered as an accepted commitment. Accessibility needs, on-call arrangements, and individual work practices also change appropriate channels and intensity.

Applying it

• Give assignments, mentions, and followed updates different default channels, persistence, and digest eligibility.
• State the triggering relationship and expected action inside the notification.
• Allow event- and status-specific overrides while retaining narrowly defined safety exceptions.
• Review responses, misses, and interruption cost; faster clicks alone do not validate prioritization.

Related

• Same group: V4.03.1 Object-level subscription · V4.03.3 Default subscription scope · V4.03.4 Scheduled digests · V4.03.5 In-notification unsubscribe
• Adjacent: V4.02 Task Assignment and Claiming · V2.08 Availability and Willingness to Be Interrupted
• Search terms: notification priority · role-sensitive alerts · interruption management