Priority labels without response protocols are decoration…
Attach specific response protocols (timing, resources, escalation) to each priority type rather than treating them as descriptive labels, making priority actionable.
When This Fires
- Designing a new priority system
- When existing priority labels don't produce different behaviors
- During triage when people agree on the label but not on what it means for response
- When "critical" items sit unaddressed because the label has no behavioral implications
Common Failure Mode
Defining priorities by description rather than response: "Critical = very important and urgent." That describes the feeling but not the action. The description doesn't tell anyone what to do differently. Protocol-based: "Critical = interrupt current sprint work, assign within 4 hours, daily status updates until resolved." Now the label triggers a specific behavioral sequence.
The Protocol
For each priority level: (1) Define timing: how quickly does work begin after assignment? (2) Define resources: who is assigned, how many, what seniority? (3) Define escalation: if unresolved within [timeframe], who gets notified and what additional resources are allocated? (4) Post the protocols where they're visible during triage. Priority labels are only useful if they trigger differentiated responses.