product strategy
Product strategy is not a roadmap, vision, or business strategy but the discipline of making explicit, evidence-backed choices about which critical problems to solve right now — and most organizations' chronic 'prioritization problems' are actually symptoms of never having built this discipline in the first place.
Product strategy is the act of making explicit choices about which problems to solve now, not a prioritized list handed down from leadership.
Roadmap, business strategy, product strategy, and product vision are four distinct things companies routinely conflate; most companies mistake a roadmap or recycled OKR slide for a strategy.
Product vision ('the mountaintop') exists to align teams in the same direction over the long term; product strategy exists to prioritize and sequence problems in service of both the vision and current business objectives.
A real strategy must state what NOT to do; strategies that only assert belief without data and reasoning are 'wishful thinking.'
Most so-called prioritization problems are actually lack-of-focus problems — if a real strategy exists, prioritization becomes implicit.
Good strategy has three ingredients: focus (explicit do/don't-do choices), transparency (the data and reasoning behind them), and placing a bet (committing without guaranteeing the outcome).
The best-practice artifact for a strategy is a written narrative (Amazon's six-pager), which lays out the data and logic for why a problem is the most important one to solve now.
Introducing focus to a resistant leadership team works best as a low-risk, reversible 'test,' with leadership itself choosing the focus area to reduce political resistance — collapsing to one 'leap of faith' instead of two.
Orgs should cap concurrent strategic bets at roughly two or three; parallel work doesn't run at the same speed as sequential work ('doing two in 2x'), and construction-style dependencies mean later-stage work can't be started before earlier phases finish.
Keep-the-lights-on work and tech debt are separate, always-funded categories, distinct from — and not sacrificed to — the chosen strategic focus.
Product leaders earn the right to define problems (vs. take stakeholder-dictated solutions) by first delivering on existing stakeholder requests reframed as outcomes; teams build trust doing solution discovery before earning latitude for independent problem discovery.
Strategy is a continuous feedback loop: problems teams surface during solution discovery become inputs to the next quarter's strategy, alongside executive input — it should be updated at least quarterly, and in practice constantly.
Annual planning (AOP) is largely a symptom of missing strategy, funding whole projects upfront ('a dog and pony show') at far higher cost than a VC-style model that funds discovery first and scales funding based on results.
For high-stakes bets, assigning the same critical problem to more than one team in parallel is a hedge against execution risk.
AI belongs in a strategy only after asking two separate questions: should this problem leverage AI at all, and is it technically ready — plus defining the guardrails for any probabilistic solution.
For crafting strategy itself, the primary tool is the brain — AI tools can sharpen strategic thinking, but can just as easily substitute for it.
Strategy failure is most often not a bad strategy but a good strategy undone by execution that proved too hard to pull off.
Leaders sometimes outsource strategy to consulting firms as a political hedge — credit if it works, blame shifted if it fails — rather than building internal strategic capability.
The video's central diagnostic move is reframing symptoms as root causes: a 'prioritization problem' is reframed as a 'focus problem,' which is itself reframed as a 'missing strategy problem' — three layers of the same underlying gap.
The coaching techniques described (the reversible 'test' framing, letting leadership pick its own focus area, the 'one bet' forcing question, the strategy-penetration diagnostic of offering someone alternate work) are all political workarounds for the same problem: leaders resist explicit tradeoffs, so the path to a real strategy runs through managing that resistance rather than through better analysis alone.
The 'peanut butter strategy' (spreading resources thin) and 'outsourcing strategy' (hiring consultants for political cover) are named as the two default failure modes leaders fall into specifically to avoid making a real, attributable tradeoff.
The VC-seed-funding-vs.-annual-planning contrast and the multi-team-parallel-assignment technique both point to the same underlying principle: fund/staff strategic bets incrementally and hedge on uncertainty, rather than committing full resources on a single unverified path.
The AI-fit framework mirrors the general strategy discipline itself — just as a strategy must justify why a problem is worth solving before committing resources, AI's inclusion in that strategy must independently justify both its relevance and its readiness before being written in.
«fundamentally the product strategy is about making those choices.»
— 03:07
«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
«We don't have a prioritization problem. We have a lack of focus problem.»
— 21:50
«Just because you can do one in x amount of time doesn't mean you can do two in 2x.»
— 27:10
«My favorite way is in a six-pager in a written narrative. My favorite artifact.»
— 41:19
«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
«Visions don't change, but strategies change a lot.»
— 53:30
For product leaders, VPs of Product, and coaches trying to diagnose why their org's 'prioritization problem' never resolves, and who need a vocabulary and set of political tactics for introducing real strategic focus.