How Do You Show AI Made Your Strategy Better?

Neeka leaves the boardroom rattled.

Her team had done the hard work of building AI into the company’s strategy process. Her presentation was thorough. The board still wasn’t satisfied.

“How do we know this made the strategy better?” a director asked.

It was a fair question. Researchers have a name for what boards fear: trendslop, the generic, fashionable advice that language models tend to produce whatever your company’s situation. Neeka’s team had worked hard to avoid it. She couldn’t prove they had.

The board told her to use AI. Now it wants evidence that using it paid off.

What does she show them?

The proof gap

Neeka isn’t alone.

A Financial Times/Infosys survey of 300 directors at large North American companies found that 75% expect AI to significantly improve strategic decision-making. The same report warns that “decision quality does not improve by default.”

CEOs are more confident still. A Harris Poll for the software firm Dataiku asked 500 CEOs. Some 89% believe AI can write an equal or better strategic plan than one of their own executives.

Belief is high. Evidence is thin.

Capgemini surveyed 500 senior executives at companies with revenue above $10 billion. Some 47% reported noticeable gains in decision quality, though that is self-reported. And 52% listed their inability to verify AI’s output as a concern. Only about a quarter of their organisations have systems to validate it.

So leaders expect better strategy, say they’re getting it, and worry they can’t check. Your board will notice the gap.

Your first instinct

Neeka’s first instinct is sensible: take a workflow first approach, and borrow from process management.

TQM, Lean and Six Sigma carry decades of guidance and a deep library of case studies. Measure the work. Standardise it. Cut the variation. Few directors would argue with a method that is proven and countable.

Then consider 3M.

In 2001 the company hired James McNerney from GE. He brought Six Sigma with him and applied it widely, research labs included.

3M emerged financially stronger. Many researchers chafed. One R&D leader later described the company as “tool happy.” McNerney’s successor, George Buckley, de-emphasised Six Sigma in R&D.

Six Sigma suited the plants. In the labs, it was the right tool in the wrong room.

Strategy is lab work

A factory aims to repeat itself perfectly. Strategy aims to produce something different from last time.

Take Jamaica, in the Caribbean. Its national development plan, Vision 2030 Jamaica, runs out in a few short years. A successor that simply stretched it another twenty years, a possible Vision 2050, would waste the exercise. A national plan should break new ground, the way a lab does.

Corporate strategy has the same job. So how do you improve work that never repeats?

What the Army learned

One organisation faced this problem decades ago.

In the 1970s the US Army wanted to learn from its training exercises. No two missions are identical, so a fixed process couldn’t be the thing the Army improved.

It built the After Action Review: a short session after the event, built on four questions. What was supposed to happen? What actually happened? Why the difference? What should we sustain or improve? A facilitator leads it, usually not the most senior person present.

The Army improved a set of questions, rather than a set of steps. Strategy can borrow that.

At the same time, the review has a limit. It looks backward.

Moreover, a strategy’s results take years to show, and many other factors intervene along the way. That’s too late.

You need questions you can ask while the work is still open, before the strategy project ends.

Catch it before it ships

Software teams solved a version of this.

At PayPal, an engineer writes a one-page proposal describing the problem and the proposed design. The team then runs a pre-mortem. They assume the design failed and work out why. The engineer fixes what turns up before building.

PayPal says the practice catches issues early and exposes blind spots. That’s the company’s own account, not a measured result, and it comes from software design, not strategy. It’s the closest documented model I know of.

A pre-mortem is a defect hunt. A defect, in this sense, is anything wrong with the work that you can name, rank and fix.

Name your defects and you can show you removed them.

A grade isn’t a defect list

Some leaders already use AI as a critic.

Salesforce CEO Marc Benioff described his routine to the writer Bernard Marr. Each January he drafts his annual plan. He used to refine it with another executive. Now AI joins as a third collaborator. He asks it to compare the plan with his competitors’ and to “give me a letter grade.” He also asks where the plan is weak and where it is strong.

Smart habit. In the account I read, though, Benioff doesn’t say what the grade rests on. A letter says how a plan scored. It doesn’t say what was wrong, what you fixed, or whether this year’s process beats last year’s. A defect list answers all three.

Capgemini’s guidance on tracking AI-assisted decisions lists KPIs such as compliance scores and decision turnaround time. Those measure compliance and speed. They say little about the quality of the strategic choices.

SPEAR: your first experiment

I see the business world developing defect detection for strategy creation. The one I use with clients is SPEAR: Strategy Process Engineering for Analysis and Refinement.

It builds on the six stages of my EndPoint Method: a snapshot of where you are, a target year, scenarios, one chosen alternative expressed in numbers, a backcast from that endpoint, and a short-term strategy map.

SPEAR adds a short defect check at each gate between stages. At your next gate, pause the work for a few minutes and ask:

1. Where are we?

2. What did we just do?

3. What defects can we see?

4. Which ones matter?

5. What can we fix now?

6. What do we record?

7. What is the next gate?

Then repeat at the next gate. There’s no baseline project and no months of process mapping. It takes a meeting you already hold.

What your board sees

The record is your proof.

Over time you build a defect library: what went wrong at each stage, how you fixed it, what you learned. It comes from your judgement, and it waits for the next team.

It also shows where AI earned its place: the defects it helped catch or prevent. Time saved tells a board very little about strategy.

Neeka returns

Neeka’s next board meeting goes differently.

She brings a short list: the defects found at each gate, what the team fixed, what it recorded. Beside it sits a note on where AI helped.

The board asked her to prove it. The record does.

—

**Sources and further reading**

– Romasanta, A., Thomas, L. D. W., & Levina, N. (2026, March 16). “Researchers Asked LLMs for Strategic Advice. They Got ‘Trendslop’ in Return.” Harvard Business Review. https://hbr.org/2026/03/researchers-asked-llms-for-strategic-advice-they-got-trendslop-in-return

– Capgemini Research Institute (2026). “Inside the C-Suite: How AI is quietly reshaping executive decisions.” https://www.capgemini.com/wp-content/uploads/2026/01/Final-Web-Version-Research-Brief-Gen-AI-in-Decision-Making.pdf

—-

This article was inspired by a column I wrote for the Jamaica Gleaner. This began as an AI-drafted version of the original.

SPEAR is fully aired in a 2 hour LTSP26 conference replay edition.

P.S.

Five prompts to try with your own AI

Paste any of these into the AI tool you use. Replace the [brackets] with your own details. Each prompt asks the AI to question you first and to flag what it can’t verify. That cuts down the generic answers.

1. Run a defect check at your next gate

“I’m at a gate in a strategy project. The stages are: snapshot, target year, scenarios, one chosen alternative in numbers, backcast, short-term strategy map. I just finished: [stage and what you produced]. Ask me up to five questions about the work first. Then take me through these seven questions: where are we, what did we just do, what defects can we see, which ones matter, what can we fix now, what do we record, what is the next gate. A defect is something wrong with the work that can be named, ranked and fixed. Quote my own words when you name a defect. If you can’t find any, say so instead of inventing some.”

2. Ask for defects, not a grade

“Here is my draft plan: [paste]. Don’t give it a grade or a score. List the defects you find. For each one, give what is wrong, where it sits in the plan, why it matters and a suggested fix. Rank them from most to least serious. Mark each as ‘evidence in the text’ or ‘my inference’. Then tell me what else you would need to know to find more.”

3. Test your plan for trendslop

“Below is a strategy recommendation that AI helped produce: [paste]. Check it for trendslop, meaning generic, fashionable advice that would suit almost any company. For each recommendation, answer three questions. Would it fit my closest competitor equally well? What specific fact about my company supports it? What would the opposite choice look like, and why was it rejected? Then list the recommendations that fail these tests.”

4. Is your work factory work or lab work?

“I’ll describe a piece of work my team does: [describe]. Help me decide whether it is factory work (repeatable, so standardising helps) or lab work (should produce something different each time, so standardising can hurt). Ask me questions first. Then tell me which parts are which, and what kind of improvement method suits each. Challenge my answers where they sound like wishful thinking.”

5. Build the record your board can see

