TL;DR: A strategy is a resourced choice — a decision about what an organization will do, what it will stop doing, and who owns the work. A strategy-shaped artifact is a slide deck that performs the visual grammar of strategy without making any of its commitments. Most AI strategies in circulation are the second thing wearing the first thing’s clothes. The way to tell them apart is to look for the choices.

The deck is the artifact. The choice is the strategy.

You’ve just left a meeting where an AI strategy was approved. The slides were polished. The roadmap had quarters on it. Three pillars were named, four use cases were prioritized, and someone said the word “transformation” twice. Something felt off, and you couldn’t say what. You weren’t wrong.

What you watched was not a strategy. It was a strategy-shaped artifact — a communication document that signals seriousness without making any of the commitments that distinguish strategy from intent. The distinction matters because the two things require entirely different things from the room. A communication artifact requires consensus. A strategy requires resourced choice. Most AI work today is approved as the first and expected to deliver as the second, which is why it stalls somewhere between Q2 and the next all-hands.

Roger Martin has spent two decades arguing that a plan is not a strategy — that strategy is an integrated set of choices about where to play and how to win, and that the absence of those choices is the absence of strategy. The AI version of this confusion is the most expensive one I have watched organizations make.

A strategy is a resourced choice. Everything else is ambition with a date on it.

The working definition is one sentence: a strategy is a resourced choice about what the organization will and will not do, made under uncertainty, with named owners and named trade-offs.

Read that twice. Every clause is load-bearing.

Resourced means budget, headcount, and calendar time have actually moved — not been promised, moved. Choice means something has been picked over something else, which means something has been let go. Named owners means a person, not a function, is accountable. Named trade-offs means the document says, in language a board member can quote back, what the organization is no longer doing in order to do this.

If any of those clauses is missing, what you have is not a strategy. It might be a vision. It might be a roadmap. It might be a very expensive piece of internal marketing. But it is not a strategy, and treating it as one produces exactly the pattern we keep seeing across the enterprise — eighteen months of pilots, a cohort of frustrated senior engineers, and a follow-on board meeting where someone asks why the numbers haven’t moved.

Strategy-shaped artifacts have four tells.

The first is ambition without trade-offs. The deck names where the organization wants to be in three years but never names what it will stop doing to get there. Every existing initiative survives. Every team’s roadmap is preserved. Every sacred cow grazes on. This is the most reliable tell because it points at the most expensive truth — real strategy reallocates, and reallocation creates internal losers, and a deck with no internal losers has not yet asked the organization to choose.

The second is capability claims without staffing. The slide promises a “production-grade RAG platform” or “agentic workflows across customer operations.” The next slide does not name the engineering leader who owns it, the team that has been pulled off other work to staff it, or the hiring plan that closes the capability gap. Capability is not a slide. Capability is a staffed team with a calendar.

The third is timelines without sequencing. There are quarters on the roadmap. There are not dependencies. Nobody has answered the question of what must be true in Q1 for Q2 to start, or which decision in Q3 forecloses what Q4 can become. A timeline without sequencing is a wish list with months attached. Ask any operator who has run a platform migration — the value lives in the sequencing, not in the calendar.

The fourth is metrics without baselines. The deck promises efficiency gains, revenue lift, or productivity multiples without naming the current number against which improvement will be measured. This is not an oversight. A baseline is a commitment. A baseline says, in twelve months this number will be different, and we will be accountable for that difference. A deck with target metrics but no baseline metrics has carefully preserved the option to redefine success after the fact.

Organizations produce theater because they confuse two artifacts.

The structural reason this keeps happening is not incompetence and rarely cynicism. It is a category error.

A board deck and a strategy document are two different artifacts that organizations have collapsed into one. A board deck is a communication artifact — its job is to align stakeholders, signal seriousness, and secure funding or political cover. A strategy document is a decision artifact — its job is to constrain future action, force trade-offs, and make accountability legible. The two have different audiences, different success criteria, and different forms.

When an organization treats the board deck as the strategy, four pressures converge at once. Board dynamics reward ambition, so the document inflates. Vendor influence rewards specific technologies, so the document picks tools before it has picked problems. Fear of committing under uncertainty rewards optionality, so trade-offs vanish from the page. And the genuine difficulty of the work — the persistent gap between AI investment and measurable financial impact documented by MIT Sloan Management Review and BCG — rewards looking decisive over being decisive.

What gets approved in the room is therefore optimized for the room. It is not optimized for execution. The execution gap is not a downstream failure. It is engineered into the artifact at the moment of approval.

The diagnostic is five questions you can ask in your next review.

Carry these into the next AI strategy review you sit in. Ask them in order, in plain language, without softening them. They are not rhetorical.

One — what are we no longer doing, and which of those things is the AI work directly displacing? If the answer is nothing, this is not a strategy. Real reallocation produces a list, and in AI work the list usually includes the analytics roadmap, a BI vendor renewal, or a team’s existing automation backlog. Ask for the list.

