57:33
product strategy
Product strategy is the discipline of making explicit, evidence-backed choices about which critical problems to solve right now — distinct from a roadmap (a list of features/projects), a business strategy (market/go-to-market choices), or a product vision (long-term direction) — and it exists to make both the vision and the business strategy real, while the absence of it is the actual root cause of most companies' chronic 'prioritization problems.'
Product strategy is fundamentally about making choices, not something handed down as a prioritized roadmap.
Most companies don't have a product strategy at all; they mistake a roadmap, a feature list, or a recycled OKR slide for one.
"Strategy" is an overloaded word — business strategy, go-to-market strategy, and product strategy are distinct but tightly related concepts.
In good companies both business strategy and product strategy exist together; business strategy shapes product strategy, and product strategy can also reshape business strategy over time.
Product vision is 'the mountaintop' — the problems the company wants to solve over a longer timeframe; product strategy is how you get there while also meeting current objectives.
The two inputs to product strategy are the product vision and the company's objectives, which themselves reflect business strategy.
Product vision's distinct job is alignment ('rowing in the same direction'), not prioritization; small companies often don't need a vision but do need a strategy.
A real strategy must make hard choices about what NOT to do; strategies that only assert belief without data and reasoning are 'wishful thinking.'
Amazon's six-page written narrative is cited as the best-practice artifact for laying out the data and logic behind a strategic choice.
Many so-called 'prioritization problems' are actually 'lack of focus' problems; if a real strategy exists, prioritization becomes implicit.
Introducing real focus to leadership is best framed as a reversible test, and the specific focus area should ideally be chosen by leadership itself to reduce political resistance.
Focus does not mean neglecting keep-the-lights-on work or tech debt — those are separate, always-funded categories.
Product leaders typically earn the right to define problems (rather than have stakeholders dictate solutions) by first delivering on stakeholders' existing requests reframed as outcomes.
Teams should focus on solution discovery before earning trust to do independent problem discovery; new problems teams surface become inputs to the next quarter's strategy, forming a continuous strategy loop.
Annual planning (AOP) is largely a symptom of missing strategy — a 'dog and pony show' that funds whole projects upfront rather than funding discovery first.
The most common reason a strategy fails is not a bad strategy but a good strategy paired with execution that proved too difficult to crack.
Product strategy has two goals: moving closer to the vision and keeping the business financially viable, sequenced around what can be monetized now.
Whether to build AI into a strategy is usually 'yes,' but the harder question is whether a specific problem is technically ready, and a good strategy should address the role and guardrails of probabilistic solutions.
For crafting strategy itself, 'the primary tool is the brain'; AI tools can sharpen thinking or become a substitute for it.
Product strategy is treated as more sensitive information inside a company than its code.
Visions rarely change, but strategies change often (e.g., under forcing functions like COVID); strategy should be a living document updated at least quarterly.
Good strategy is synthesized as three elements: focus (what to do and not do), transparency (the data/reasoning behind the choices), and placing a bet (choosing without guaranteeing the outcome).
Product model (vs. project/roadmap model) — An organizational approach where teams are given hard problems to solve in ways customers love that also work for the business, rather than a list of features/projects to execute. Apply: Hand teams a problem and outcome to own instead of a pre-specified feature to build.
Roadmap (feature/project list) — A prioritized list of features and projects handed down to product teams, which most companies mistake for a product strategy. Apply: Recognize that a features-and-projects list alone does not resolve prioritization conflicts and is not a substitute for a strategy.
Business strategy / go-to-market strategy / product strategy triad — Three distinct but interrelated forms of strategy: business strategy sets market/monetization choices, go-to-market strategy governs how products reach customers, and product strategy decides which problems to solve. Apply: When defining product strategy, explicitly trace how it serves the company's business strategy and how it will, in turn, shape go-to-market strategy.
Placing bets (strategy-as-bets framing) — The idea that a product strategy is an argument for a series of bets rather than a guarantee of outcomes. Apply: Present strategic choices to stakeholders as bets backed by reasoning, not as promised results, to avoid overselling.
OKRs/KPIs as business-strategy mechanism — The measurable objectives (e.g., 'a third of revenue from Europe by year end') through which business strategy shows up as targets for the product org. Apply: Translate a business-strategy shift into a concrete OKR/KPI, then have the product org determine via discovery what product changes are needed to hit it.
Discovery — The product-discovery process used to determine what's actually different when entering a new market or context (e.g., China or Africa vs. domestic). Apply: Before committing to a business-strategy-driven target, run discovery to find out how difficult the required product changes will be.
"Rowing in the same direction" (product vision's alignment role) — The specific function of a product vision — inspiring and aligning many teams toward one direction, distinct from strategy's prioritization role. Apply: As a company scales past roughly ten product teams, introduce a product vision to keep teams aligned, separate from the quarterly strategy that assigns problems.
Amazon-style six-page written narrative — A written-narrative format (popularized by Amazon) that lays out data and reasoning for why a problem is the most important one to solve right now, and Cagan's favorite output artifact for a product strategy. Apply: Write a six-page narrative documenting the evidence and logic behind prioritization choices so stakeholders can transparently evaluate and challenge the reasoning.
"If you have a strategy, prioritization is implicit" — The claim that most 'prioritization problems' are actually symptoms of a missing strategy, since a real strategy already makes the choices explicit. Apply: When a team complains about a prioritization backlog, diagnose whether the real gap is a missing strategy rather than a scheduling failure.
Reversible "test" framing for introducing focus — A coaching technique of pitching a shift to real focus to leadership as a low-risk, reversible experiment rather than a permanent commitment. Apply: Propose trying one focused approach for a limited period, explicitly noting the org can revert to its old way of working if it doesn't help.
Letting leadership pick their own focus area — A political technique where the coach/product leader has the CEO or leadership team choose the single focus area themselves, rather than having the strategist dictate it, reducing the leaps of faith required. Apply: Instead of insisting your prioritization is correct, ask the CEO/GM to select the focus area — this removes one point of resistance.
"One bet" forcing question — A coaching question that forces leadership to name a single top priority: 'if you had to make one bet to deliver to your investors this year, which one is it?'. Apply: Use this question in leadership sessions to surface the genuinely most important initiative when a list has too many co-equal priorities.
2–3 concurrent focus areas (WIP cap) — A recommended limit on the number of strategic initiatives an org pursues simultaneously, since doing two things in parallel doesn't run at the same speed as doing one twice. Apply: Cap the number of concurrent strategic bets at about two or three rather than ten or seventy.
Work-in-progress limits (construction-site analogy) — The idea, illustrated via building a house, that you must complete foundation-then-walls-then-roof in order and can't crowd the site with materials for later, uncertain phases. Apply: Sequence strategic work logically and resist requests to start later-stage work before earlier dependencies are done.
Separating focus work from keep-the-lights-on work and tech debt — A categorization that keeps operational maintenance and technical debt as distinct, always-funded buckets separate from the team's chosen strategic focus. Apply: Track the percentage of team time spent on keep-the-lights-on work and continue funding it regardless of which strategic bets are chosen.
Strategy-penetration diagnostic test — A personal test where you offer someone alternate work and see whether they escalate to their manager for 'prioritization' rather than explaining why their current work matters. Apply: Use this test with individual contributors to check whether the strategy's 'why' has actually propagated to the team level.
"Peanut butter strategy" — A pejorative term for spreading resources thinly across too many initiatives instead of making real tradeoffs. Apply: Flag this pattern when leadership tries to fund many initiatives at once instead of committing to a small number of bets.
Outsourcing strategy (political failure mode) — A pattern where leaders hire outside firms to produce strategy so they can claim credit if it works and shift blame if it fails, rather than building internal strategic capability. Apply: Recognize reliance on outsourced strategy as a sign the organization hasn't built internal strategic muscle, and work to shift ownership to the product leader.
Outcome-based roadmap reframing — A technique for converting stakeholders' feature-request roadmaps into outcome/problem statements, first triaging whether a request is keep-the-lights-on or needs a defined problem to solve. Apply: For each stakeholder request, ask whether it's operational upkeep or a real opportunity; if the latter, reframe it as the problem/outcome to solve rather than the specific feature requested.
Problem discovery vs. solution discovery — A distinction between identifying which problems are worth solving (problem discovery) and figuring out how to solve a given problem (solution discovery), both skills empowered teams have. Apply: Have teams focus on solution discovery first to build stakeholder trust before earning the latitude to also do independent problem discovery.
Continuous strategy feedback loop — A cycle where problems teams surface during solution discovery are brought to the product leader and become inputs to the next quarter's strategy, alongside executive input. Apply: Have teams report newly discovered problems upward rather than act on them unilaterally, feeding them into the next strategy cycle.
VC seed-funding model vs. corporate annual planning ("project model") — A contrast between venture capital, which funds discovery first and only funds further based on results, and corporate annual planning (the 'project model'), which funds whole projects upfront based on pitched revenue/ease claims. Apply: Push annual planning toward funding discovery phases before committing full project budgets, rather than funding a 'dog and pony show' of upfront project pitches.
Two required outputs of a product strategy — A product strategy's output consists of (1) the prioritized problems to solve this quarter/year, and (2) the 'why' — the data, argument, and interdependencies behind those choices. Apply: When writing a strategy document, always pair the list of chosen problems with the underlying evidence and reasoning, not the problems alone.
Multi-team parallel assignment for critical bets — A technique of assigning an important, high-stakes problem to more than one team simultaneously so different skill sets are applied and at least one team is likely to succeed. Apply: For the highest-risk strategic problems, deliberately duplicate effort across teams rather than betting the outcome on a single team's execution.
Two-goal framework for product strategy — The claim that product strategy must simultaneously move the company toward its vision and keep the business financially viable, sequencing which problems to tackle based on what can be monetized now. Apply: When choosing which problems to prioritize, favor ones that both advance the long-term vision and generate near-term revenue/viability.
AI-fit evaluation for strategy — A two-part framework for deciding whether AI belongs in a product strategy: (1) should this problem leverage AI at all, and (2) is the specific problem technically ready for AI or does it need more foundation-model progress. Apply: For each candidate problem, explicitly assess AI leverage and technical readiness before committing it to the strategy, and define the role/guardrails for any probabilistic solution.
AI tools: clarity aid vs. substitute for thinking — A dichotomy noting that AI tools can either sharpen a team's strategic thinking or replace it entirely, both of which are possible outcomes of using them. Apply: Use AI to refine and pressure-test a strategy you've already reasoned through, rather than asking it to generate the strategy outright.
Focus + Transparency + Placing a bet (recap framework) — A three-part synthesis of what makes a strategy good: focus (explicit choices of what to do and not do), transparency (sharing the insights/data behind the choices), and placing a bet (committing without guaranteeing the outcome). Apply: Audit any strategy document against these three elements to check whether it's a real strategy or just a relabeled list.
Quarterly living-strategy cadence — The principle that a product strategy should be updated at least quarterly, and in practice continuously, as each quarter's bet results inform the next. Apply: Revisit and revise the strategy document every quarter using the outcomes of the prior quarter's bets rather than treating it as a fixed annual artifact.
A prioritization crisis is framed as diagnostic of a missing strategy rather than a scheduling problem: 'if you have a strategy, prioritization is implicit.'
The safest political move to introduce focus is letting the CEO/leadership pick the one focus area themselves rather than have the strategist dictate it, cutting the number of 'leaps of faith' needed from two to one.
The 'peanut butter strategy' — spreading resources thin across many initiatives — is named as the default failure pattern leaders fall into when avoiding hard tradeoffs.
A simple diagnostic for whether strategy has actually propagated down: offer someone alternate work and see if they escalate to their manager for 'prioritization' instead of explaining why their current work matters.
Leaders often outsource strategy to consulting firms as a political hedge — claiming credit if it works, blaming the outside firm if it fails.
Corporate annual planning is contrasted with venture funding: VCs fund discovery (seed rounds) first and only fund further based on results, while corporate planning funds whole projects upfront at what Cagan estimates is 'literally hundred times the price.'
Assigning a single critical problem to multiple teams in parallel, leveraging different skill sets, is used as a hedge against execution risk on high-stakes bets.
Scale is reframed as a focus problem rather than a resource problem: a 300,000-employee company asking for $50M more budget is met with 'what if you focused,' and small four-engineer teams are said to 'run circles around' 200-person teams.
Product strategy informing business strategy is illustrated by Datasite divesting underperforming business units to fund the product line that the strategy had proven out.
«Many companies may claim they have one, but more often than not, what they think is product strategy is really just a road map, a list of futures, or a recycled slide of last year's OK ARBs.»
— 00:17
«fundamentally the product strategy is about making those choices.»
— 03:07
«critical problems that will do two things. We'll take you towards your vision number one, and number two, pay the bills along the way.»
— 04:53
«The product strategy is how we make the product vision true and how we make the business strategy true.»
— 12:21
«How do you make sure everybody's rowing in the same direction? That's product vision.»
— 13:52
«a lot of product strategies are just wishful thinking. They're just wishful thinking. There is no real analysis about how and why that's going to happen.»
— 16:56
«Every leader in the company thinks they know what's important. And none of them are wrong.»
— 18:26
«We don't have a prioritization problem. We have a lack of focus problem.»
— 21:50
«It's a lot better to be uncomfortable on the thing that you believe is genuinely the most important.»
— 25:57
«Just because you can do one in x amount of time doesn't mean you can do two in 2x.»
— 27:10
«if it works well, I'm the hero. If it fails, you can blame the company that created it.»
— 30:23
«That does not — that's not a good look. That is never a good look.»
— 34:24
«Their primary job is to solve problems and the product leader's primary job is to identify those problems to solve.»
— 35:56
«You'd think by now the world would know.»
— 39:44
«My favorite way is in a six-pager in a written narrative. My favorite artifact.»
— 41:19
«You can have a beautiful logical well informed product strategy that you don't execute on.»
— 46:01
«For something like product strategy, the primary tool is the brain. That's the primary tool because product strategy is all about thinking, thinking clearly.»
— 50:43
«Can tools help bring clarity to thought? Yes. Can tools also be a substitute for thinking? Unfortunately, yes.»
— 51:01
«Even their code I think is less valuable to them than their strategy.»
— 52:26
«Visions don't change, but strategies change a lot.»
— 53:30
«I believe that a product strategy is a living thing. At a minimum, it should be updated quarterly. In reality, I think it's living. It's just constantly updating as you learn.»
— 53:50
«you're a bank like why is a request from a regulator always a panic like you haven't strategically understood that to be a bank you need to respond to regulatory requests and changes in compliance»
— 55:16
Reception
The audience response is overwhelmingly positive, mixing a few substantive compliments about clear, practical insights with a large volume of short, generic praise and emoji reactions.
The episode presents a coherent, coaching-derived map of product strategy — grounded in Cagan's SVPG/'Empowered' framework and Amazon's narrative-writing practice — offered as established best practice via anecdote and analogy rather than tested against competing definitions of strategy.
57:33