01
Demand
Is there evidence anyone wants this — measured in behavior, not in enthusiasm from the team proposing it?
Ask about Skip
Prepared answers · no data sent
Generate, assess, score, prioritize — the four machine capabilities that decide what an enterprise does next
It is not the strongest of the species that survives, but the one most responsive to change.
AI is moving from a supportive tool to a system that touches every part of how a business runs. Not because the models got clever — because the decision load outgrew the people carrying it.
Every enterprise now generates more signal than its leadership can process: product telemetry, service transcripts, movement in supply and price, regulatory change, and the exhaust of a dozen systems never designed to be read together. It arrived faster than the decision-making structures built to absorb it — structures designed for quarterly cycles and a manageable number of options.
The result is familiar. The list of things the business could do is longer than ever, the evidence behind each is thinner than anyone would like, and the meeting where it gets decided has not grown any longer.
Of organizations are now scaling AI enterprise-wide, up from 38 percent a year earlier1
Report any EBIT contribution from that AI — a figure that has not moved1
Of the high performers fundamentally redesigned how work runs, against 25 percent of everyone else1
Of day-to-day work decisions will be made autonomously by 2028, from effectively zero in 20242
Read those four numbers together and a pattern appears. Deploying AI is ordinary. Getting it to change a business result is not, and the organizations that manage it redesigned the work rather than decorating it. Meanwhile Gartner expects roughly 15 percent of day-to-day work decisions to be made autonomously by 2028, from essentially zero.2 The question is no longer whether machines participate in decisions but which parts they are given.
Strip the technology conversation back to what a decision requires and four capabilities fall out. Options have to be generated, assessed against evidence, scored so unlike things can be compared, and prioritized against a capacity always smaller than the ambition.
Humans have always done all four. What changes is the scale of the first three and how often the fourth can be revisited. That is the whole shift.
The machine's job is to make the volume tractable. The human's job is to decide. Confusing the two is how organizations end up automating the wrong half.
The first capability is the one most organizations underuse: continuous, structured option generation from signal no human team could read in a quarter, let alone a week.
A system with access to the right data reads trend data, industry shifts, customer behavior, competitor movement, and internal telemetry, then proposes products, business models, and process changes against them. Not once at the offsite — continuously, as the signal moves.
The instinct is suspicion, and it is half right. Generation at scale is worth nothing if the output is random. The value depends on the constraint: options produced against a named decision and an explicit objective, or the organization drowns in a larger pile of ideas than before.
Done well, it surfaces opportunities an organization would never have reached — not for want of cleverness, but because the pattern sat across four systems and three functions that never meet. Done badly, it produces a thousand plausible sentences and a leadership team that trusts the exercise less.
Generate widely. Bound tightly. Those are not in tension — the second is what makes the first safe.
The second capability is evaluation: taking a long list of candidates and establishing, quickly and consistently, what each one would actually involve.
Assessment asks five questions of every option: is there demand, can we do it operationally, what does it cost, what does it risk, what would it return. Human teams answer well and slowly, one initiative at a time, with depth depending on who was in the room. A machine answers consistently across hundreds of candidates.
Consistency is the underrated half. Every option gets the same questions with the same rigor — which is precisely what does not happen when assessment depends on which executive is sponsoring which idea.
Is there evidence anyone wants this — measured in behavior, not in enthusiasm from the team proposing it?
Can this organization actually run it — with the data it has, the systems it runs, and the people it employs today?
The full cost — build, change management, governance, and the ongoing operation that arrives after launch.
What breaks if this is wrong, who is exposed, and what the organization is obliged to prove afterwards.
The expected effect on a number the business already tracks — stated before the work starts, not reconstructed after.
Assessment has a shelf life. Anything evaluated against last quarter's conditions is a historical document, not a recommendation.
Assessment at machine speed is not about answering faster. It is about answering evenly — which is the thing human assessment almost never does.
Assessment tells you what each option involves. Scoring is what lets you compare things that have nothing else in common.
This is the step organizations skip, and skipping it is why AI portfolios end up sorted by seniority. A claims automation project and a customer service assistant share no unit until someone imposes one. The imposition is the point. A score is not a verdict; it is a common language that makes an argument possible.
The formulation I use is Decision RICE: Reach × Impact × Confidence ÷ Effort — reach counting decisions per quarter rather than users, confidence blending evidence quality with data readiness, effort including change and governance work, not just the build. Machines compute it continuously. Choosing the criteria remains an executive act.
Reach is decisions touched per quarter. Effort is person-months of build, change, and governance. Move a slider and watch the ranking answer back.
Two things become obvious. High-reach, low-impact work — summarization, assembly, retrieval — often out-scores the ambitious agentic initiative everyone arrived excited about, because it touches so many decisions so cheaply. And confidence does more damage than any other input: uncertain data readiness cannot be bought back with a strong impact estimate.
Score ranks. It does not decide. A high-reach, low-impact initiative can top the chart and still be the wrong thing to fund this year.
Which is why scoring is the third capability and not the last one.
Prioritization is where the previous three capabilities either become an operating decision or stay an analysis. It is also the only one of the four that is fundamentally about scarcity.
A ranked list is not a plan. A plan is a ranked list met with real capacity — engineering months, change bandwidth, governance attention — and a decision about where the line falls. Above it gets funded, staffed, governed. Below it is not a backlog or a phase two; it is what the organization has agreed not to do while the funded work finishes.
Machines make this dynamic in a way it never has been. Capacity changes, a supplier moves, a regulation lands — and the line gets redrawn against current conditions rather than the ones that held at the last offsite. The prize is not faster ranking. It is re-cutting without waiting for the calendar.
Drag the capacity. Notice what has to leave the plan before anything new can enter it.
Dynamic does not mean continuous. Re-cutting weekly produces whiplash and destroys the conditions under which anything finishes; re-cutting annually runs the business against conditions that expired months ago. Quarterly, with a standing mechanism to force a re-cut when something material moves.
The four capabilities are worth nothing as a diagram. What follows is the sequence I run with leadership teams, and the order is load-bearing.
Connect the machine to real data. Generation and assessment are only as good as their reach into CRM, ERP, finance, service, and operations. The least glamorous step, and the one that determines everything downstream — an assessment layer on a curated extract produces confident answers about a business that does not exist.
Name the objective before generating anything. Market expansion, cost reduction, cycle-time compression, risk posture — the objective is the constraint that turns generation from noise into options. Teams that skip this step get volume and mistake it for progress.
Automate assessment and scoring, not the choosing. Let the machine evaluate and rank against criteria you set. Keep the criteria, the weights, and the final cut in human hands — that is what your board holds you accountable for.
Make prioritization dynamic, and give it a cadence. Build the mechanism that re-cuts when conditions move, then decide how often it may fire. Dynamic without cadence is churn; cadence without a mechanism is annual planning in new language.
The honest description is not that AI decides. It is that the preparation — assembling, comparing, ranking, reconciling numbers from four systems — stops consuming the week before the meeting. What arrives is a ranked, evidenced, capacity-tested set of options with the assumptions visible.
Executives then spend their time on what machines are worst at: what the organization is for, what it will not do, and which uncomfortable trade-off it will accept. That work does not get automated. It gets clearer and faster, because the arithmetic underneath is already done and visible.
The constraint was never intelligence. It was throughput on the way to judgment.
Start with one decision your business makes repeatedly and expensively — claims routing, pricing, capacity commitments, portfolio investment. Run the four capabilities against it end to end: generate the options, assess them evenly, score them on one sheet, cut against real capacity. Measure cycle time before and after.
One decision, done completely, teaches an organization more than a dozen pilots aimed at capabilities. It also produces the thing every subsequent conversation needs: evidence, from your own business, that the loop works.
Generate widely. Assess evenly. Score honestly. Prioritize ruthlessly. Then do it again next quarter, against the conditions that actually hold.
Figures cited in this paper come from named research published between mid-2025 and mid-2026, with the methodology noted so each claim can be read at its actual strength.
Where this goes next
The four capabilities are easy to agree with and hard to sequence. If your team is working out where generation, assessment, scoring, and prioritization belong — and which decision to prove them against first — that is the conversation I have most often.
Skip Vanderburg · CX Strategy, Design & Innovation · skip.vanderburg@gmail.com · skipvanderburg.com
