Clone Solutions
Template

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

  1. Load every candidate opportunity from the Problem Statement Register and the workflow maps into the inventory.
  2. Score each dimension 1–5 using the scales below. Write one line of evidence for every score.
  3. Apply the weights. The default weights are below; the steering committee may change them once, before scoring, not after.
  4. Apply the gates. Any opportunity that fails a gate is parked, whatever its score.
  5. Plot the top opportunities on the value-versus-feasibility grid to sanity-check the ranking.
  6. Group ranked opportunities by department and propose the Year-1 sequence: two departments in parallel, about six weeks per rollout.
  7. 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

ScoreDefinition
1Under 0.25 FTE of effort or negligible business impact
20.25–1 FTE, or minor quality improvement
31–3 FTE, or measurable cycle-time or error reduction on a core process
43–8 FTE, or direct revenue, cash or customer-experience impact
5Over 8 FTE, or strategic impact named by the executive sponsor

Feasibility (F): how hard it is to build and run

ScoreDefinition
1Systems lack APIs; heavy custom build; unclear process
2Custom skill needed and at least one system integration is uncertain
3Custom skill or integration needed; systems have APIs
4Marketplace template fits with configuration; connectors exist
5Existing skills and connectors cover it; process is stable and documented

Risk (R): what happens if the Clone gets it wrong (higher score = lower risk)

ScoreDefinition
1Customer-facing or regulated decision; errors are hard to reverse
2Touches Restricted data or financial postings; reversible with effort
3Internal impact; Confidential data; errors caught by existing review
4Internal drafts and recommendations; easy to reverse
5Read-only, internal, Public or Internal data only

Data readiness (D): can the Clone work from the truth

ScoreDefinition
1Data or knowledge does not exist in usable form
2Exists but scattered, conflicting or outdated
3Mostly available; some cleanup needed before go-live
4Available and current; minor gaps
5Clean, current, owned and accessible through approved connections

Weights and formula

DimensionDefault weightAgreed weight
Value40%
Feasibility25%
Risk20%
Data readiness15%

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

IDOpportunityDepartmentProblem IDVFRDScoreGates pass?Starting autonomyTarget autonomy (12 mo)Build pathEvidence notes
OP-01Marketplace / Configure / Custom
OP-09AP invoice-to-PO matchingFinancePS-004443373YesRecommendExecute 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 scoreSuggested starting levelTypical first promotion
1AssistRecommend, after 60+ days of evidence
2Assist or RecommendExecute with approval
3RecommendExecute with approval
4Recommend or Execute with approvalExecute within limits
5Execute with approvalExecute within limits

Every promotion still needs evidence and sign-off from InfoSec and the business owner.

Value-versus-feasibility grid

Feasibility 1–2Feasibility 3Feasibility 4–5
Value 4–5Plan: strategic buildNext waveDo first
Value 3ParkBacklogQuick win
Value 1–2DropParkQuick win if cheap to run

Ranked roadmap and Year-1 department sequence

SlotWeeksDepartment ADepartment BTop opportunitiesChampionDependencies
01–4InfoSecSecurity questionnaire response, policy Q&A
15–10
29–14
313–18
417–22
15–10FinanceCustomer SupportOP-09, OP-11; OP-03Senior AP specialist; Support team leadERP 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

RoleNameDateDecision
InfoSec leadRisk scores accepted / Vetoes noted
Executive sponsorRanking approved
Steering committeeYear-1 sequence approved