How to use this framework
Score each candidate workflow from 1 to 5 against the six criteria below. Multiply the score by the weighting, compare the total score, then use the result to decide whether to move, prepare, hold, or stop.
Scoring criteria
25%
Business value
Will the use case improve revenue, cost, speed, quality, risk, customer experience, or leadership decision-making?
- High: Clear measurable value and a visible sponsor.
- Low: Interesting idea but weak business consequence.
20%
Feasibility
Can the workflow be described, scoped, piloted, and supported with current tools or a practical build path?
- High: Inputs, outputs, process steps, and users are clear.
- Low: The workflow is ambiguous or depends on major system changes first.
20%
Data readiness
Are the documents, data sources, permissions, quality standards, and ownership clear enough for a pilot?
- High: Sources are known, accessible, and trusted enough for a controlled pilot.
- Low: Data is scattered, duplicated, sensitive, or missing clear ownership.
15%
Risk and governance
Can the team define acceptable use, human review, exception handling, privacy, and escalation boundaries?
- High: Risk boundaries and accountable owners are clear.
- Low: The use case could affect sensitive decisions without defined controls.
10%
Adoption effort
Can the target users realistically adopt the new workflow with training, templates, and manager support?
- High: Users feel the pain and can see how the workflow improves their day.
- Low: Adoption depends on behavior change with no clear support model.
10%
Operating ownership
Is there a business owner who will sponsor, test, approve, measure, and improve the workflow?
- High: Named owner, decision rights, and success measures exist.
- Low: The idea has interest but no accountable operator.
Score interpretation
| Score | Decision | Guidance |
|---|---|---|
| 80-100 | Move first | Strong candidate for discovery-to-pilot. Define success metrics, data requirements, risk boundaries, and a build path. |
| 60-79 | Prepare then pilot | Promising but needs cleanup, tighter scope, stakeholder alignment, or data foundations before implementation. |
| 40-59 | Hold for later | Useful idea, but not the best first use case. Revisit after higher-readiness workflows have moved. |
| 0-39 | Do not prioritize | Low readiness, weak value, unclear owner, or high governance burden. Document the idea but do not fund it now. |
Recommended scoring process
- List the candidate workflows, not just AI ideas.
- Score each workflow against the six criteria using a 1-5 scale.
- Apply the weightings to calculate a first-pass score.
- Discuss disagreements between business, technology, risk, and user groups.
- Select one first-move workflow and write a short pilot brief.
- Define the build path: assisted workflow, shared AI workspace, or API workflow pipeline.
Next step
If the scorecard reveals one strong candidate, convert it into a pilot brief with a workflow owner, success measure, data requirement, risk boundary, and build path.