CHAPTERS
- 0:00 – 4:50
Why “strategy” is usually just planning (and why that fails)
Aakash opens by challenging why strategy feels hard, and Roger Martin argues most leaders confuse strategy with planning. Lists of initiatives and budget narratives create activity, but not advantage. Real strategy must create a compelling reason for customers to choose you over alternatives.
- •Strategy is not a comprehensive plan or initiative list
- •Many orgs produce “budgets with prose,” not strategy
- •A good strategy compels customers to take the desired action (buy/choose you)
- •Initiatives should be outputs of strategy, not the starting point
- 4:50 – 6:13
Roadmaps vs. strategy: the product manager’s trap
Aakash frames why product teams are especially prone to confusing execution with strategy: they’re trained to build roadmaps and ship features. Roger agrees that great PMs are often unrecognized strategists. The chapter sets up the need for clearer strategic inputs before tactical planning.
- •Product teams over-index on tactical roadmaps
- •Organizations often expect PMs to be a “silver bullet,” without naming strategy explicitly
- •Great PMs behave like strategists even if the company doesn’t label it that way
- •The right sequence is: strategic choices first, roadmap second
- 6:13 – 10:38
The “Playing to Win” five-question strategy framework
Roger lays out his core strategy model: five integrated choices that reinforce one another. Strategy begins with a winning aspiration and flows through where-to-play and how-to-win choices, supported by capabilities and management systems. Fit and reinforcement across the five is what makes the strategy compelling.
- •Five choices: winning aspiration, where to play, how to win, must-have capabilities, management systems
- •Winning often means competitors decide to win somewhere else (avoid a ‘bloody war’)
- •Where-to-play and how-to-win must be tightly matched
- •Capabilities and systems are required to sustain the chosen advantage
- 10:38 – 12:35
Sponsor break: WorkOS & Amplitude
Aakash shares sponsor messages about enterprise SaaS infrastructure and product analytics tooling. The segment emphasizes enterprise readiness (SAML/SCIM/RBAC) and product maturity assessment as ways to scale product strategy and execution.
- •WorkOS for enterprise features (SAML, SCIM) and authorization (Warrant/Zanzibar)
- •Positioning as a drop-in Auth0 alternative with a free tier
- •Amplitude’s digital experience maturity assessment for product teams
- •Tools framed as enablers to ship faster and align on what matters
- 12:35 – 14:38
What business school gets wrong about teaching strategy
Aakash challenges the value of traditional MBA strategy curricula. Roger argues business schools overemphasize academic tools—especially the resource-based view—while practitioners rarely use them. He contends these analytical frameworks don’t reliably produce strategists.
- •Business schools emphasize the resource-based view of the firm
- •Strategy courses often teach tools (game theory, five forces, blue ocean) rather than practice
- •Real-world usage of these theories is rare in consulting/practice
- •Tools don’t substitute for making integrated strategic choices
- 14:38 – 16:17
How to learn strategy: diagnose what companies actually do
Roger explains how he would teach strategy: use the five-question framework and repeated practice. The key discipline is to infer a company’s strategy from observed actions—not from glossy strategy documents. Students should map the current strategy into the framework and propose improvements.
- •Teach strategy as practice: repeated, structured exercises
- •Strategy is what you do, not what you say
- •Analyze a company’s current choices using the five boxes
- •Improve strategy by tightening fit across the choices
- 16:17 – 22:24
Case study: Anthropic—can it win in “general LLM” without traffic?
Roger analyzes Anthropic’s apparent where-to-play (general LLMs) and questions the clarity of its how-to-win against traffic-rich, deep-pocketed rivals. He argues horizontal general AI is hard to monetize without distribution advantages. He suggests narrowing the where-to-play to find a more plausible path to winning.
- •Competing in general LLMs pits Anthropic against entrenched distribution (Google, Apple, Amazon, X)
- •Traffic/data flywheels matter as a competitive advantage
- •A narrower where-to-play can increase odds of being ‘better’ (vs. trying to be biggest)
- •Vertical examples (e.g., legal AI) show how focus can create a durable win
- 22:24 – 26:57
Westlaw vs Google: why narrower plays can still be huge businesses
Roger uses Thomson Reuters’ Westlaw to illustrate how a focused where-to-play can beat a giant on outcomes customers value. Google search returns too many results; Westlaw returns the few that matter, saving expensive lawyer time. The story reinforces matching a specialized database and process to a specific customer job.
- •Westlaw’s advantage is precision and time savings for litigators
- •Differentiation comes from proprietary systems (taxonomy/numbering, headnotes)
- •A narrower field can sustain multi-billion, high-margin economics
- •The goal is a matched where-to-play and how-to-win, not maximum market breadth
- 26:57 – 30:20
Aakash’s Anthropic strategy: enterprise APIs, coding/writing, and trade-offs
Aakash proposes that Anthropic’s real where-to-play may be enterprise/API use cases rather than consumer chat. He cites revenue mix differences (Anthropic API-heavy vs OpenAI consumer-heavy) and points to coding/writing partnerships as data and distribution leverage. Roger validates this as a narrower, more defensible choice built on competitor trade-offs.
- •Anthropic revenue mix suggests enterprise/API focus vs consumer dominance by OpenAI
- •Potential wedge: enterprise-grade AI assistance and coding/writing via partners (e.g., Cursor)
- •Differentiators discussed: constitutional AI, long context windows, safer/slower rollouts
- •Defensibility via trade-offs competitors may ‘won’t’ make (release speed vs enterprise reliability)
- 30:20 – 35:23
Sponsor break: Linear (product planning + execution in one system)
Aakash describes how fragmented PM tooling creates “human API” work: syncing feedback, roadmaps, and execution across systems. Linear is positioned as a unified workspace to capture feedback, plan, coordinate teams, and monitor delivery. The segment highlights adoption by high-profile product teams.
- •Problem: too many disconnected tools for planning, tracking, and feedback
- •Linear pitched as a single place for ideas, execution, and progress tracking
- •Reduces overhead of keeping systems and stakeholders in sync
- •Social proof: used by teams at OpenAI, Vercel, Brex, Cash App
- 35:23 – 41:23
Planning cycles: initiative lists create comfort; strategy requires bets
Roger contrasts the comfort of plans (clear tasks and checklists) with the discomfort of strategy (resource commitments under uncertainty). Executing a bad strategy perfectly still fails if customers aren’t compelled. The right approach is to start with outcome-driven strategic choices, then derive initiatives.
- •Plans optimize activity; strategy optimizes outcomes and customer choice
- •A well-executed list can still produce no sales if the offering isn’t compelling
- •Strategy demands focus and trade-offs (what you won’t do)
- •Derive initiatives from the strategy to reduce conflict and improve prioritization
- 41:23 – 43:22
What to do when strategy is ‘above your pay grade’—and how to escalate well
Aakash asks how lower-level PMs can engage when they can’t change strategy directly. Roger argues you should still surface the strategic issue clearly, propose changes, and invite discussion—otherwise you may be stuck executing a losing plan. He emphasizes communicating with maturity: frame it as updated assumptions and prudent reconsideration, not blame.
- •Even if you can’t decide strategy, you can diagnose and escalate misalignment
- •Present concerns as assumptions changing over time, not as ‘leaders are idiots’
- •If leadership can’t engage thoughtfully, consider leaving rather than marching toward failure
- •Developing strategic voice early is key to becoming a leader
- 43:22 – 53:57
Southwest Airlines: a tightly integrated where-to-play/how-to-win system
Roger walks through Southwest’s foundational choices: point-to-point flights, single aircraft type, fast turns, secondary airports, and a low-friction boarding model. These choices reinforce each other to maximize time in the air, lowering costs and enabling frequent, cheap flights that compete with buses. Incumbents couldn’t copy without tearing up their entire model.
- •Core insight: planes make money in the air; design the system to minimize ground time
- •Choices: point-to-point, one aircraft type, no seat selection, no interlining, minimal catering
- •Where to play: short-haul, high-frequency, low-cost alternative to Greyhound
- •Copying would require incumbents to abandon hubs, fleets, channels, and service tiers—too costly
- 53:57 – 1:00:29
Strategy needs a theory of the future + ‘what would have to be true’ (Bayesian updates)
Roger argues strategy is a theory about the future, not a claim of certainty. The key discipline is articulating “what would have to be true” for your strategy to work, then monitoring those assumptions and updating as new data arrives. Aakash reframes annual planning as a structured Bayesian update to strategic beliefs.
- •Strategy is a bet based on a theory of how the future will unfold
- •Ask: ‘What would have to be true?’ about customers, channels, competitors, industry
- •Choose among alternative theories by evaluating which assumptions seem most likely
- •Continuously monitor assumptions and update strategy as evidence changes
- 1:00:29 – 1:11:16
Finding competitors’ ‘won’ts’: mixed motives as a source of defensibility (Olay, Tesla, Amazon, Dollar Shave Club)
Roger explains that durable advantage often comes from choices competitors won’t make—not can’t make—because of mixed motives and fear of harming their core business. He illustrates with Olay vs. prestige skincare channels, Tesla vs. ICE incumbents, and Amazon vs. Walmart’s reluctance to cannibalize stores. He also covers P&G vs. Dollar Shave Club to show how channel dependence can create a ‘won’t’ constraint.
- •Defensibility often comes from ‘won’t’ (trade-offs), not ‘can’t’ (ability)
- •Mixed motives: copying you would damage incumbents’ existing profit pools
- •Examples: Estee Lauder/Clinique won’t go mass; automakers resisted EVs; Walmart delayed online dominance
- •Lesson: avoid replicating incumbents’ where-to-play, or you inherit their mixed motives
- 1:11:16 – 1:20:18
Roger Martin’s work today: advisory model, writing flywheel, and monetization
Aakash closes by asking about Roger’s time allocation and business model post-dean career. Roger splits time between advising CEOs and writing, using widely distributed content as a lead generator rather than direct monetization. He describes a simple consulting structure based on day rates and lightweight advisory engagements.
- •Time split: roughly half advising CEOs, half writing
- •‘Practitioner Insights’ series as a large free/low-friction knowledge base
- •Writing monetizes indirectly by attracting high-value advisory work
- •Consulting offer: straightforward day rate, minimal proposals, flexible support for good clients
