Quick Wins vs. Transformational Bets
Sequencing your AI portfolio
- Be able to distinguish a quick win from a transformational bet by their structural traits, not their hype
- Be able to plot candidate use cases on a value-by-feasibility matrix and read off the right sequencing decision
- Be able to defend why a portfolio should concentrate on two or three high-value vertical workflows rather than dozens of pilots
- Be able to set a portfolio-horizon budget allocation and explain why most spend belongs in near-term productivity first
- Be able to recognize and stop the most common sequencing error: launching autonomous agents before data and governance foundations exist
- Be able to ask the right diagnostic questions before approving any use case for the portfolio
Most AI value is captured by leaders who sequence it deliberately: a portfolio of repeatable, measurable quick wins first to build credibility and cash flow, then a small number of transformational, end-to-end bets that require data and governance foundations. This lesson gives you the sequencing logic, the value-by-feasibility matrix to prioritize with, and the discipline to concentrate on two or three high-value workflows rather than scattering scores of shallow pilots. The recurring failure mode is reaching for autonomous agents before the data and governance to run them safely even exist.
- 1The real question isn't 'which use case' — it's 'in what order'
- 2Two categories: quick wins and transformational bets
- 3The tool: a value-by-feasibility matrix
- 4Concentrate on two or three bets, not scores of pilots
- 5Budgeting the portfolio: horizons and the 10-20-70 reality
- 6The cardinal rule: don't start with agents
- 7Putting it together: a sequencing playbook
The real question isn't 'which use case' — it's 'in what order'
Every leader gets the same pitch deck: a dozen exciting AI use cases, each with a big number attached. The instinct is to pick the most ambitious one and go. That instinct is exactly how organizations end up in the value gap.
The data is blunt about this. As of 2025, near-universal adoption has not translated into value: McKinsey's State of AI (Nov 2025) found roughly 88% of organizations use AI in at least one function, yet only about 39% report enterprise-level EBIT impact. MIT's NANDA study (July 2025) was harsher still — about 95% of enterprise generative-AI pilots delivered no measurable P&L return, and the root cause was a learning gap in workflow and integration, not weak models. BCG's Widening AI Value Gap (Sept 2025) put just 5% of firms in the 'future-built' category capturing value at scale, against 60% 'laggards.'
The lesson buried in those numbers is about sequencing. Value isn't lost because leaders pick bad use cases; it's lost because they pick them in the wrong order — chasing a multi-year transformation before the organization has earned the credibility, the data foundations, or the change-management muscle to deliver it. The discipline this lesson teaches is portfolio sequencing: start where the odds are good, build the muscle, then spend that earned credibility on the bets that actually move the business.
Key insight
The reframe
AI value is not a use-case-selection problem; it is a sequencing problem. The same use case that fails as your first move can succeed as your fifth, once you have credibility, data, and a change-management track record to draw on.
Watch out
Where leaders get it wrong
Launching the flagship 'transformation' first — the splashy end-to-end agentic workflow — before any quick wins have proven the operating model. When it stalls (and ~95% of pilots showed no P&L return as of 2025), the whole AI program loses its mandate.
Two categories: quick wins and transformational bets
Almost every AI opportunity falls into one of two buckets. Telling them apart by their structure — not by how exciting they sound — is the first skill.
Quick wins are bounded, repeatable tasks with structured inputs, a clear success metric, a human in the loop, and fast feedback. They make an existing task faster (a copilot, in the chatbot/copilot/agent vocabulary). Examples leaders should recognize: customer-support assist, internal knowledge search, coding assistance, marketing-content drafting, finance reporting and close acceleration, and meeting/document summarization. These are well-evidenced: as of 2023, the NBER study of 5,179 support agents (Brynjolfsson, Li & Raymond) found a gen-AI assistant raised issues resolved per hour by ~14% on average and ~34% for novices; the 2023 GitHub Copilot RCT found developers finished a coding task ~55.8% faster.
Transformational bets are end-to-end agentic workflows that redesign how a core function operates — claims, underwriting, supply chain, the full customer journey — or entirely new AI-native products. They deliver a step change in value, but they do the task rather than merely speed it up (an agent: more value, more risk, more process redesign). They require data foundations, governance, change management, and multi-year ambition before they pay off.
| Trait | Quick win | Transformational bet |
|---|---|---|
| What it changes | Makes an existing task faster | Redesigns how the work is done end-to-end |
| Steering pattern | Copilot — human in the loop every step | Agent — human on the loop / escalation point |
| Inputs | Structured, repeatable | Spans messy systems and data |
| Success metric | Clear and immediate (time, resolution rate) | Composite and lagging (EBIT, cycle time) |
| Prerequisites | Off-the-shelf tools; little redesign | Data, governance, workflow redesign, change mgmt |
| Time to value | Weeks to a quarter | Often 2–4 years (Deloitte, 2026) |
| Risk if it fails | Contained, reversible | Large, visible, mandate-threatening |
Neither is 'better.' A portfolio needs both — but in sequence, with quick wins establishing the credibility and the operating muscle the bets will consume.
Tip
The leadership move
When a use case is pitched, ask one diagnostic question: Does this make an existing task faster, or does it redesign the work end-to-end? The answer tells you which bucket it's in, which prerequisites it needs, and roughly when you should sequence it — before you ever look at the ROI slide.
Example
Customer support: the canonical quick win
Support assist is the best-proven quick win precisely because it has every quick-win trait: a structured knowledge base, repeatable queries, an obvious metric (resolution rate, handle time, CSAT), and a human in the loop. The NBER field study (2023) measured a ~14% average and ~34% novice lift. Just remember the Klarna lesson covered later in this module — track quality (CSAT/NPS), not just volume.
The tool: a value-by-feasibility matrix
To turn a list of opportunities into a sequence, plot each one on two axes: business value (impact on revenue, cost, customer experience, or risk) and feasibility (how ready your data, tools, and processes are, and how low the effort and risk to deliver). This is the value-by-feasibility (impact/effort) 2×2 that the strategy module introduced.
| Low feasibility (hard, not ready) | High feasibility (ready, low effort) | |
|---|---|---|
| High value | Transformational bets — sequence later. Build the data and governance foundations first, then invest to own. | Quick wins — start here. Highest-priority: real impact, deliverable now, builds credibility. |
| Low value | Avoid / park. Expensive and low-return — the classic resource sink that drowns AI programs in shallow pilots. | Fill-ins / 'because we can.' Cheap but minor; do opportunistically, never as the flagship. |
The sequencing logic falls straight out of the grid:
- Start in the top-right (high value, high feasibility) — your quick wins. They build credibility and cash flow.
- Then deliberately move toward the top-left (high value, low feasibility) — your transformational bets — after using the quick-win period to raise feasibility: clean and govern the data, stand up the operating model, build change-management capability.
- Starve the bottom-left. Low-value, low-feasibility work is where AI budgets quietly die.
The matrix is not a one-time exercise. Feasibility moves as capabilities and your own foundations improve, so re-plot the portfolio quarterly — a high-value bet that was infeasible last year may have become a quick win this year.
Key insight
Sequencing is movement across the grid
Don't read the matrix as four static boxes. Read it as a path: deliver top-right quick wins to earn credibility and raise feasibility, which moves your top-left bets within reach. The quick wins are how you afford the bets — politically, operationally, and financially.
Watch out
The bottom-left trap
Low-value, low-feasibility pilots feel like progress because they're 'doing AI.' MIT NANDA (2025) found that misallocated, disconnected pilots are the dominant pattern in the ~95% that show no P&L return. If a use case is neither high-value nor feasible, the correct decision is to park it — not to run it as a learning exercise.
Concentrate on two or three bets, not scores of pilots
The single most common strategic error in AI portfolios is spreading too thin: launching scores of disconnected pilots, each consuming resources and attention, none reaching the scale where value compounds. BCG's research is explicit that focus beats breadth — winners run a few important workflows end-to-end rather than many shallow experiments.
McKinsey's prescription for capturing agentic value (its 'four pillars') is the durable version of this discipline. Winners:
- Pick 2–3 high-value vertical use cases — not a long horizontal menu of copilots bolted onto every team.
- Embed AI into reimagined workflows — redesign the process, don't layer AI onto the broken one. (McKinsey finds workflow redesign has the single biggest effect on EBIT impact.)
- Scale with the right foundations — infrastructure, cross-functional teams, and strong governance.
- Build a new skills mix — reskill the people who run the redesigned work.
Why concentration wins: value compounds only past a threshold of scale and integration, and leadership attention is the scarcest resource of all. Three workflows you take all the way to production beat thirty pilots that each stall at 'interesting demo.' This is also why the gen-AI paradox persists — as of 2025, ~80% of firms used gen AI yet ~80% reported no material P&L impact, because effort sat in shallow horizontal copilots instead of a few deep vertical workflows.
Tip
The leadership move
Cap your transformational bets at two or three and put a named executive sponsor on each. If a fourth 'must-have' bet appears, it doesn't get added — it competes with the existing three for the slot. Scarcity of slots forces the prioritization that scarcity of money should have.
Example
JPMorgan: scoped, not scattered
JPMorgan runs 450+ AI use cases in production with benefits reported growing roughly 30–40% year over year — the opposite of a single moonshot. The lesson isn't 'run hundreds of pilots'; it's that each use case is scoped, KPI-anchored, and tied to a clear owner and metric. Volume only works when every item is disciplined; scattered, unmeasured pilots are the failure mode, not the model.
Budgeting the portfolio: horizons and the 10-20-70 reality
A sequenced portfolio needs a budget shape, not just a use-case list. Two framings keep the money honest.
Portfolio horizons. Allocate roughly ~60% to near-term productivity (quick wins that pay back fast), ~30% to capability-building (the data, governance, and platform work that makes the bets feasible), and ~10% to exploration (early experiments on what's next). Re-prioritize quarterly as capabilities and feasibility shift. The point of the split is to fund the foundations now — the 30% — so that high-value bets become deliverable later rather than staying perpetually 'not ready.'
The 10-20-70 reality check. BCG's 10-20-70 rule is the most important budgeting insight a leader can internalize: of the effort and cost to capture AI value, only ~10% is the algorithms/models, ~20% is technology and data, and ~70% is people and process — adoption, workflow redesign, reskilling, incentives. Stalled programs invert this and over-spend on tools. The 70% is exactly what executives own, and it's the reason transformational bets need a runway: most of their cost and time is organizational change, not technology.
The two framings connect: the 30% capability-building horizon and the 70% people-and-process share are how a quick-win program manufactures the feasibility that high-value bets require. Skip them and your bets stay stuck in the top-left of the matrix forever.
Key insight
You are mostly buying change, not technology
If 70% of the cost of value is people and process (BCG 10-20-70), then a 'transformational bet' is mostly a change-management program with an AI engine inside it. Budget, staff, and govern it as such — and you'll understand why it can't be sequenced first, before that capability exists.
Watch out
The seat-licensing footgun
A tempting 'quick win' is buying copilot seats for the whole workforce on day one. As of 2025, ~30–40% of those seats typically go unused within 90 days. Blanket per-seat licensing is a vanity quick win — high adoption metric, low value. Pilot with a focused cohort, prove the workflow lift, then scale.
The cardinal rule: don't start with agents
The most consequential sequencing error of 2025–2026 is reaching for autonomous agents first — before the data and governance foundations that let them run safely and usefully even exist. Agents are the most powerful and most risky category, which makes them the last thing to sequence, not the first.
The evidence is consistent. BCG's guidance is to treat agentic AI as a next step, not a starting point: its prerequisites are strong data foundations, scaled AI capabilities, and clear governance. As of 2025, 46% of companies were piloting agents but only ~16% of those showed tangible value, and 72% already reported unmanaged AI-security risks. Gartner predicts (2025) that over 40% of agentic-AI projects will be canceled by end of 2027 — citing cost, unclear value, and weak risk controls. The constraint is rarely the model; it's that agents act, so the blast radius of a wrong action is larger, and they can't query data they can't find.
The practical sequence is therefore: prove value with supervised copilots (quick wins) → build the data and governance foundations during that period → only then graduate the highest-value, best-understood workflows into more autonomous agentic bets. The autonomy delegation test from the agentic module is the gate: delegate a decision to an agent only when the data is clear, the rules are defined, and the cost of waiting for a human exceeds the cost of a wrong autonomous action. Until a workflow passes that test, it stays a copilot.
Watch out
Where leaders get it wrong
Mandating 'agents everywhere' as the flagship initiative before data is governed and a human-in-the-loop policy exists. With ~40%+ of agentic projects forecast to be canceled by 2027 (Gartner, 2025) and most early agent pilots showing no tangible value yet, leading with autonomy is the highest-odds way to burn your AI mandate.
Tip
The leadership move
Make 'foundations before autonomy' an explicit gate. Before any agentic bet is approved, require evidence on three things: is the data clean, governed, and findable? Is there a human-in-the-loop / escalation policy? Can we halt and roll back? No to any one means it's not sequenced yet.
Putting it together: a sequencing playbook
The whole lesson collapses into a repeatable sequence a leader can run on any AI opportunity list.
- Sort every candidate into a bucket — quick win (faster) or transformational bet (redesign). Use the diagnostic question, not the hype.
- Plot all candidates on the value-by-feasibility matrix. Quick wins cluster top-right; bets cluster top-left; the bottom-left gets parked.
- Start in the top-right. Run a handful of high-value, high-feasibility quick wins with clear metrics and humans in the loop. These build credibility and cash flow.
- Use that period to raise feasibility — fund the 30% capability-building horizon and the 70% people/process work to clean data, stand up governance, and build change muscle.
- Concentrate the bets. Pick 2–3 high-value vertical workflows (McKinsey four pillars), each with a named sponsor and a redesigned process — not a redecorated old one.
- Gate autonomy. Graduate a workflow to an agentic bet only after it passes the delegation test (clear data, defined rules, halt/rollback).
- Re-plot quarterly. Feasibility and capability move; what was an infeasible bet last quarter may be a quick win this one.
Run in that order, the portfolio is self-funding: quick wins pay for and de-risk the bets, and the bets are the step change that the quick wins alone can't deliver.
The right questions to ask in any portfolio review: Is this a tool rollout or a workflow redesign? What's the clear success metric, and are we tracking quality, not just volume? Is our data clean, governed, and accessible enough to feed this? For anything that acts on its own — what's our human-in-the-loop policy, and can we halt and roll back?
Key insight
Self-funding by design
Done in order, the portfolio funds itself: quick wins generate the credibility, cash, and organizational muscle that the transformational bets consume. Done out of order — bets first — you spend credibility you haven't earned and stall before the quick wins can rescue you.
Try it: Sequence your AI portfolio on a value-by-feasibility matrix
Goal: turn a list of AI opportunities into a defensible sequence — the exact decision you'll make in a real portfolio review. 1) Gather candidates. List 8–12 AI opportunities your organization is considering or already piloting (pull from current pitches, shadow-AI usage, and the value-by-function map). 2) Bucket each one. For every candidate, answer the diagnostic question — does this make an existing task faster (quick win / copilot) or redesign the work end-to-end (transformational bet / agent)? — and label it. 3) Plot the matrix. Draw a 2×2 with business value on the vertical axis and feasibility (data readiness, effort, risk) on the horizontal. Place every candidate. Be honest about feasibility — most 'transformational' items will sit low-feasibility, and that's the point. 4) Read off the sequence. Pick 3–4 top-right quick wins to start now (each must have a clear success metric and a human in the loop). Pick 2–3 top-left high-value bets to sequence later, and name the specific data/governance/change-management work that would raise each one's feasibility. Park the bottom-left. 5) Apply the gates. For any candidate that involves an autonomous agent, run the delegation test (clear data? defined rules? can you halt and roll back?) — if it fails, mark it 'not sequenced yet.' 6) Set the budget shape. Sketch a rough ~60/30/10 split across near-term productivity / capability-building / exploration, and note one 70%-of-cost people-and-process item each bet will need. 7) Write the one-page brief. In half a page, state: your 3–4 first-quarter quick wins, your 2–3 sequenced bets with their feasibility-raising prerequisites, what you're parking and why, and the named executive sponsor for each bet. This one page is exactly what you'd take into a board or steering-committee review to defend why this order — the deliverable that separates a sequenced portfolio from a pile of pilots.
Key takeaways
- 1AI value is a sequencing problem, not a use-case-selection problem: near-universal adoption (~88% of orgs, McKinsey 2025) has produced value for few (~39% report EBIT impact) because leaders order their portfolio badly.
- 2Quick wins make an existing task faster (copilots: support assist, knowledge search, coding assist, content drafting, finance close, summarization) with structured inputs, a clear metric, and a human in the loop — start here.
- 3Transformational bets redesign a core function end-to-end (agentic workflows in claims, underwriting, supply chain, the customer journey) and require data, governance, change management, and multi-year ambition — sequence them later.
- 4Use a value-by-feasibility matrix: start top-right (high value, high feasibility), use the quick-win period to raise feasibility, then move toward high-value bets; starve the low-value, low-feasibility pilots that drown AI programs.
- 5Concentrate on 2–3 high-value vertical workflows with named sponsors (McKinsey four pillars), and budget for reality: ~60/30/10 across productivity/capability/exploration, with ~70% of true cost being people and process (BCG 10-20-70).
- 6Don't start with agents: autonomy is the last thing to sequence, not the first — BCG calls agents a next step requiring data and governance foundations, and Gartner (2025) forecasts >40% of agentic projects canceled by end of 2027.
Quiz
Lock in what you learned
Check your understanding
0 / 4 answered
1.A CIO proposes making the company's first AI initiative a fully autonomous, end-to-end claims-processing agent — the most ambitious item on the list. Based on the sequencing logic in this lesson, what is the strongest objection?
2.On a value-by-feasibility matrix, where should a leader focus the portfolio first, and why?
3.BCG's 10-20-70 rule states that of the total effort and cost to capture AI value, roughly 70% goes to which category — and what does that imply for transformational bets?
4.A board member argues: 'To move fast, let's run thirty AI pilots across every department at once and see what sticks.' Which response best reflects the lesson's guidance?
Go deeper
Hand-picked sources to keep learning
Source for the adoption-vs-value gap (~88% adoption, ~39% EBIT impact) and the four pillars / workflow-redesign findings. Re-verify the figures before each cohort.
The gen-AI paradox (horizontal copilots vs. deep vertical workflows) and the four-pillar prescription for concentrating on 2–3 high-value use cases.
Future-built vs. laggards, the function value map, agents as a next step (46% piloting / ~16% with value), and the focus-beats-breadth guidance. Volatile stats — verify live.
Source for the 10-20-70 budgeting rule (10% algorithms, 20% tech & data, 70% people & process) underpinning the portfolio-budget section.
The ~95%-of-pilots-show-no-P&L-return finding and the 'learning gap' (workflow/integration, not model quality) that motivates disciplined sequencing.
The forecast behind the 'don't start with agents' rule; cites cost, unclear value, and weak risk controls. A prediction — treat as volatile and re-verify.