To prioritize AI use cases, score each candidate on value, effort, and risk, then start with the one that is high value, low effort, and low risk. This avoids the common trap of picking the most exciting idea instead of the one most likely to pay off quickly. The idea that generates the most enthusiasm in a meeting is often the worst place to start, because ambitious, customer-facing ideas tend to be high-effort and high-risk, exactly the combination that stalls. A scoring method protects you from your own excitement by putting every candidate through the same lens. This guide gives you a simple way to list candidates, a three-dimension scoring approach, and a rule for choosing the first project so you build a reliable win before attempting anything bold.
List candidates before you score
Gather ideas from the people doing the work. Frequent, repetitive, text-heavy tasks are usually the best starting candidates. Our 30-minute AI audit is a fast way to build this list.
Score each use case
Rate every candidate one to five on three dimensions. The simplest priority score is value divided by effort, with risk as a veto.
- Value: how much time, output, or quality this could improve.
- Effort: setup, integration, and learning required.
- Risk: what happens if AI gets it wrong here.
Start in the sweet spot
The first project should be high value, low effort, and low risk. Save the ambitious, risky ideas for after you have a proven win and your team trusts the process. The McKinsey research on generative AI points to large potential across functions, but capturing it depends on disciplined choices, not chasing every idea.
A scoring table you can copy
- Columns: use case, value (1-5), effort (1-5), risk (1-5), notes.
- Priority score: value divided by effort.
- Rule: any high-risk item needs a review plan before it qualifies.
- Pick the top low-risk item to start.
Re-score as you learn
Your first project will teach you what effort and risk really look like in your business. Update the scores and revisit the list each quarter so prioritization stays grounded in reality.
Watch out for the exciting-but-wrong idea
The use case that generates the most enthusiasm in a meeting is often the worst place to start. Ambitious, customer-facing, or revenue-changing ideas tend to be high-effort and high-risk, exactly the combination that stalls. A scoring method protects you from your own excitement by forcing each idea through the same value, effort, and risk lens. When the spreadsheet points to a humble task, trust it; a small reliable win earns you the credibility to attempt the bold idea later.
It also helps to involve the people who actually do the work in the scoring. They know which tasks are genuinely repetitive, where the hidden complexity lives, and what would break if AI got it wrong. Their input keeps your effort and risk estimates honest, and it builds buy-in for whatever you choose. Broad research such as the McKinsey State of AI survey consistently links value to disciplined choices and engaged teams rather than to the flashiest project.
Keep a running backlog
Ideas that do not make the cut today are not wasted; they belong in a backlog you revisit each quarter. As you complete projects, your sense of effort and risk sharpens, tools improve, and yesterday's high-effort idea may become tomorrow's easy win. A living backlog turns prioritization from a one-time exercise into an ongoing practice, and it means you always have a vetted next candidate ready when capacity opens up. Pair it with our 30-minute AI audit to keep the list fresh.
How do I choose my first AI project? +
Score candidates on value, effort, and risk, then start with the one that is high value, low effort, and low risk.
Should I pick the most impressive idea? +
No. Impressive ideas are often high-effort and high-risk. A smaller, reliable win builds trust and momentum faster, and it earns you the credibility to attempt the bold idea later, once you have evidence and a team that trusts the process.
How many use cases should I score? +
Gather as many as you can, but commit to only one to start. Finishing one beats starting five. Keep the rest in a backlog you revisit each quarter, since your sense of effort and risk sharpens with experience and yesterday's hard idea can become tomorrow's easy win.
How often should I revisit priorities? +
Quarterly, or after each completed project, since real effort and risk become clearer once you have experience.