“I need to show my board whether AI improved our strategy work. Here are the defects my team has found, fixed and recorded so far: [paste, or write ‘none yet’]. Help me set up a defect library: suggest columns, categories and a format that fits on one page. Then draft a short board note listing defects found, fixes made, and where AI helped catch or prevent them. Don’t use time saved as evidence. If my records are too thin to support a claim, tell me what is missing.”

The Bets Your Strategy Makes Without Asking You

Your leadership team has announced a new ambition: be number one.

You nod along, but something nags at you. The goal is clear. It’s easy to repeat. Nobody could call it vague.

So why the unease?

Because a goal this simple hides more than it shows. In the next few minutes, I’ll cover what it hides, a case from the heavy-equipment industry, and three questions you can take into your next leadership meeting.

Seven Outcomes, One Phrase

Every organization answers to a long list of outcomes:

– Profit (or surplus, for a nonprofit)

– Customer value

– Staff commitment

– Resilience

– Innovation

– Social impact

– Long-term survival

“Be number one” keeps one line from that list: a ranking against rivals, usually measured in money or market share.

The other six stay in the business but drop out of the conversation. Nobody votes to give them up. They just aren’t in the room when the goal gets written.

Supporters of the single goal say people need something simple to rally around, and they’re right about clarity. The cost is what the simplicity conceals. The commitments you stop discussing are still commitments.

What One Famous Rivalry Cost

From the 1960s into the 1980s, Japanese equipment maker Komatsu pursued a stated intent: “Encircle Caterpillar.” Gary Hamel and C.K. Prahalad made the phrase famous, and business schools still teach it as a model of bold goal-setting.

It was more than a slogan. Komatsu’s yearly priorities and projects were measured against Caterpillar’s results.

For a long time it worked, because the global market for heavy equipment was growing. Then growth slowed. By the late 1980s, Komatsu’s own growth and profits had stalled. Its dependence on construction equipment and on its home market had become a weakness.

In 1989, a new president, Tetsuya Katada, spotted the deeper problem. Years of chasing a rival had narrowed how his managers thought. They knew how to track a competitor. They didn’t know how to find a new direction once the chase stopped paying off.

He replaced the old goal with a deliberately wide one: “Growth, Global, Groupwide.” Then he pushed managers to turn those words into specific new opportunities.

Look at what happened. Komatsu placed one bet in the open. When it ran out, the company placed a second. Between them, a number of bets went unnamed.

Three Kinds of Bets

Every strategy is a set of wagers. Sorting them into three types makes them easier to see.

Explicit bet. An outcome the company states out loud. For Komatsu: “Encircle Caterpillar.”

Implicit bet. A commitment squeezed out by the stated goal, such as customer value or resilience. The company trades it away without a decision. At Komatsu, one casualty was the managers’ habit of questioning direction. After years of single-target discipline, they had lost the skill.

Shadow bet. An outcome the company commits to through repeated choices, omissions and budget lines, without ever stating it.

Shadow bets are the dangerous ones. They never appear in a plan, and nobody can be polled on them.

Where Shadow Bets Hide

You find implicit bets by asking what a goal leaves out. Shadow bets slip past that question because nobody knows they’re making them. You find them by watching behavior: what gets funded, who gets promoted, what never receives a budget line.

Komatsu’s priorities were pegged to a rival’s results. That arrangement assumed the market would keep growing. Nobody wrote the assumption down. The budget stated it anyway.

Climate offers a current example. Many companies act as if climate change will leave their operations alone. That may hold for a few years. Behind it sits a second shadow bet: that future leaders will cope when the effects arrive. Neither bet appears in any strategy deck.

Consider a common arrangement: a company busy chasing a ranking sets up a small innovation unit “to explore new categories.” Look at the budget and you’ll find the shadow bet, that the core business will keep winning and the lab will stay a sideshow. This matters because a ranking only exists inside a category that already exists. A culture built around the ranking has little reason to invent a new one.

Short planning horizons make all of this worse. When a company plans five years out and no further, assumptions pile up unexamined. In the failed strategies I’ve studied, one pattern keeps recurring: short-term plans that led to disastrous long-term consequences. Firms that practice rigorous foresight make fewer shadow bets, and the ones they do make carry less risk.

Why the Usual Fixes Miss

Executives who sense the problem often try one of these:

– A softer slogan. “Market leader” or “first choice” instead of “number one.” Same bet, gentler words.

– A longer race. “Number one by 2040.” Longer horizon, same single outcome.

– A balanced scorecard. More metrics, all still rolling up to the ranking.

– A sustainability report. Run beside the strategy, not inside it. Climate becomes compliance instead of a bet.

– A listening tour. Stakeholders share what they care about. No budget changes.

Each adds activity. None puts a bet on the table where it can be examined.

The Executive Who Counts

Picture Maria, a composite character. Newly promoted into the C-suite, she’s startled by how much of the room’s time goes to the competition. In the last strategy update, she counted: 45 percent of the discussion was about beating the market leader from their position at number two.

She raised it afterward with the founder, a former Olympian and self-described hypercompetitive type. “You’d best become accustomed to us winning if you want to be a team player!” he barked, and cut the discussion short.

She never reached her real news. A new technology will reshape the industry in six or seven years. The two people who understand it have left to start their own firm, and the third is being courted by two competitors. Catching up would take about ten researchers and $10 million in new technology.

Maria has worked at the company for twenty years and doesn’t want to leave. That night, she updates her LinkedIn profile anyway.

Her story shows the social cost. When the conventional wisdom is simple and your peers stay quiet, a lone concern gets overridden. You need language that others can pick up and use. Without it, you’re one person with an unease.

Three Questions for Your Next Meeting

Take these into the room.

1. Explicit bets: What are we betting on?

2. Implicit bets: What does this goal compress, and what does the compression cost us?

3. Shadow bets: What do our budgets, promotions and omissions say we’re betting on?

An outside facilitator or an AI assistant can help with the third question, because neither is invested in your stated intentions.

Start with your own “be number one” goal. List what it says, what it compresses and what your budgets imply. The gaps between the three lists show where your unexamined risk sits.

Then try Maria’s method. Count the minutes your last strategy meeting spent on rivals, versus customers, staff, regulators and the world you’ll operate in a decade from now. That ratio is a bet too.

A company places bets every year through what it funds, whom it promotes and what it leaves unfunded. Ask the three questions. You may find bets nobody decided to make.

—-

This article is based on a column written for the Jamaica Gleaner. It’s first draft was AI-based.

P.S. Five prompts to put these ideas to work

Paste any of these into your AI assistant. Replace the [bracketed text] with your own details, and leave out names or figures you wouldn’t share outside your organization.

**1. Unpack your goal**

My organization’s stated ambition is: [paste your “be number one” or “be the best” goal]. A goal like this can compress seven outcomes into one: profit or surplus, customer value, staff commitment, resilience, innovation, social impact and long-term survival. Ask me, one question at a time, how my organization treats each of these in practice. Then show me which ones get airtime in leadership discussions and which have dropped out. Do not guess about my organization. Ask when you don’t know.

**2. Count the minutes**

Below are the agenda or notes from our last strategy meeting: [paste]. Estimate how much time went to rivals and competitor comparisons, and how much went to customers, staff, regulators and the future we will operate in. Show your reasoning. Then name the outcomes the discussion left out, and what it could cost us if they stay out. Mark clearly what you counted from my notes and what you are inferring.

**3. Hunt for shadow bets**

Here is what I know about where my organization puts its resources: what we fund, whom we promote, and what we leave unfunded or delay: [paste]. Act as a skeptical outsider with no stake in our stated strategy. Infer the bets these behaviors imply, including unwritten assumptions about growth, our market, climate or leadership succession. List up to five. For each, give the evidence from my notes and one question I could ask my team to test it. Say so when the evidence is thin.

**4. Test the category**

Imagine that in fifteen years the category we compete in has shrunk sharply or been replaced. Ask me five questions, one at a time, about our technology, talent, customers and funding. Then describe what a number-one ranking would be worth in that world, and list which of our current projects and budgets assume the category survives. Separate what I told you from what you assume. If you need facts about my industry, ask me.

