New-Market Capability Test
If it's exactly like what you already do, you'd already be great at it -- so ask what genuinely new capability the new market requires.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- —
A decision framework Ballmer uses to explain Microsoft's mobile and search failures and Azure's success: before extending an existing franchise into a new market, a company must consciously ask whether the new market is truly a line extension of current capability or a fundamentally different game requiring new capability, new talent, and sometimes a new business model. The trap is defaulting to your existing playbook out of comfort, fear of losing 'permission to exist,' or overconfidence, rather than honestly diagnosing what new muscle the opportunity demands.
Origin
Extracted from Acquired
Core principles
- 01Consciously and explicitly evaluate whether a new market resembles your existing business or not
- 02If a market is genuinely new, you must build or acquire genuinely new capability, not repurpose old strengths
- 03Look for existence proofs -- which business models already work in this market, and do you have either one?
- 04Don't let 'permission to exist' thinking (I only deserve to be here because of my legacy franchise) drive product decisions
- 05Going in halfway with the old playbook is often worse than either committing fully with new capability or not entering at all
How to run it
- 1
Name the new market's proven business models
Identify which monetization/product models already work in the new space (e.g., hardware + subsidized profit, or ad-funded free distribution in mobile).
- 2
Check if you already have either model
Honestly assess whether your existing capabilities map to any proven model, or whether you have neither.
- 3
Diagnose what's genuinely new
List the specific capabilities, talent, and UI/API choices that must be built from scratch rather than inherited.
- 4
Decide: build, buy, or don't enter
Determine whether you can build the missing capability internally, acquire it, or should not enter the market at all.
- 5
Fully commit, don't half-commit
If you decide to enter, go all the way with new capability rather than retrofitting your existing product's look and feel to save time.
In the wild
Microsoft tried to keep the familiar Windows user interface and started on Intel processors for Windows Mobile, prioritizing consistency with its existing franchise over what phone users and the ARM ecosystem actually needed.
→ Microsoft missed the two models that worked -- Apple's integrated hardware/profit model and Android's ad-monetized free model -- and never gained real mobile share.
Microsoft entered search five years after Google with no existing talent base in the space, pulling engineers from other divisions before eventually recruiting outside expertise like Qi Lu.
→ Better focus and dedicated new capability (rather than spreading across verticals) eventually helped Bing gain traction.
Ballmer pulled Dave Cutler and Amitabh Srivastava out of their existing roles into a standalone incubation team explicitly separate from the Server & Tools organization to build a genuinely new cloud platform.
→ Azure eventually became one of Microsoft's two core enterprise/cloud tricks.
Common mistakes
Windows Everywhere overreach
Microsoft tried to extend Windows into phones, cars, and media centers out of a mix of fear (losing 'permission to exist') and overconfidence, without building genuinely new capability for each context.
Spreading new-market bets too thin
Rather than committing fully to one new capability build, Microsoft simultaneously chased portals, verticals, and search, none of which got the focused investment needed to win.
Is it for you?
Best for
Executives at established companies deciding whether and how to enter an adjacent but structurally different market.
Not ideal for
Fast-moving startups without an existing franchise to protect or extend.
From the transcript
“Number one, you have to be focusing consciously on the issue.”
“just look two models worked in phone. Build the hardware, capture the profit, have a back-end monetization system that even let you pay the phone…”
From the episode
The Steve Ballmer Interview