Incident Priority vs Urgency: Different

Both matter; they're different. The distinction.

Priority

Priority is the magnitude axis. How important; how many customers; how much revenue at stake.

• How important. Per-incident impact magnitude; high priority means many customers, high revenue.
• Reflects the magnitude. Per-incident size dimension; drives staffing and exec attention.
• Per-incident named priority owner. Per-incident responsible exec; supports accountability for high-priority cases.
• Per-incident customer-segment cut. Per-tier priority weighting; enterprise-versus-free customers carry different priority.

Urgency

Urgency is the rate axis. How fast it's getting worse; how soon you must act.

• How fast. Per-incident rate-of-change view; high urgency means degrading rapidly.
• Reflects rate of change. Per-incident trajectory dimension; drives the timing of response, not its size.
• Per-incident named urgency trigger. Per-incident "if it doubles in 10 minutes" gate; catches accelerating incidents.
• Per-metric rate-of-change alarm. Per-metric burn-rate watch; supports early urgency detection.

Matrix

The matrix combines the two axes. Each quadrant has a different response posture.

• High priority + high urgency. Per-incident drop-everything response; war room, all-hands.
• High priority + low urgency. Per-incident scheduled-work plan; important but not racing the clock.
• Low priority + high urgency. Per-incident contain-the-spread posture; stop it growing into high priority.
• Low priority + low urgency. Per-incident backlog disposition; tracked but not active.