**5. Rehearse the room**

Role-play a senior executive who believes “be number one” is the right goal. Raise objections such as: the market rewards leaders, simple goals motivate people, nobody can plan fifteen years out, and new categories are for startups. I will argue for naming our explicit, implicit and shadow bets. Push back realistically but fairly. After five exchanges, step out of character and tell me which of my arguments landed, which did not, and what language I could use to win allies instead of raising concerns alone.

When One Future Isn’t Enough

Your company is winning. Revenue is up, market share is stable, and the board likes what it sees. But look past the numbers and a real question is waiting: is this a strategy, or just an extrapolation of what’s worked so far?

That distinction matters more than it sounds like it should. Extrapolation works fine right up until the market shifts. By then, it’s too late to build an alternative.

Take Kodak and Fujifilm. Both companies had digital photography technology decades before it upended their industry. Kodak’s version of the story gets told the most: brilliant engineers, a dominant brand, and a board that shelved the innovation rather than risk film sales. When digital cameras finally took over, Kodak had no second act ready.

Fujifilm had the same technology and the same warning signs. Its leadership drew a different conclusion: photographic film would not pay the bills forever. So it went looking through its own laboratories for technologies that could become something else entirely. Two bets came out of that search, developed side by side. One was Instax, an instant-camera category built on Fujifilm’s imaging chemistry. The other was Astalift, a cosmetics line built on collagen and nanotechnology the company had originally developed for film. Neither was a better camera. Both answered a customer question film photography never asked.

That’s the real lesson. Improving a product and reinventing a category are not the same move. One extends an answer. The other asks a new question.

Kodak’s failure has company. Blockbuster stayed anchored to the physical rental store while Netflix built a fundamentally different way to watch movies, and filed for bankruptcy in 2010. Nokia kept optimizing handsets while Apple and Google moved the competition to software and app ecosystems, and eventually sold its phone business to Microsoft. Borders kept investing in the physical bookstore, outsourced its own online sales to Amazon in 2001, and liquidated a decade later.

Look closely at those three and you’ll notice they didn’t fail the way Kodak did. Kodak’s category disappeared: film photography became structurally unattractive, and there was nothing to pivot back into. Blockbuster, Nokia, and Borders had it worse in one sense. The underlying customer need never went away — people still wanted to watch movies, communicate on the go, and read books. What disappeared was their claim on it, because somebody else built a new category to serve that same need. A strong core business can keep performing right up to the moment a competitor creates the category that makes it irrelevant.

That’s what makes a portfolio of candidate futures worth the trouble. Amazon didn’t wait for online retail to plateau before placing its next bet. It launched S3 in 2006 and EC2 not long after, building the cloud-computing category while its retail business was still scaling. Alphabet does something similar on purpose: it runs a set of “Other Bets” — Waymo, Verily, and several others — deliberately kept at different stages of development, some barely past the research stage, so the company always has more than one shot at the future in play at once.

None of this is really new. IBM ran something similar in the early 2000s under a formal program that tracked what it called emerging business opportunities. Within three years, the portfolio had grown to seventeen candidates, spanning life sciences, Linux, pervasive computing, and business-process integration, each one tracked against its own milestones rather than forced through the existing business’s metrics.

Samsung did something comparable in 2010, naming five future growth businesses — including solar cells, batteries, and biopharmaceuticals — and committing serious capital to develop them in parallel. Some of the five went nowhere. A few became genuinely important. That’s not a coincidence, and it’s not a weakness in the approach. It’s the approach working as intended: the value isn’t in a high hit rate, it’s in having more than one live option when the environment shifts.

Naming that pattern is the easy part. Committing real resources to a future that might not happen is much harder, especially while the current category is still paying the bills. Few leadership teams even attempt to plan fifteen or thirty years out. Fewer still try to hold multiple long-range futures at the same time.

Until recently, that kind of work belonged to consultants and academics, who produced dense reports that ended up on a shelf. AI changes what’s possible now. It took the launch of ChatGPT to reveal what GPT-3 had only hinted at a year earlier, and most organizations planning long-term in 2021 missed that shift entirely, because nobody was scanning for it. Tools like Preempt.live can now surface thousands of plausible futures for an industry in an afternoon, which lowers the cost of asking “what else might happen” close to zero.

If your organization already has a few candidate categories in mind, the next steps aren’t complicated:

  1. Name a handful of candidate categories, with input from AI and your board.
  2. Assign each one to a champion who wants to see it succeed, not a department that inherits it as a side project.
  3. Teach each champion to use AI to track the faint signals that would tell you a candidate is starting to matter.

None of this requires certainty. It requires candidates, champions, and the discipline to keep watching for the next fifteen to thirty years.

Your current strategy is paying the bills today. Start building the one that will pay them next.

[This article is a longer, AI-generated version of an original Gleaner column.]

P.S. — Five prompts to run through your own AI tool

1. “List every product or service my organization sells today. For each one, tell me: if this disappeared entirely in the next ten years, would our underlying customer need disappear with it, or would someone else just be serving that need in a different way?”

2. “Based on what you know about my industry, name five to ten emerging categories that don’t exist yet but plausibly could within the next 15 years. Don’t filter for feasibility — I want the raw list first.”

3. “Play devil’s advocate: what is the single strongest argument that my current category will keep paying the bills for the next 15 years, with no need for a backup? Then tell me what would have to be true for that argument to be wrong.”

4. “If I had to hand one candidate future to a named person on my team — not a department — and ask them to genuinely champion it, who on my team already has the curiosity or skills to do that well, based on what I tell you about them?”

5. “Help me design a simple, low-effort way to monitor faint signals for [insert one candidate category]. What sources, search terms, or data points should someone check monthly to catch early movement?”

The Strategy You Already Own, But Never Deploy

Somewhere in your leadership team’s meeting notes from last year sits a decision that probably didn’t feel like much of a decision at the time: wait, and see how this AI wave settles before committing to anything. It felt sound in the moment. Nobody in the room had a clear read on where things were headed, generative AI was still new enough that predictions felt like guesswork, and plenty of executives could still remember the dot-com collapse, when doing nothing turned out to be the smartest move a lot of firms made. Caution had worked before. Why wouldn’t it work again?

A year has passed since then. Walk the halls of your own organization and not much has changed: same teams, same processes, same planning cadence you had this time last year. Walk outside those halls, though, and the picture looks very different. Plenty has changed, and most of it happened somewhere you weren’t watching closely.

That gap is the part worth sitting with. The instinct that once looked like prudence now looks, on closer inspection, like exposure. Competitors are shipping products that would have taken your own team a full planning cycle just to get approved. You’ve heard the rumors, maybe more than rumors, of firms in your industry that dragged their feet and are now quietly winding down. Nobody on your leadership team wants to say it out loud, but the question is sitting in the room anyway, unasked: what if the real danger was never the disruption itself, but standing still while the ground under it kept shifting?

Here’s a fact worth revisiting, because most executives have heard it once and never thought about it again. Back in 2016, Jeff Bezos wrote to Amazon’s shareholders about what it takes to avoid sliding into complacency and eventual irrelevance. One of his four rules was the “eager adoption of external trends.” His logic was blunt: fight a trend and you’re fighting the future. Embrace it, and that same force instead becomes a tailwind pushing you forward.

That letter is nearly a decade old now. It gets quoted often enough in strategy decks and leadership podcasts. What almost nobody has done is build it into how they actually plan.

Two Failures, One Root Cause

Companies that freeze when a wave is clearly visible on the horizon tend to end up in roughly the same place: a diminished version of what they once were. Kodak is the example everyone reaches for first, and for good reason. Its own engineers invented the core technology that eventually replaced its film business, and the company still couldn’t bring itself to act on what it had built. Blockbuster watched a smaller, quieter rival mail out DVDs and later stream movies directly into people’s living rooms, and treated the whole thing as a niche experiment rather than an existential signal. Xerox PARC is the strangest case: its researchers built the graphical interface and elements of what became the personal computer years before almost anyone else had the concept, then watched other companies commercialize both while Xerox itself moved on.

