The big bet paradox

Spoiler alert: it is not your strategy that is broken.

Picture the quarterly strategy meeting. The slides are crisp, the market opportunity is large, and everyone is nodding at the next big initiative. Eighteen months later you are in a post-mortem on another transformation that did not transform anything. If that sounds familiar, you are in good company. Research on major business transformations consistently puts the failure rate somewhere between 70 and 88 percent, depending on who is counting and how generous they are about "success". The interesting part is that it is rarely because the strategy was wrong. Most organizations are trying to execute tomorrow's strategy with yesterday's capabilities.

I have looked at a great many of these initiatives over the years, successful and otherwise, and the companies that land their big bets are not reliably the ones with the sharpest market insight or the deepest pockets. They are the ones that have quietly built three capabilities that turn uncertainty into an advantage. None of the three shows up on a strategy slide.

Learning at the speed of change.

Everyone talks about Steve Jobs's intuition, and less about what Apple has done since. Its services business grew over 12 percent in 2024 to close to 100 billion dollars, and that did not happen because a second visionary appeared. Jobs famously did not ask customers what they wanted; today's Apple has built something more durable, a systematic way of understanding how people actually live with technology, and made it a competency any engineer can draw on. That is learning velocity engineered into the organization rather than resident in one person.

Microsoft under Satya Nadella shows you do not need to be naturally quick at learning, only systematic about it. Nadella did not change everything at once. The growth mindset was not a slogan but a working rule for how teams approached decisions, and knowledge started to move between teams that had barely spoken. The company that had been stuck in Windows thinking ended up leading in cloud. The practical lessons are plain enough: make environmental scanning part of everyone's job rather than the strategy team's; build formal ways for teams to share what they learn; track what you learned this quarter alongside what you delivered.

Capabilities that build themselves.

Amazon Web Services was not born in a strategy session about cloud computing. It emerged because Amazon had to solve its own scaling problems, and solved them in a particular way: documented, turned into reusable patterns, built as if someone else might need them one day. Eventually someone else did, and the business now generates tens of billions a year. The lesson is not about cloud. It is about solving today's problem in a way that leaves a capability behind, so that the next problem is easier and the one after that is a product.

Most organizations sit somewhere on a spectrum here. At one end, every new challenge feels like starting from scratch, knowledge walks out of the door with the people who had it, and heroes carry the projects. At the other, building a new capability has become routine: every solution leaves a reusable pattern behind, there is a living library of them, and innovation compounds. The way to move along the spectrum is unglamorous. Document as you build. After every project, ask what you learned that could be systematized. Make reuse easier than reinvention. Measure how long it takes to get from idea to execution, and set out to shorten it.

Change that does not break everything.

The third capability is the one that makes the other two matter. You can learn faster than your industry and build capabilities at speed, and still produce nothing but expensive pilots if the organization cannot actually change. Microsoft's market value tripled not because it launched revolutionary products but because it rewrote how change happened inside the company. Every leader went through the growth-mindset work, and none delegated it, which for a senior team is the harder half. Promotion started to depend on learning as well as performance. The partner network was used to reinforce the shift until it felt inevitable rather than imposed. No single change was brilliant; the sequence was.

Change readiness is built the same way. Start with small, low-risk changes and win consistently, because success builds psychological safety faster than any program. Keep the CEO's vision, operational execution and cultural change moving together, since any one of them on its own fails. Use external pressure, the market, the competitors, the customers, so that change feels like adaptation rather than disruption. And reward teams that try new approaches even when they do not work, because that is the risk tolerance transformation runs on.

The startup reality check.

Conventional wisdom says startups have this solved. They are fast, they are agile, they iterate, and they will tell you so. The record says otherwise: a large share of startups fail by running out of cash despite all the iteration, and a good number collapse from scaling before they are ready. The survivors are not just fast. They learn in a focused way, build capabilities that can scale, and change direction without losing momentum. For established companies the lesson is uncomfortable. Speed without systems is just expensive chaos.

Before the next big bet.

Run the initiative through three tests. The learning test: how quickly do we notice when the environment changes, can we make sense of it across teams, and do insights change how we operate or just produce reports? The capability test: what is our record of turning ideas into execution, how fast can we move resources when priorities shift, and can we build new skills while running the current business? The change test: is the leadership genuinely aligned, does the culture treat change as opportunity or threat, and have we come through a major change before?

If the answers are mostly no, do not abandon the bet. Choose your battles more carefully, and favor initiatives that use the strengths you have over ones that need wholesale transformation. And if you can only invest in one of the three capabilities, invest in change readiness. It is the one that unlocks the others.

What this changes is the questions you ask at the start:

• Not "is this a good market opportunity?" but "are we the kind of organization that can execute it?"
• Not "what is our competitive advantage?" but "what is our capability advantage?"
• Not "how big is the prize?" but "how ready are we for the change it requires?"

The choice is not whether to place big bets; standing still is the riskiest strategy of all. The choice is whether to build the organization first, or keep hoping that a better strategy will beat weak execution. The organizations that will matter in the next decade are not necessarily the ones with the best strategy today. They are the ones building the operating system to execute whatever strategy the future asks of them, and since these capabilities compound, the sooner you start, the further ahead you are.