Assessment Playbooks
Prioritization Rubric
Prioritization turns discovery findings into an ordered backlog. Rank work by risk reduction and execution reality, not by which tool is most interesting.
Scoring factors
Score each proposed item from 1 to 5.
| Factor | Question |
|---|---|
| Impact | How much customer, business, security, or operational risk changes? |
| Urgency | What happens if this waits 90 days? |
| Confidence | How strong is the evidence? |
| Effort | How much time, coordination, and migration work is required? |
| Reversibility | Can we undo or adjust this safely? |
| Enablement | Does this unblock other valuable work? |
Ranking formula
A simple starting formula:
priority = (impact + urgency + confidence + enablement)
- effort
+ reversibilityUse the number to start the conversation, not end it. Executive commitments, compliance deadlines, and incident follow-up may override pure scoring.
Backlog item shape
Every ranked item should include:
- Problem statement.
- Evidence or source.
- Owner.
- Expected impact.
- First reversible step.
- Dependencies.
- Risk of not doing it.
- Definition of done.
Sequencing rules
- Stabilize risky production systems before large migrations.
- Fix missing observability before optimizing reliability.
- Fix ownership gaps before adding advanced tooling.
- Prefer reversible platform improvements early.
- Avoid broad rewrites unless incremental risk reduction is impossible.
Review cadence
Re-rank after discovery, after major incidents, before quarterly planning, and whenever new evidence invalidates the original ordering.