Sears looks, at first glance, like the exception — a company that eventually did act. But by the time it moved, the moment for genuine structural change had already passed. What followed wasn’t a correction so much as a scramble that looked like decisiveness but never addressed the underlying planning failure. It was the same failure as Kodak’s or Blockbuster’s, just delayed and dressed up as urgency instead of paralysis.

That’s the part people consistently miss. Panic and paralysis aren’t opposites, even though they look nothing alike from the outside. They’re the same mistake, playing out on two different timelines. One postpones the decision indefinitely. The other skips the decision entirely and replaces it with visible motion. Neither one does the actual work of deciding where the company is headed.

The Busywork That Isn’t a Decision

If your organization has responded to generative AI at all, it’s probably done something visible, something you could point to on a slide if a board member asked what the company was doing about it. A pilot project here. An AI task force there, staffed by people who already had full-time jobs before this got added to their plate. A chatbot bolted onto customer service, mostly answering questions the FAQ page already answered. A dashboard tracking “AI trends to watch.” Maybe even a reorg, complete with a shiny new title for whoever now formally owns “AI strategy,” even though nobody’s strategy actually shifted as a result.

Every one of these things is real. Money got spent. Hours got logged. And yet none of them is, in any meaningful sense, a decision.

There’s a useful, if slightly dark, image for what’s happening here: the passengers on the Titanic who spent their final hour rearranging deck chairs. Not because it would help, but because doing something felt better than sitting with the discomfort of a decision not yet made. Most corporate responses to AI disruption look a lot like that scene: visible, energetic, and disconnected from anything that would actually change how the company decides what to build or where to invest.

Why the Old Playbook Stopped Working

During the dot-com era, waiting genuinely was a defensible strategy for a lot of companies, and it’s worth being honest about that rather than pretending caution was always foolish. If you sat out a cycle back then, you could usually catch the next one without much cost. Technology moved fast by the standards of the day, but slowly enough that a delay could be absorbed and corrected later. That was the safety cushion “wait and see” was built on, and for a long time it held up.

That margin has disappeared. A year lost to indecision today doesn’t come back next year, because the landscape itself won’t be the same one you paused in front of. Whatever assumptions justified the pause will likely be out of date by the time you revisit them. The runway you thought you had when you first decided to wait keeps getting shorter while you’re still taxiing down it, and there’s no obvious moment when someone announces it has run out. You just eventually notice you’re airborne with nowhere safe to land.

The alternative to freezing isn’t speed for its own sake. It’s the kind of long-horizon thinking that lets a leadership team see the whole shape of where things are heading — not just next quarter’s numbers or even next year’s roadmap, but the version of the industry that plausibly exists two or three decades out. That’s a considerably harder discipline to build than launching a pilot program, because it asks executives to commit to a direction before all the evidence is in. It’s also the only discipline that lets a trend like AI actually become a tailwind instead of a threat, because a tailwind only helps you if you already know which way you’re sailing.

The Cost of Ignoring Long Cycles

There’s a pattern worth borrowing from an industry that has nothing to do with software, which is exactly what makes it useful. Tree crops, cocoa, coffee, certain timber varieties among them, take years to mature after planting, and considerably longer still to reach peak yield. A grower who doesn’t plan a full decade ahead ends up, eventually, with an aging, under-producing plantation and no fast way to fix it. You can’t will a tree into maturity by working harder once the shortfall is already visible. The lead time is the lead time, fixed by biology rather than ambition or budget.

Something structurally similar is happening with the physical infrastructure behind AI itself. Building a new advanced semiconductor fabrication plant, the kind of facility that manufactures the chips training and running today’s large models, takes roughly three to four years from decision to operation, and billions of dollars in committed capital. I’d encourage you to verify that figure against current industry reporting, since capacity plans are shifting quickly. But the point holds regardless of the exact number: companies only now deciding to secure long-term compute capacity are, in effect, planting a tree they needed to plant several years earlier. There’s no accelerated version of that decision available now, no matter how much budget they’re suddenly willing to throw at it.

Short-cycle thinking doesn’t just delay a decision and leave it waiting patiently to be made later. It quietly forecloses options that can no longer be recovered on a short timeline, no matter how much urgency shows up afterward. Some doors, once missed, don’t reopen just because the company finally noticed them.

What Actually Breaks the Pattern

When I raise timelines like these with executives, the reaction is often disbelief, sometimes mild irritation. Surely the cultural shift their own organization needs can happen in a quarter or two, not years. It’s a comforting assumption, and it’s usually wrong. Cultures, like tree crops and fabrication plants, run on their own clocks. They don’t move faster just because a deadline is approaching.

The antidote to wait-and-see was never a faster reaction, even though that’s the instinct most organizations reach for once the discomfort of standing still becomes too much to bear. The real antidote is a longer view, deliberately and structurally built into how the company plans. That means a genuine long-horizon strategy, one that looks fifteen, twenty, even thirty years out, rather than a rolling set of one-year guesses dressed up in five-year language. That kind of thinking doesn’t eliminate uncertainty, and it isn’t meant to. What it does is give a company a fixed point far enough out on the horizon that even as the path toward it bends or gets rerouted entirely, the organization keeps moving instead of freezing at the first sign of ambiguity.

That’s the tailwind Bezos described almost a decade ago. It was never a secret, and it was never complicated to state. It has just rarely, if ever, been built.


PS: Five prompts to work through with your own AI assistant

  1. “Here’s how my company has responded to AI disruption so far [describe your pilots, task forces, or initiatives]. Help me identify which of these are genuine strategic decisions and which are ‘deck-chairing’ — visible activity that doesn’t change how we actually decide things.”
  2. “Walk me through what a 15-to-20-year horizon for my industry might plausibly look like, given current AI and automation trends. What would have to be true for my company to thrive in that version of the future?”
  3. “I want to test whether my organization is in ‘wait-and-see’ mode without realizing it. Ask me a series of questions that would reveal whether we’ve actually made a strategic decision about AI, or just delayed one.”
  4. “Help me draft three or four scenarios for how AI could reshape my specific industry over the next decade, ranging from gradual to disruptive, so my leadership team can pressure-test our current plan against each one.”
  5. “I want to explain to my board why ‘we’re waiting to see how this settles’ is riskier than it sounds. Help me build a short, non-alarmist argument, using examples of companies that lost their advantage through delay rather than through acting.”

The Strange Thing Successful CEOs Do Before They Fail

Picture a boardroom anywhere in the world. A new strategic plan is about to be built, and it follows a stretch of disappointing results. Someone at the table believes the old plan deserves an honest look before anyone writes a new one. The rest of the room disagrees, and the person leading that resistance is the chief executive.

This scene repeats itself constantly, across industries and continents, in companies large and small. And it repeats for a reason that has surprisingly little to do with the numbers on the page.

Somewhere in that room, someone already knows what went wrong. They stay quiet, and not because they lack nerve. Often the silence exists because the one person who most needs to hear the diagnosis has quietly turned the plan’s failure into a verdict on himself.

This has a name, though it is rarely the name people reach for. It isn’t stubbornness, and it isn’t ego in the casual sense most people mean when they use the word. It’s something closer to fusion: the CEO’s sense of identity has welded itself to the authorship of the plan. Criticizing the plan starts to feel indistinguishable from criticizing the man.

The Instinct to Diagnose the Leader

The common response to a struggling CEO is to assume he needs more self-reflection. That diagnosis feels intuitive, and it is usually wrong.

Executive coaches who work with senior leaders will tell you something consistent: top performers tend to run high on confidence, and sometimes on narcissism. Wins get filed under personal skill. Losses get filed under bad luck, timing, or a market nobody could have predicted. Which means owning a failure takes real effort, precisely because nothing in the leader’s usual operating system asks him to.

So what actually moves a confident leader to let go of a plan he built?

Three well-documented cases suggest an answer, and it isn’t introspection triggered by failure. It’s something closer to a deliberate choice, made from strength rather than crisis.

Garry Ridge spent over two decades running WD-40, and built one of the most studied culture turnarounds in modern business on a simple, command-driven mantra: be brilliant, be brief, be gone. At some point that mantra stopped fitting the company he wanted to build. He later described the shift in five plain words: he couldn’t do it alone.

