AAcquired
← All frameworks
Innovation

Innovate Before the Inflection

Build strategic options before a crisis forces you to use them

Difficulty
Advanced
Time to result
~months to results
Steps
5
Confidence
97%

Innovate Before the Inflection treats research, adjacent products, and early customer contracts as strategic options rather than discretionary projects. A company uses strength in its current business to explore multiple future lines, places small but real bets, and learns which technologies can become complete businesses. These options must mature before the core encounters a crisis because building technology, capacity, customer trust, and organizational competence takes time. Intel could pivot toward processors because it had already invented and shipped CPUs, secured the IBM PC design win, and continued developing the x86 line while memory remained central. When the inflection arrived, management was reallocating toward an existing trajectory rather than inventing a rescue plan from scratch.

Origin

Intel's sustained R&D created a microprocessor business and IBM PC relationship before Japanese competition made the company's memory strategy untenable.

Core principles

  • 01A crisis is too late to begin creating credible alternatives
  • 02Continuous experimentation creates strategic options
  • 03Emerging product lines need real customers before they become rescue paths
  • 04Core-business success should finance exploration
  • 05Optionality matters even when the future use case is uncertain

How to run it

  1. 1

    Identify disruption vectors

    List the technological, competitive, and behavioral changes that could weaken the core business. Translate each into a possible future customer need.

    Pro tip Include developments that initially look too small to threaten the core.

    Watch out Do not assume the largest current market will remain strategically central.

  2. 2

    Create bounded options

    Fund several small initiatives related to those future needs. Give each one a clear technical or commercial learning objective.

    Pro tip Treat early projects as options with capped downside rather than miniature core businesses.

    Watch out Spreading resources without learning goals creates an innovation theatre portfolio.

  3. 3

    Ship to real customers

    Move promising technologies beyond research and into actual customer use. Seek contracts that reveal integration requirements and market pull.

    Pro tip A strategically important design win can matter more than early revenue.

    Watch out Laboratory progress alone does not prove that an option can become a business.

  4. 4

    Build supporting capability

    Develop the talent, production knowledge, supplier relationships, and sales competence each option requires. Protect the strongest initiatives from short-term core-business demands.

    Pro tip Track capability maturity separately from revenue.

    Watch out An under-resourced side project may not be ready when the company needs it.

  5. 5

    Scale when evidence converges

    When external change and internal traction align, concentrate resources on the best option. Stop treating it as an experiment and make it the strategy.

    Pro tip Define advance signals that would trigger the resource shift.

    Watch out Waiting for certainty can erase the lead created by early investment.

In the wild

Intel develops processors before the memory collapse

Intel created early processors, developed the x86 architecture, and won the IBM PC contract while it still identified primarily as a memory company. That work gave it products, customers, and technical momentum before the memory crisis peaked.

→ Intel had a credible business ready to receive resources when it abandoned memory.

A rideshare company develops delivery early

A mobility company tests food delivery years before passenger demand collapses. It builds courier supply, merchant relationships, dispatch software, and customer habits while rides remain healthy.

→ When travel demand falls, the company can scale an operating business rather than start an emergency experiment.

Common mistakes

Starting innovation during the crisis

New products require time to establish technology, distribution, and customer trust. Emergency incubation rarely produces a mature replacement quickly enough.

Funding research without market contact

Technical progress that never reaches customers provides limited evidence about business viability. Use real deployments to expose missing capabilities.

Killing every small business

Future options often look insignificant beside a healthy core. Evaluating them only by current revenue can eliminate the company's eventual escape route.

Is it for you?

Best for

It is best for established companies whose core market could be disrupted by technology, competition, or changing demand.

Not ideal for

It is not ideal for organizations without enough resources to support even a tightly bounded portfolio of experiments.

From the transcript

“Like the time to innovate is not when you find yourself in a strategic inflection point.”

David Rosenthal · 1:01:30

“It is well before then.”

David Rosenthal · 1:02:00

“Like you constantly should be looking for new product lines, looking for diversification.”

David Rosenthal · 1:02:00

From the episode

Adapting Episode 3: Intel

→