Opportunity Scoring Rubric
A weighted scoring method for value, feasibility, risk and data readiness that ranks every opportunity and sets the Year-1 department sequence.
What this is for
Every organization finds more opportunities than it can deliver in a year. Without a shared method, the loudest department goes first, not the one with the best return. This rubric scores each opportunity on four dimensions, makes the trade-offs visible, and produces two deliverables: the scored Opportunity Inventory and the Ranked Opportunity Roadmap with the Year-1 department sequence. It also sets the starting autonomy level for each opportunity, so risk is designed in from the first day.
When to use it
After problem statements are confirmed and the Systems & Workflow Map is drafted for priority departments. Re-score at every quarterly business review, and when a new department joins the roadmap.
Who's involved
- Solutions Architect Clone: produces first-pass scores with the evidence behind each.
- Implementation Engineer: checks feasibility scores.
- InfoSec lead: checks risk scores and can veto.
- Business owners: check value scores for their departments.
- Steering committee: approves the ranking and sequence.
How to fill it in
- Load every candidate opportunity from the Problem Statement Register and the workflow maps into the inventory.
- Score each dimension 1–5 using the scales below. Write one line of evidence for every score.
- Apply the weights. The default weights are below; the steering committee may change them once, before scoring, not after.
- Apply the gates. Any opportunity that fails a gate is parked, whatever its score.
- Plot the top opportunities on the value-versus-feasibility grid to sanity-check the ranking.
- Group ranked opportunities by department and propose the Year-1 sequence: two departments in parallel, about six weeks per rollout.
- Review with InfoSec and business owners, then take it to steering for approval.
The template
Scoring scales
Value (V): what it's worth if it works
| Score | Definition |
|---|---|
| 1 | Under 0.25 FTE of effort or negligible business impact |
| 2 | 0.25–1 FTE, or minor quality improvement |
| 3 | 1–3 FTE, or measurable cycle-time or error reduction on a core process |
| 4 | 3–8 FTE, or direct revenue, cash or customer-experience impact |
| 5 | Over 8 FTE, or strategic impact named by the executive sponsor |
Feasibility (F): how hard it is to build and run
| Score | Definition |
|---|---|
| 1 | Systems lack APIs; heavy custom build; unclear process |
| 2 | Custom skill needed and at least one system integration is uncertain |
| 3 | Custom skill or integration needed; systems have APIs |
| 4 | Marketplace template fits with configuration; connectors exist |
| 5 | Existing skills and connectors cover it; process is stable and documented |
Risk (R): what happens if the Clone gets it wrong (higher score = lower risk)
| Score | Definition |
|---|---|
| 1 | Customer-facing or regulated decision; errors are hard to reverse |
| 2 | Touches Restricted data or financial postings; reversible with effort |
| 3 | Internal impact; Confidential data; errors caught by existing review |
| 4 | Internal drafts and recommendations; easy to reverse |
| 5 | Read-only, internal, Public or Internal data only |
Data readiness (D): can the Clone work from the truth
| Score | Definition |
|---|---|
| 1 | Data or knowledge does not exist in usable form |
| 2 | Exists but scattered, conflicting or outdated |
| 3 | Mostly available; some cleanup needed before go-live |
| 4 | Available and current; minor gaps |
| 5 | Clean, current, owned and accessible through approved connections |
Weights and formula
| Dimension | Default weight | Agreed weight |
|---|---|---|
| Value | 40% | |
| Feasibility | 25% | |
| Risk | 20% | |
| Data readiness | 15% |
Priority score = (V × wV + F × wF + R × wR + D × wD) × 20, giving a score out of 100.
Gates (any "No" parks the opportunity)
- Has a confirmed problem statement with an executive owner
- A business owner and a likely champion exist
- InfoSec sees no blocking risk at the proposed starting autonomy level
- Required data can be accessed under the Connections & Permissions Plan
- No conflicting in-flight project
Opportunity Inventory
| ID | Opportunity | Department | Problem ID | V | F | R | D | Score | Gates pass? | Starting autonomy | Target autonomy (12 mo) | Build path | Evidence notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OP-01 | Marketplace / Configure / Custom | ||||||||||||
| OP-09 | AP invoice-to-PO matching | Finance | PS-004 | 4 | 4 | 3 | 3 | 73 | Yes | Recommend | Execute within limits (matched invoices under tolerance) | Configure + one custom skill | ~3 FTE; ERP API exists; tolerance rules need one approved version |
Worked score for OP-09: (4 × 0.40 + 4 × 0.25 + 3 × 0.20 + 3 × 0.15) × 20 = (1.60 + 1.00 + 0.60 + 0.45) × 20 = 73. If the steering committee overrides a calculated score, record the original score, the new score and the reason.
Starting autonomy guide
| Risk score | Suggested starting level | Typical first promotion |
|---|---|---|
| 1 | Assist | Recommend, after 60+ days of evidence |
| 2 | Assist or Recommend | Execute with approval |
| 3 | Recommend | Execute with approval |
| 4 | Recommend or Execute with approval | Execute within limits |
| 5 | Execute with approval | Execute within limits |
Every promotion still needs evidence and sign-off from InfoSec and the business owner.
Value-versus-feasibility grid
| Feasibility 1–2 | Feasibility 3 | Feasibility 4–5 | |
|---|---|---|---|
| Value 4–5 | Plan: strategic build | Next wave | Do first |
| Value 3 | Park | Backlog | Quick win |
| Value 1–2 | Drop | Park | Quick win if cheap to run |
Ranked roadmap and Year-1 department sequence
| Slot | Weeks | Department A | Department B | Top opportunities | Champion | Dependencies |
|---|---|---|---|---|---|---|
| 0 | 1–4 | InfoSec | Security questionnaire response, policy Q&A | |||
| 1 | 5–10 | |||||
| 2 | 9–14 | |||||
| 3 | 13–18 | |||||
| 4 | 17–22 | |||||
| 1 | 5–10 | Finance | Customer Support | OP-09, OP-11; OP-03 | Senior AP specialist; Support team lead | ERP service account approved |
Good looks like
- Every score has a line of evidence. A score without evidence is an opinion.
- Weights are set before scoring, not adjusted afterward to move a favorite up.
- InfoSec's veto is used early, not discovered in Design week.
- The first department mixes value and speed. A high-value, high-feasibility win in Weeks 5–10 funds trust for harder work.
- Non-Clone answers stay in. Some top opportunities are automation, data cleanup or another AI tool. Clone-first, not Clone-only.
- Common mistake: ranking by department politics. Rank opportunities first, then group them into departments.
How Clone helps
The Solutions Architect Clone produces first-pass scores from the workflow maps and problem statements, cites evidence for each, and recalculates when inputs change. The Project Clone turns the approved ranking into the roadmap and schedules department rollouts. In the portal, the inventory and ranked roadmap are the Opportunity Inventory and Ranked Opportunity Roadmap deliverables under Opportunity & Roadmap; steering approval is recorded against both.
Sign-off
| Role | Name | Date | Decision |
|---|---|---|---|
| InfoSec lead | Risk scores accepted / Vetoes noted | ||
| Executive sponsor | Ranking approved | ||
| Steering committee | Year-1 sequence approved |