Alan Mulally took over a struggling Ford and steered it through the 2008 financial crisis without the government bailout its competitors needed. About the plan that made that possible, he said something equally direct: it was bigger than him.

Satya Nadella went a step further at Microsoft. Rather than simply saying the company’s direction wasn’t his alone, he dismantled the senior leadership structure built to run things that way, on the theory that no single person, including the CEO, should hold that much of the answer.

None of these three men were failing when they made that call. Each was already succeeding, with every reason to keep doing exactly what had gotten him there. Yet each one gave up sole ownership of his company’s direction anyway, voluntarily, before a board or a crisis forced the issue.

That timing matters more than it first appears. It suggests the shift isn’t a symptom of failure, something a leader is forced into once the results turn bad. It’s a decision available to any leader, in good times or bad, and the best ones make it deliberately, long before anyone hands them a reason to.

Rejecting a Popular Premise

Ridge, Mulally, and Nadella weren’t managing their egos more skillfully than other executives. They were rejecting an assumption most organizations never examine: that a company’s direction is supposed to be authored by one person at the top, the way a founder might write a mission statement on a napkin and hand it down as scripture.

That assumption carries a flaw most boardrooms never name out loud. A company’s direction isn’t handed down from a single mind, however talented that mind happens to be. It gets surfaced collectively, through the accumulated judgment of the people running the business day to day, closest to the customers and the friction points a CEO rarely sees firsthand. The more a leader treats that direction as personal property, something he built and therefore owns, the more fiercely he will defend it against the one exercise that could actually improve it: an honest post-mortem.

The Same Reflex, Wearing Two Faces

This reflex shows up differently depending on how the last plan went, which is part of why it goes unrecognized so often.

When a leader senses the prior strategy failed, he tends to suppress honest discussion about it. Even a carefully facilitated review can land like an accusation rather than an exercise, and the room adjusts accordingly, softening its language until the review says almost nothing useful at all.

When a leader believes the prior strategy succeeded, the resistance shows up dressed differently, but the underlying mechanism is identical. Success gets defended as proof that nothing needs to change. This is the same instinct that kept a dominant film company comfortable with film long after digital cameras arrived, kept a video rental giant comfortable with physical stores while streaming quietly took over living rooms, and has repeated itself across a long list of once-dominant firms convinced that what worked before would keep working. Confidence in past results becomes the very thing that blocks an organization from spotting the threat forming just outside its field of view.

Failure resists a post-mortem out of self-protection. Success resists it out of certainty. Both come from the same place: a leader who has made the plan’s outcome personal, whichever direction that outcome happened to run.

There is a third variation worth naming, quieter than the other two. Some leaders resist not because the result was clearly good or bad, but because it was ambiguous, and ambiguity is harder to defend than either extreme. A mixed result invites the most debate, and debate is exactly what identity fusion is built to avoid.

What a Colleague Can Actually Do

If you aren’t the top leader, and you sense your CEO is standing in the way of an honest review, pressure rarely works. Direct confrontation tends to trigger the very defensiveness you’re trying to move past, and most people who have tried it once rarely try it the same way twice.

A better move is reframing the role itself. Help your CEO see himself less as the sole author of the company’s direction and more as its chief learner, or its lead experimenter, someone whose job is to keep testing the plan rather than defend it. That single shift in self-perception does more work than any argument about specific numbers ever will.

Ridge, Mulally, and Nadella are useful here, not as inspiration but as evidence. Each one answered the same question at the height of his influence, when nothing outside forced the admission: whose plan is this supposed to be?

Now picture your own CEO hearing that question, in your own boardroom, this week. He is still resisting the post-mortem, and you are still deciding how hard to push. The better question isn’t how hard. It’s which question you ask.

Not a challenge to his judgment. An invitation to a role he likely never chose for himself, and one he remains entirely free to choose now, at whatever stage his company’s story happens to be in.

——————————————-

PS: Five prompts to take this further with an AI assistant

  1. “I lead a team where a senior leader seems to be personalizing a past strategic failure. Help me identify three signs this is happening, based on the psychological pattern described in this article.”
  2. “Using the Ridge, Mulally, and Nadella examples, help me draft a short, low-pressure way to raise the idea of a strategy post-mortem with my own leader, without it sounding like a criticism.”
  3. “Walk me through the difference between a leader resisting a post-mortem out of failure versus resisting one out of past success. Which pattern sounds more like what I’m seeing in my own organization?”
  4. “Help me design a simple post-mortem process for my team’s last strategic plan that treats the findings as collective, not as an evaluation of any one person.”
  5. “If I wanted to reframe my own role from ‘owner of the vision’ to ‘chief learner,’ what would that change about how I lead the next planning cycle? Help me think through three concrete differences.”

Ep 37 Why Global Conflict Has Your C-Suite Knee-Jerking Strategy Once Again

Your company prides itself on its long-term thinking, planning and acting. But now that times are difficult due to the outbreak of a war, you are wary of what might happen given your experience of COVID, supply chain breakdowns and sudden tariffs.

During these extreme events, you saw C-Suite executives delve into the weeds, doing the work of managers. As their time horizons shortened, they ignored the big picture until well after the crisis passed. This meant lost opportunities, and a lack of preparation for future threats.

How should you intervene given that it appears as if the roots of long-term thinking are weaker and shallower than you thought?

In this episode we look at your leadership system and where it lacks disciplined practices for long-term focus.

This is a public episode. If you’d like to discuss this with other subscribers or get access to bonus episodes, visit longtermstrategy.substack.com/subscribe

Culture Isn’t Killing Your Strategy. Silence Is.

You built a strategic plan. Leadership signed off. It launched with fanfare. Six months later, engagement scores are worse, not better, and someone in the room says it: “Culture eats strategy for breakfast.”

That line isn’t wrong. It’s just not useful. It gives everyone permission to stop looking.

Take a CEO — call her Elena. She ran the full rollout playbook: division townhalls, a slick explainer video, a one-page summary, focus groups to gather feedback. A month later, her engagement survey showed staff more confused about direction than before the rollout began. Her leadership team had a ready explanation: culture. Discipline. Willpower. The usual suspects.

None of them held up. Elena’s people weren’t lazy or resistant. They’d been talked at, thoroughly and repeatedly, by a strategy that never once talked back.

The Direction Problem

Strip away the blame-shifting, and the actual defect is structural: every channel Elena used ran in one direction only. Town halls, PDFs, infographics, cascaded briefings from managers — all of it broadcasts. None of it lets an employee bring their specific situation into the conversation and get a specific answer back. (Most town halls don’t result in real Q&As even if they are repeatedly requested.)

For most of business history, this didn’t matter, because one-way was the only method available. A shift is now underway.

I recently spoke with B. Joseph Pine II, whose new book The Transformation Economy argues that real value increasingly comes from experiences that change the person going through them, not just inform them — moving someone from a passive recipient of information into a different, more capable version of themselves. Applied to strategy rollout, that’s the distinction: informed staff know the plan exists. Activated staff have engaged with it directly enough that it’s changed how they act.

Every manager has watched this happen in miniature. An employee seeks out a mentor. A handful of real conversations later, that person works differently. It’s not mysterious. It’s just expensive, or time-prohibitive, to do at scale — which is exactly why most organizations quietly substitute something cheaper for it.

The Substitutes That Don’t Work

Faced with the cost of scaling real conversation, most companies reach for a lookalike instead:

  • The FAQ document — answers questions anticipated in advance, not the one the employee actually has.
  • The all-hands Q&A — technically interactive, but only a few brave voices ever speak; everyone else spectates.
  • The manager cascade — assumes every supervisor can personalize a strategy for each report, without ever giving them a tool to do it.
  • The engagement survey — captures a reaction, then feeds it into a report acted on months later, if at all.

Elena’s confusion was built from exactly this list. So is most organizations’. None of it is communication in any sense that produces change — it’s distribution.

There’s a fifth, sneakier substitute worth naming directly: the strategy chatbot. Many leadership teams believe they’ve already solved this problem with an AI tool.

