| name | priority-triage |
| description | Triage competing work using urgency, impact, dependencies, capacity, and cost of delay while keeping ownership explicit. |
Priority Triage
Use when multiple requests compete for limited execution capacity.
Procedure
- Normalize each request into an outcome, owner, deadline or time sensitivity, and consequence of delay.
- Identify hard dependencies and work that unblocks multiple downstream items.
- Separate true urgency from loudness. Note regulatory, security, outage, contractual, or irreversible deadlines explicitly.
- Estimate effort only to the precision needed for sequencing; avoid false certainty.
- Rank work using impact, cost of delay, risk reduction, and dependency leverage.
- Expose conflicts where the same owner or resource is overcommitted.
- Produce a clear ordered queue with reasons and identify which items are deliberately deferred.
- Re-triage when assumptions or deadlines materially change.
Quality gate
A priority decision is good when the ordering is explainable from consequences and constraints, not from who asked most recently.