Two — who is the single accountable owner, and what has been removed from their plate? If the owner is a steering committee, you have a meeting, not an owner. If nothing has been removed from their plate, you have a side project, not a priority. AI work in particular fails when ownership is split between a data team, a platform team, and a business sponsor — pick one throat to choke.

Three — what is the baseline number we are starting from, what is the target, and is that metric something the model can actually move, or are we measuring a proxy? Both numbers must exist. If the baseline cannot be stated to two significant figures, the target is performance. And if the metric is “engagement” or “satisfaction” rather than something tied to a workflow the system actually touches, the target will move whether the AI works or not.

Four — what must be true in the next ninety days — specifically about data access, model selection, and the team’s ability to ship against an evolving capability frontier — for this to still be on track in twelve months? This forces sequencing. AI strategies fail in the first ninety days more often than the last ninety: the data isn’t accessible, the chosen model is superseded, or the team that needs to integrate it doesn’t exist yet. A strategy that cannot answer the ninety-day question has not been thought through past the cover slide.

Five — what would cause us to kill this, and who has the authority to kill it? Optionality is the enemy of execution, and AI work attracts optionality like nothing else — there is always a newer model, a better benchmark, a vendor pitch that argues for one more quarter. A strategy that cannot describe its own off-ramp is one nobody intends to be accountable for.

If a document survives all five questions, you are looking at a strategy. If it survives two or three, you are looking at a serious draft. If it survives none, what was approved in the room was an artifact, and the work of strategy has not yet started.

The five questions, in one place:

  1. What are we no longer doing, and which of those things is the AI work directly displacing?

  2. Who is the single accountable owner, and what has been removed from their plate?

  3. What is the baseline, what is the target, and can the model actually move that metric?

  4. What must be true in ninety days — about data, model, and team — for the twelve-month plan to hold?

  5. What would cause us to kill this, and who has the authority to do it?

Screenshot that. Bring it to the meeting.

Common failure modes

The diagnostic itself can be misused, and three patterns are worth naming before you carry it into a meeting.

The first is using the questions to grandstand. A diagnostic is not a gotcha. The point is to surface where the choices haven’t been made yet — not to indict whoever wrote the deck. Operators who use these questions to score points lose the room and the leverage in a single meeting. Ask in good faith. Make it easier, not harder, for the team to admit what is missing.

The second is applying the test to the wrong artifact. A vision document is allowed to be aspirational. An R&D exploration is allowed to be open-ended. The diagnostic applies to documents that are being approved as strategy and resourced as strategy. Demanding baselines from a six-week discovery sprint is its own form of theater.

The third — and the most common — is mistaking the strategy document for the strategy itself. The deck is downstream of the choices. If the choices have actually been made, the document writes itself in an afternoon. If the team is on draft fourteen and still arguing about wording, the underlying choices have not been made yet, and no amount of wordsmithing will produce them. Send the team back to the choice, not back to the slide.

The closer

Strategy is what you say no to. The deck cannot make the choices for you, and approving the deck is not the same as making them. The five questions above are not a framework — they are a flashlight. Point them at the next AI strategy that comes across your desk, including your own, and you will know within ten minutes whether you are looking at a plan or a performance.

AI does not replace leadership. It exposes the quality of it — and nowhere more cleanly than in the gap between the deck that gets approved and the work that gets done.

I unpack observations like this every week in Operator’s Log. Grounded AI perspective from the operator’s seat. Free. Subscribe →

FAQ

Q: What is the difference between an AI strategy and an AI strategy deck?A: A strategy is a resourced choice — a decision about what the organization will do and will not do, with named owners, named trade-offs, and budget actually moved. A deck is a communication artifact about a strategy. The deck is downstream of the choices. If the deck has no trade-offs, no baselines, and no named owners, you are looking at the artifact without the strategy underneath it.

Q: How can I tell if my company’s AI strategy is real or theater?A: Ask what the organization has stopped doing to fund the work, who the single accountable owner is, what the current baseline metric is, and what would cause the work to be killed. If those four answers exist in plain language, the strategy is real. If they don’t, what got approved was a communication document, not a decision.

Q: Why do most AI strategies stall after the board presentation?A: Because the document was optimized for board approval, not execution. Boards reward ambition and optionality, which is the opposite of what execution requires — namely, trade-offs and constraint. The execution gap is not introduced afterward; it is engineered into the artifact at the moment of sign-off.

Q: What questions should I ask in an AI strategy review?A: Five. What are we no longer doing because of this? Who is the single accountable owner and what has been removed from their plate? What is the baseline and what is the target, and can the model actually move that metric? What must be true in ninety days — about data, model, and team — for this to be on track in twelve months? What would cause us to kill this, and who has the authority to do so?

Q: What does a real AI strategy look like in practice?A: It is short. It names two or three problems the organization will solve before it names any technology. It lists what is being defunded or deprioritized to fund the work. It assigns a single accountable owner per workstream. It states current and target metrics. It includes a kill criterion. The slides, when they exist, are downstream of those decisions, not a substitute for them.