Look closely and it’s usually a scripted FAQ bot wearing an AI label — competent at retrieving pre-written answers, useless at helping someone reason through what the strategy means for their actual role. It’s the imitation of the solution, not the solution.

What Real Activation Looks Like

Genuine one-to-one, AI-enabled activation is a different animal, and it’s already running inside serious organizations.

At Sumitomo Mitsui Financial Group, one of Japan’s largest banking groups, employees can now consult an “AI CEO” — a tool modeled on Group CEO Toru Nakashima’s own management thinking, built to help staff refine proposals and think through strategic direction, rather than simply announce it to them.

At the Norwegian School of Economics, researchers built an AI interview bot modeled on their own rector, Helge Thorbjørnsen, and sent it out to conduct one-to-one conversations with more than 800 students, staff, alumni, and partners over a few weeks. The result was the most comprehensive stakeholder input the institution had ever gathered for a strategy process — and, notably, people said more to the AI, unscripted, than they typically say in an anonymous survey.

Neither of these is a chatbot answering FAQs. Both put the person on the other end of a realistic exchange, where their specific situation shapes the response they get back.

A newer tool aimed squarely at this gap is Contextuum AI, software built specifically to convert one-way strategy communication into real-time, interactive decision support. Rather than delivering the plan as a document, it drops employees into role-based simulations that force them to make the same strategic choices their job actually requires — turning a plan they’d otherwise skim into a set of decisions they’ve already practiced making.

The Shift This Requires

The old assumption was: staff has been told enough times; that should be sufficient. The better standard is: communication has only really begun once staff can give useful, specific feedback back into the strategy — and see that feedback change something.

That’s a genuinely different kind of rollout. It doesn’t start with a document dump. It starts by putting each employee into a live exchange — AI-powered, individualized, ongoing — where their first real encounter with the strategy is active, not passive.

Elena didn’t need another town hall. She needed a channel that could talk back.

The next time your organization launches a strategy and momentum stalls, resist the easy explanation. Culture didn’t eat it. Silence did — and silence has a fix.


PS — Five prompts to use with your own AI assistant

  1. “Here’s our current strategy summary [paste it]. Ask me questions, one at a time, about how this applies to my specific role — and don’t move to the next question until my answer makes sense to you.”
  2. “I’m a manager trying to cascade this strategy to my team without garbling it. Interview me about my team’s day-to-day work, then help me translate the strategy into three concrete implications for them specifically.”
  3. “Play devil’s advocate: what are the three most likely reasons this strategy quietly fails to get implemented in an organization like mine? Push back on my answers until we land on the real risk, not the comfortable one.”
  4. “Based on what I’ve told you about my team’s actual work, draft two or three questions I should be asking my own staff — not townhall questions, but ones that would surface whether they’ve actually understood how this changes their work.”
  5. “Six months from now, what evidence would tell us this strategy was genuinely activated rather than just announced? Help me define that before we start, not after.”

The One Diagnostic Step Every Failed AI Rollout Skipped

There are two ways a board loses confidence in a CEO’s AI strategy. One is watching a rushed rollout blow up in public. The other is watching nothing happen, quarter after quarter, while rivals pull ahead. Leaders treat these as opposite sins — one of recklessness, one of paralysis. They are the same sin wearing two costumes.

Consider a government vehicle-inspection office. For years, getting a car certified meant a wasted morning: unexplained queues, arbitrary waits, a process nobody could explain and everybody dreaded. The clerks weren’t the problem. They were as trapped in the system as the drivers standing in line.

When the office was finally redesigned, the fix didn’t come from the counter staff working harder. It came from above — from leadership finally treating the process itself as something to be mapped, tested, and rebuilt. Decades of avoidable frustration turned out to be a leadership failure wearing a service-counter disguise.

That’s the pattern behind almost every stalled or embarrassing AI rollout today: cause and effect get separated. The department that visibly breaks is rarely the one that made the mistake. The quarter where the failure shows up is rarely the quarter where it was made. That lag is exactly why the rushed CEO and the frozen CEO can’t see they share a cause. Skip the diagnosis, and the bill arrives later — as a scrapped pilot, a quiet rollback, or a board that’s run out of patience. Each time, it looks like an isolated, unrelated event. It isn’t.

The Proof Is Piling Up

This isn’t a resource problem, and it isn’t confined to one company, sector, or country.

Starbucks spent nine months running an AI tool meant to automate beverage-inventory counts across its North American stores, before quietly retiring it after the system kept miscounting and mislabeling items, such as confusing similar milk types. Ford has been rehiring and promoting more than 350 experienced engineers after automated quality-control systems failed to capture the expertise of veteran employees. Commonwealth Bank of Australia replaced dozens of customer-service staff with an AI voice bot, then had to reverse the job cuts when the system couldn’t keep up and call volumes climbed. IBM automated large parts of its HR function, discovered the tool could resolve routine requests but stumbled on anything requiring judgment, and announced plans to triple its U.S. entry-level hiring soon after. A widely cited MIT study found that 95% of enterprise generative AI pilots fail to deliver measurable returns.

None of these were companies short on capital, talent, or enthusiasm. Every one of them had the AI capability. What none of them had was a diagnosis of the underlying process before the tool was chosen.

What Got Lost

That’s understandable, in a way. Most companies today are wide open to AI because their own stakeholders are demanding they keep up. A new tool appears, it gets deployed, and results get measured afterward. That works fine when the change is as simple as installing a new printer. It fails the moment the process underneath is genuinely complex — which is most of the time. What’s missing is the step where the existing process gets mapped, stress-tested for bottlenecks, and redesigned before automation is even on the table.

Both the rushed CEO and the frozen CEO would benefit from the identical corrective move — not “go faster,” not “go slower,” but insert the diagnostic step neither is in the habit of taking.

If that sounds obvious, it’s worth asking why so many organizations quietly abandoned it. Process management — mapping, testing, and redesigning core operations — was standard executive discipline in the 1990s, built on Total Quality Management, Lean, and the Theory of Constraints. Somewhere along the way, leadership teams let it lapse. The lesson hasn’t gone anywhere; it’s just been sitting unused. Years before generative AI, executives attempting Robotic Process Automation without first doing this work were warned by experts that skipping it was a recipe for failure. The warning was accurate then. It’s still accurate now, just louder.

There’s a second reason the step feels skippable: nearly every executive has personally felt AI work well. Ask ChatGPT or Claude a question on your phone, and an articulate, confident answer arrives in seconds. That experience quietly convinces leaders that AI should transform every part of the business with the same ease. But personal productivity gains and enterprise-wide transformation are not the same category of problem. Real organizational change requires the unglamorous work of scoping, staffing, and sequencing multi-year projects. There is no shortcut from a good chatbot answer to a redesigned supply chain.

One Reveal Worth Adding

In other podcast I have drawn a sharp line between planning and strategy: planning extrapolates from what you’re already doing, while strategy forces a real choice that involves tradeoffs. Most AI “strategies” are actually AI plans — lists of tools to deploy, extrapolated from what competitors are doing, with no binding constraint identified and no real choice made. A genuine AI strategy starts by asking which single process constraint, if resolved, would unlock the most value — and works backward from there. Everything else is activity dressed up as strategy.

The Actual Fix

The CEOs who rush and the CEOs who freeze are both missing the same discipline — not courage, not caution, but the willingness to slow down at the exact moment everyone else is speeding up. The rushed CEO skips the diagnosis to look decisive. The frozen CEO avoids it to look careful. Neither has done the work.

The fix isn’t a faster rollout or a longer pause. It’s a process that’s been mapped and stress-tested before a single tool gets chosen. Boards don’t ultimately reward the leader who moved first or the one who moved last. They reward the one who knew where to look before moving at all.


PS: 5 Prompts to Use With Your Favorite LLM

