Problem Prioritization: Decide What to Solve First
Good prioritization compares verified problems against explicit decision criteria and preserves hard obligations before ranking discretionary work.
How to prioritize problems
Separate mandatory work from discretionary choices, then describe each problem with the same evidence window. Compare impact, urgency, affected people, confidence, tractability, dependencies, and the cost of delay. Use a score as a discussion aid, not an automatic decision, and run a sensitivity check before committing resources.
Problem prioritization compares verified gaps while protecting mandatory obligations and making impact, urgency, evidence, and uncertainty visible.
Key relationships
- An obligation gate places mandatory work outside a discretionary score.
- A criterion represents one stated reason a problem should move in the queue.
- A sensitivity check shows whether uncertain ratings can reverse the priority order.
Prioritize a backlog without hiding the evidence
A service team has three verified gaps and capacity for one investigation. A simple total can start the comparison, but obligation gates, evidence confidence, and sensitivity decide whether that total deserves trust.
| Problem | Impact | Urgency | Evidence | Dependency | Decision note |
|---|---|---|---|---|---|
| Accessibility barrier blocks form submission | High | High | Direct reports and reproduced failure | None | Mandatory access issue, act before scoring |
| Weekly report arrives late | Medium | Low | Timestamp history | Data pipeline review | Investigate after the blocking issue |
| Search results feel inconsistent | Unknown | Medium | Anecdotal reports | Needs query sample | Gather evidence before ranking |
The accessibility barrier is not allowed to lose because another issue receives a larger weighted total. The report delay is well evidenced but has lower cost of delay. The search concern is not automatically low priority; it is insufficiently defined, so a small evidence task belongs in the queue before a large fix.
Create a decision record
- Name the obligation or criterion that drove the choice.
- Cite the evidence date and acknowledge important unknowns.
- Assign the next action and a capacity boundary.
- State what change would trigger reprioritization.
Build a comparable problem register
Write each candidate as a measurable gap rather than a solution request. Include affected group, current condition, expected condition, evidence date, impact, owner, and known constraints. Items cannot be compared fairly when one has detailed evidence and another is only a persuasive label.
Split large problems when their causes, populations, or decisions differ. Merge duplicates that describe the same underlying gap. This prevents one issue from receiving several votes under different names and makes ownership clearer.
Protect obligations before scoring
Legal, safety, contractual, or severe harm thresholds may require action regardless of a portfolio score. Mark these gates first and record the authority or evidence behind them. A weighted average must not trade away a non-negotiable duty.
Also identify incidents that need containment now while investigation continues. Urgent containment and long-term correction are different work items and can have different priorities.
Choose criteria with anchored meanings
Impact can include number affected, severity, frequency, duration, inequity, cost, and strategic consequence. Urgency describes how the consequence changes with delay. Confidence describes evidence quality, not how strongly a sponsor believes the story.
Tractability estimates whether a bounded action can improve the outcome with available time, access, and capability. Dependencies can raise priority when one fix unlocks several others, or delay work that cannot begin until a prerequisite is complete.
Compare scores without surrendering judgment
Use short anchored scales and preserve the component ratings. Two problems can receive the same total for very different reasons. Review the profile, uncertainty, and who bears the cost rather than sorting by a hidden decimal.
Run a sensitivity check by varying uncertain ratings and reasonable weights. If the top item changes easily, the portfolio is not ready for a confident ranking. Gather the evidence that could change the decision or choose a reversible first step.
Turn the ranking into a reviewable queue
Assign an owner, next action, capacity limit, and review trigger to selected work. Record why lower items were deferred and what new evidence would move them. A ranked list without capacity or decision records becomes a wish list.
Revisit the queue when impact, obligations, dependencies, or evidence change. Do not rescore simply to protect an earlier choice. The purpose of the system is to direct attention to current value and risk, not to make priorities look stable. Keep completed and rejected items in the decision history so the same proposal does not return without new evidence.
Connect prioritization to definition and comparison
Use the testable problem statement guide to make every backlog item comparable before ranking.
When several discretionary options survive, calculate a transparent comparison with the weighted decision matrix.
Map weak evidence behind a high priority with assumption mapping.