Copy these into Claude, ChatGPT, or your assistant of choice to apply the article to your own organization.

  1. Find your lag. “Walk me through a recent failure or slowdown in my organization. Help me trace it backward — what department, decision, or process choice from 12–24 months ago might actually be the root cause, even if it doesn’t look connected on the surface?”
  2. Spot your substitute behavior. “I’m about to approve/reject an AI tool for [describe the process]. Before I decide, ask me questions that test whether I’ve actually mapped this process and identified its bottleneck — or whether I’m just reacting to pressure to ‘do something.’”
  3. Run a mini process diagnosis. “Here’s how [a specific process] works today, step by step: [describe it]. Identify the most likely bottleneck, and tell me what would need to be true for automating this process to actually help rather than just move the bottleneck somewhere else.”
  4. Test for real strategy vs. planning. “Here’s my current AI roadmap: [paste it]. Using Roger Martin’s distinction between planning and strategy, tell me honestly whether this is a strategy — with a real choice and a clear binding constraint — or a plan that’s just a list of tools.”
  5. Pressure-test your own excuse. “I’m the CEO/leader in this situation: [describe whether you’re moving fast or holding back on AI]. Play devil’s advocate and challenge me on whether my current pace is actually a disguised way of avoiding a proper process diagnosis.”

The Missing Rung: Why Your Innovation Efforts Remain Uninspiring and Empty

As the person responsible for driving innovation in your organisation, you have probably sat through a version of this conversation more than once.

The leadership team agrees that a new category is needed. Everyone nods. A workshop is scheduled. Consultants are hired, sticky notes are deployed, and three months later the team resurfaces with a list of incremental improvements dressed up in the language of transformation. Nothing changes. The cycle repeats.

This is not a talent problem. It is not a budget problem. It is not even a creativity problem — though it will feel like one. It is a navigation problem. And the reason it keeps recurring is that most organisations begin every innovation effort from the same invisible assumption: that they already know what kind of thing they are trying to become. They don’t. And without that clarity, no workshop, no consultant, and no off-site retreat will produce a genuinely new category. You will keep generating better versions of what you already are.

There is a framework that changes this calculus entirely. It arrived quietly, in a new book by Joe Pine — the same strategist who gave executives The Experience Economy twenty-five years ago and reshaped the way the world thought about what companies actually sell.

What a Category Actually Is

Before you can design a new category, you need a precise definition of what a category is. In business, a category is not a filing label or a market segment. It is a space in people’s minds — the mental frame that allows a customer to understand what a product is, where it belongs in their life, and why it matters. “Smartphone,” “microwave oven,” and “streaming service” are all categories that someone invented. Each one began as an answer to a need that customers had not yet been able to name.

Category design — the deliberate act of creating a new mental frame rather than competing inside an existing one — is widely discussed and rarely achieved. Most executives who attempt it eventually conclude that it requires a creative leap they cannot engineer. That conclusion, it turns out, is wrong. What it actually requires is a ladder.

The Ladder Most Executives Have Only Seen Half Of

Pine’s original insight, from The Experience Economy, was that organisations don’t just sell things — they offer value at different levels, and those levels form a hierarchy. At the bottom are commodities: undifferentiated raw inputs where price is everything. Above that are products: manufactured goods with consistent specifications. Above that are services: activities performed on behalf of the customer. And above that are experiences: carefully staged events that engage customers emotionally and memorably.

Every hotel in the world, for example, offers a blend of products and services — a room, a meal, a concierge. A smaller number have moved up to experiences: the Marriott’s flagship properties with their signature design and curated atmosphere. Sandals, in the Caribbean, built an entire brand around the all-inclusive experience category. Each of these companies moved up Pine’s ladder deliberately, and each time they did, they left their competitors arguing about price on the rung below.

Here is what Pine’s original framework did not include — and what his new book, Transformation Economy, now adds. There is a fifth rung. Above experience sits transformation: an offering that does not merely engage or delight the customer, but permanently changes them. Not their situation. Not their environment. Them — their skills, their identity, their capabilities, their trajectory.

This rung exists in every industry. In most, it is unnamed, unclaimed, and therefore available. It is the most defensible category a company can occupy, and the hardest to copy, because transformation is not a feature. It is a relationship with a long-term outcome.

Rung Invisibility: The Hidden Reason Innovation Stalls

Most companies have never asked which rung they currently occupy. They operate without a precise definition of their own offering type, which means that when they sit down to innovate, they have no fixed starting point. Call it rung invisibility: you cannot climb toward a destination you cannot see.

This is the innovator’s dilemma in its most structural form. It is not that successful companies refuse to innovate — it is that they keep innovating on the wrong rung. They add features to products, extend services, improve experiences, and call it transformation. The ladder makes the distinction visible. Once you can see the rungs, you can locate yourself accurately, name the next rung, and build toward it with precision.

Waiting With a Destination in View

In 2007, Andrew Ng began uploading his Stanford computer science lectures to the internet. The vision was clear: university-quality education, accessible to anyone, anywhere, free. What was not yet ready was the road. Broadband penetration was uneven. Streaming infrastructure was immature. Mobile adoption had not reached the scale required. The concept of learning via video had not yet been normalised for a mass audience.

Ng spent five years building precursors, testing formats, and watching the infrastructure mature. When Coursera launched in 2012, it was not because the idea had finally arrived — it was because the enabling conditions had. MasterClass followed a similar logic: the transformation offering was clear (learn directly from the world’s best practitioners, not just their subject matter), but the model required cinematic production quality and broadband capable of delivering it at scale. Both companies launched not when they were ready, but when the world was.

This is a categorically different posture from running innovation workshops. It is not luck. It is not serendipity. It is the discipline of naming a destination — a specific rung, a specific transformation offering — and then building the long-term strategy around the conditions that will make the climb viable. Pine himself waited over twenty-five years to write Transformation Economy. As he has said, the world simply wasn’t ready before now.

Corporate Inspiration at Its Finest

As a leader, you have probably tried to inspire your organisation through personal energy — motivating speeches, bold vision statements, off-site retreats designed to generate momentum. When the results are mixed, the temptation is to conclude that you need more charisma, a better facilitator, or a more compelling narrative. You don’t. What you need is a structure that does the inspiring for you.

This is what Pine’s ladder offers when it is embedded in a corporate strategy: inspiration that lives in the architecture of the plan itself. Aspirational but credible. Fact-based. Free of hyperbole. Specific enough to span a decade without losing its force. When employees understand not just what the company does today but which rung it is climbing toward — and what conditions the organisation is watching for — they engage differently. The destination gives their work a direction that no workshop can manufacture.

Steve Jobs was explicit, in at least one public interview, that Apple’s strategy was to wait — to define the destination clearly and hold it until the technology matured enough to make the climb possible. Inside Apple, the roadmap to the iPhone and iCloud gave those who knew it something to work toward that transcended any individual product cycle. That kind of inspiration is structural, not charismatic. It is replicable. And it begins with locating yourself honestly on the ladder.

What to Do Next

Every organisation, without exception, can do this. The transformation rung exists in your industry. It is almost certainly unnamed. The fact that it is unclaimed is not a warning — it is an invitation.

The work begins with three questions. What rung does your organisation currently occupy — precisely, not aspirationally? What would a transformation offering look like in your sector: what would it permanently change about your customer? And what enabling conditions — technological, cultural, regulatory, infrastructural — are not yet mature, but are on their way?

The EndPoint Method offers one systematic approach to answering these questions within a long-term strategy process. But the starting point is available to any leadership team willing to look at the ladder honestly and ask where they are.

Innovation is not a creativity problem. It is a navigation problem. Pine’s ladder is the instrument. The fifth rung is waiting.

PS — Five Prompts to Take This Further

Use these with any AI assistant (Claude, ChatGPT, or similar). Replace the bracketed text with your own details.

Prompt 1 — Locate your rung “I work in [industry]. Our core offering is [brief description]. Using Joe Pine’s five-rung ladder — commodities, products, services, experiences, transformations — help me identify which rung we currently occupy and what evidence supports that assessment. Be precise, not flattering.”

Prompt 2 — Define the transformation offering “In the [industry] sector, what would a genuine transformation offering look like? Define it using Pine’s standard: an offering that permanently changes the customer themselves, not merely their situation or experience. Give me three specific examples of what this could mean for a company like [company type].”

Prompt 3 — Map the enabling conditions “The transformation offering I want to build is [brief description]. What external conditions — technological, cultural, regulatory, or infrastructural — are not yet mature enough to support this at scale? Which of these are likely to mature in the next five to fifteen years, and what signals should I be watching for?”

Prompt 4 — Diagnose your innovation process “My organisation runs [describe your current innovation process — workshops, sprints, planning cycles]. Using the concept of rung invisibility — the idea that companies cannot innovate toward a destination they cannot see — identify the specific points in our process where the absence of a named transformation rung is likely to be causing us to recycle existing assumptions.”

Prompt 5 — Draft the strategic narrative “Help me write a one-page internal strategic narrative for my leadership team that: names our current rung on Pine’s ladder, defines the transformation offering we are building toward, identifies the two or three enabling conditions we are watching, and explains why this is a navigation strategy rather than a creativity exercise. Tone: direct, credible, free of consultant language.”

P.S. The LTSP26 Conference is open for registration here on Linkedin. https://www.linkedin.com/events/7475287796359028737?viewAsMember=true. Part of the lineup will feature Category Cathy, an interactive AI persona with unique knowledge of work by experts like Joe Pine, author of Transformation Economy.

The CEO Who Solved Everything and Inspired No-one

You are putting in serious effort to motivate your team — and it still isn’t working. The hours are long, the intent is genuine, and the results are stubbornly flat. Before you blame your communication strategy, your budget, or your personality, consider a different diagnosis entirely.

Two fictional CEOs illustrate the problem.

Marcus is a decisive firefighter. He earned his position by tackling the problems nobody else would touch, and he has been doing the same thing ever since. Elena takes a more consultative path. She commissions engagement surveys, listens carefully to what staff say, and builds action plans from the results.

Yet both are looking at the same uncomfortable numbers: absenteeism climbing, burnout reports rising, and employees quietly asking each other, “Where exactly are we headed?” Both assume the problem is in the delivery — the messaging, the resources, the rollout. They are looking in the wrong place.

The actual diagnosis is a pattern called “Follower-Friendly Failure.”

The Same Mistake in Different Clothes

Follower-Friendly Failure is the attempt to build organisational momentum by removing friction. Fix the complaints. Address the survey results. Solve the urgent problems. The instinct is generous — leaders genuinely want to make things better for their people — but the strategy is structurally flawed.

Marcus and Elena look like opposites: urgent problem-solver versus consensus-builder. But they are making the same error in different packaging. Their failure is not in how they lead. It is in what they are leading toward — or rather, the absence of any clear answer to that question.

Elena’s approach is particularly instructive. Aggregating staff concerns produces a politically safe wish list, not a strategy. It assumes that resolving individual frustrations will compound into collective motivation. It won’t. Addressing one round of complaints simply surfaces the next round. The circle is vicious, and staff eventually exhaust themselves chasing problems that regenerate faster than they are solved.

The missing ingredient is not smarter problem-solving. It is a destination.

In this context, a destination is not a goal, a value, or a problem to be solved. It is a specific, vivid picture of where the organisation will stand at a defined point in the future — real enough that an ordinary person can orient themselves toward it.

What Political Science Reveals About Leadership

Research on voter behaviour offers an unexpected window into how destination-clarity functions as a loyalty mechanism. Studies of Donald Trump’s coalition have consistently found that roughly 25–35% of his supporters privately dislike specific policies, find aspects of his persona difficult, and disagree with particular decisions. They back him anyway.

The reason is not charisma, party loyalty, or agreement with the plan. It is agreement with the destination. These voters know where he says the country is going, and that clarity holds them even when the specific steps, or personal foibles do not.

The organisational parallel is direct. Every leadership group contains a subset of destination-first followers — people who will tolerate management friction, imperfect policies, and even a leader they find personally disagreeable, provided they can see clearly where the organisation is headed. Marcus and Elena have no mechanism for reaching this group because neither has named a destination unambiguous enough to reach them.

This is what Dr. Riel Miller, a UNESCO senior adviser, calls Futures Literacy: the capacity to use the future as a resource for acting in the present. It requires holding the future genuinely open — treating several possible destinations as real — until a single, unambiguous endpoint is chosen. Once that commitment is made, something shifts. Inspiration and discretionary effort are not manufactured through communication techniques. They are released.

This distinction matters more than most leadership development programmes acknowledge. Charisma, communication skill, and policy competence are all useful. But none of them substitute for a destination that employees can inhabit in their imagination before they inhabit it in reality

The Leading Indicator No Dashboard Captures

Executives searching for evidence that a strategy is working typically reach for lagging indicators: engagement scores, C-suite alignment, project milestones, revenue shifts. These confirm what has already happened. They do not tell you whether the organisation is actually moving.

There is a better signal, and it costs nothing to detect.

Consider an employee — call her Jody — who works in a mid-level, non-senior role. Her department has been identified as high-leverage: it sits in the 20% of organisational effort that drives 80% of strategic results, directly connected to a 15-year destination the company has committed to.

Without a clear destination, that leverage is invisible to Jody. She spends Monday doing what she did the Monday before. This is not apathy. It is a rational response to ambiguity. When no clear endpoint exists, the safest professional behaviour is to replicate what worked yesterday. Jody is not the problem. The missing destination is.

With one — a specific, unambiguous endpoint she can picture and act toward — something different happens. On Monday morning, unprompted by her manager, she spends three hours doing something she has never done before: taking deliberate actions aligned with where the organisation says it is going. Not because she was told to. Because she can see the destination and has decided to move toward it.

Notice what did not cause this shift: not a town hall, not a revised KPI framework, not a team-building exercise. The destination did the work. Her manager’s job, once the destination is clear, is largely to stay out of the way.

That behaviour — one ordinary person in a non-senior role doing something genuinely novel in alignment with the stated direction — is the leading indicator that a strategy is alive. Engagement surveys can score well while this signal is completely absent. The signal’s presence means the destination has landed. Its absence means it has not, regardless of what the dashboard reads.

When enough Jodys emerge across an organisation, the needle moves. Not because leadership pushed harder, communicated more cleverly, or solved one more urgent problem. But because ordinary people with real jobs decided, on their own initiative, that the destination was worth moving toward.

The practical implication is uncomfortable for leaders trained in comprehensive planning: resist the pressure to make the destination inclusive. A destination designed not to alienate anyone ends up directing no one. Choose one. Make it unambiguous. Then watch what Jody does on Monday morning.

Five Prompts for Deeper Reflection

Use these with any AI assistant (or as journaling prompts) to apply the ideas in this article to your own leadership context.

Prompt 1 — Diagnose your own Follower-Friendly Failure

“Here is how I currently try to motivate my team: [describe your approach]. Based on the distinction between problem-fixing and destination-setting, identify where my current approach might be producing Follower-Friendly Failure. What am I likely missing, and what would a clearer destination look like in my specific context?”

Prompt 2 — Test your destination for ambiguity

“Here is our current strategic vision or mission statement: [paste it]. Assess whether this constitutes a genuine, unambiguous destination that an ordinary employee could act toward on Monday morning — or whether it is a wish list, a values statement, or a problem-solving agenda in disguise. Then suggest what a sharper destination might say instead.”

Prompt 3 — Find your Jody

“Our organisation has articulated the following strategic direction: [describe it]. Help me identify what a ‘Jody Bloggs’ signal would look like in our context — that is, what specific, observable, novel behaviour by a non-senior employee would indicate that our destination has genuinely landed, rather than merely been communicated.”

Prompt 4 — Identify your destination-first followers

“The article describes a subset of followers who are loyal to a destination rather than to a leader’s personality or specific policies. Thinking about my own team or organisation, help me profile what this group might look like: how would I identify them, what do they need from a destination to engage, and how might I be inadvertently failing to reach them with my current communication?”

Prompt 5 — Rewrite your strategy communication through a Futures Literacy lens

“Here is how I typically communicate our strategy to staff: [paste an example — a town hall script, an all-staff email, a strategic summary]. Rewrite this using Futures Literacy principles: remove problem-solving language, eliminate wishlist elements, and replace them with a single unambiguous destination that an ordinary employee could picture and act toward. Show me the before and after side by side.”

P.S. Remember that registration is open for the Long-Term Strategy Conference 2026 – click here.