42:42
product strategy
Dan Olsen argues that good product strategy is rare not because it's impossible but because teams either never prioritize thinking beyond the current sprint or lack a usable framework, and that strategy is fundamentally about deciding what to say no to; his method is to ground strategy in customer problem space first, then use the Kano model (must-have, performance, delighter) inside a "product strategy grid" scored against broadly-defined competitors to find the one performance dimension a team can own plus a unique delighter — a pattern he reverse-engineers from Instagram's and Uber's early strategies.
Good product strategy is rare because teams either stay stuck in tactical, sprint-by-sprint execution or want to think strategically but lack a framework for doing so.
Strategy is defined as a plan for how you will win, requiring decisions about how to reach goals (not just stating the goals), balancing customer-centricity with competitive awareness, choosing an appropriate time horizon, and above all deciding what to say no to.
Teams must define the problem space (customer need/benefit, via an Agile-style user story) before moving into solution space (specific feature/design); over 80% of product failures are attributed to skipping this and jumping straight to a solution.
The Kano model sorts customer needs into three categories — must-have (expected, doesn't add satisfaction but its absence causes dissatisfaction), performance (more is proportionally better, and where most competition happens), and delighter (unexpected, adds outsized satisfaction) — and needs migrate over time: delighters become performance features, which become must-haves.
The Product Strategy Grid operationalizes this: rows are categorized customer needs for a chosen time frame, columns are your product plus competitors (defined broadly, Porter's-style, to include substitutes like Excel or manual workarounds), and cells are scored low/medium/high to reveal which single performance benefit is realistically ownable.
The output of the grid exercise is a small set of unique differentiators — usually one performance benefit to win plus a unique delighter — which then feeds into the Lean Product Process (brainstorm solutions, spec an MVP, prototype, validate with customers, then build).
Instagram (2010) beat a crowded photo-sharing category via a quantifiable performance edge (faster photo posting) plus a then-unique delighter (filters), while matching must-haves (basic photo sharing); its tagline packed the whole grid into a few words.
Uber's original Series A deck (as UberCab) positioned it as faster and cheaper than a limo but nicer and safer than a taxi — outperforming on three dimensions at once, a rarity Dan attributes to disrupting a monopolistic, customer-value-decoupled taxi/limo industry via mobile and GPS technology.
PM Motto (with great responsibility comes power) — Dan's inversion of Spider-Man's line, capturing that PMs own product outcomes and strategy without having direct reports. Apply: Use influence and persuasion (bring the donuts for the engineers) rather than authority to get cross-functional buy-in on strategy.
Dan's five-part definition of product strategy — Strategy is a plan for how you will win, requiring decisions on how to reach goals (not just stating them), balancing customer-centricity with competitive awareness, an appropriate time horizon, and clarity on what you say no to. Apply: Check any strategy draft against all five criteria before treating it as finished, especially whether it names what will be declined.
Strategy means saying no (Steve Jobs focus principle) — Citing Jobs, Dan frames focus and strategy as the discipline of saying no to the many good ideas you aren't pursuing, not just saying yes to the one you are. Apply: Treat a strategy that names no explicit rejections as a signal it isn't yet a real strategy.
Google's 70/20/10 resource allocation model — A resource split where 70% of investment targets the core business with 12-month ROI, 20% targets seeds for revenue beyond 12 months, and 10% funds moonshot experimentation. Apply: Map planned initiatives into the three buckets to see if an organization is over-indexed on short-term work versus Dan's observed common alternative of 95/5 or 99/1.
Time-frame clarification — Explicitly picking a strategy's time horizon (1 vs. 3 vs. 5 years) before running a planning exercise, since different horizons yield very different answers. Apply: State the intended time frame at the start of any strategy session so participants aren't mixing quarterly and multi-year thinking.
Runway reality-check exercise (Airbnb workshop) — A workshop where participants role-play as Airbnb's founders, draft a grandiose strategy, then check it against a typical 12-18 month runway for a 4-person startup. Apply: After drafting an ambitious strategy, test it against real resource and time constraints to confirm it's achievable in the stated period.
Problem space vs. solution space — Two sides of one coin: problem space is the customer problem/need/benefit a product should address; solution space is the specific implementation or design that meets it. Apply: Articulate the customer problem a feature serves before discussing the feature itself, moving from problem space to solution space in that order.
Agile user story template — The As a [type of customer], I want to [do X] so I can [enjoy benefit Y] template, used as the clearest articulation of problem space. Apply: Write candidate needs in this template to force explicit statement of customer and benefit before any solution is proposed.
Benefit ladder — A two-level hierarchy of customer benefits (e.g., TurboTax's top-level improve confidence, save time, save money, each with child benefits) mapping a product's full problem space. Apply: Sort every candidate feature idea into an existing ladder rung, treating a genuinely new top-level ladder as a rare, notable strategic addition.
Solution pollution (and its response technique) — Dan's term for proposing a specific feature/solution without first grounding it in a customer problem. Apply: Respond with I hear you saying we should build feature X, can you help me understand how that benefits the customer? to surface the underlying problem before debating the solution.
Kano model — A framework (originated by Professor Kano in Japan) plotting how fully a product meets a need (X-axis, 0-100%) against resulting customer satisfaction/dissatisfaction (Y-axis), used to categorize needs. Apply: After defining needs in problem-space terms, sort each into performance, must-have, or delighter to decide where to invest competitively.
Performance benefit (Kano category) — A benefit where more fulfillment creates proportionally more value and can usually be quantified (e.g., % faster, % more relevant); most competition happens here. Apply: Identify which performance dimensions competitors are weak on and target being quantifiably best on at least one.
Must-have benefit (Kano category) — A benefit that doesn't increase satisfaction even at 100% fulfillment (e.g., secure transactions, HIPAA compliance) but causes increasing dissatisfaction if unmet. Apply: Meet must-haves at parity only, don't invest differentiation effort there, and don't mistake an MVP with only must-haves for something that creates customer value.
Delighter (Kano category) — A benefit whose absence causes no dissatisfaction but whose presence creates outsized positive satisfaction, e.g., early-car GPS or Instagram's 2010 filters. Apply: Pair one performance-benefit lead with a unique delighter, expecting the delighter to eventually get copied and migrate into a must-have.
Product Strategy Grid — Dan's tool: rows are categorized customer needs (must-have/performance/delighter) for a set time frame, columns are your product plus broadly-defined competitors, and cells score how well each meets each need. Apply: Populate the grid, find the performance row where competitors are weak or tied, and build strategy around owning that row plus a unique delighter.
Porter's alternatives/substitutes (broad competitor framing) — Defining competitor to include any current way customers meet the need, not just funded rivals, e.g., Excel, duct tape, or a CSV export. Apply: When listing grid columns, include informal or manual workarounds customers currently use alongside direct competing products.
Unique differentiators — The intended output of the grid exercise, typically one performance benefit a team can uniquely win plus any unique delighters. Apply: Explicitly decline to match a competitor's unbeatable strength and instead commit resources to the one dimension that's genuinely ownable.
Lean Product Process — Dan's book process for turning grid conclusions into product: brainstorm solution ideas for the chosen benefit, spec an MVP, prototype, and validate with customer feedback before building. Apply: Treat the grid-derived strategy as a hypothesis and test it with a prototype and real users before committing full engineering investment.
Product archaeologist method — Dan's technique of reverse-engineering a company's underlying, often never-explicit product strategy by mining artifacts like published Series A pitch decks. Apply: When a founder shares an old pitch deck, look for statements mapping onto must-have/performance/delighter categories rather than accepting the deck's own framing.
Dan-speak phrasing convention — A style rule where problem-space statements start with a verb (e.g., save time) while performance statements use comparative adjectives (faster, cheaper, nicer, safer), which can double as internal slogans. Apply: When rewriting a benefits slide, phrase needs as verb-led statements and competitive strengths as comparative adjectives to keep the two framings distinct.
Optimistic background-upload UX pattern — Instagram's technique of starting a photo upload in the background the instant the photo is taken, since ~95-99% of taken photos get posted, rather than waiting for the user to finish editing and tap Share. Apply: When most user actions eventually reach a wait-heavy end state, start the expensive operation optimistically at the earliest reliable signal and roll back only for rare cancellations.
Uniform square aspect-ratio design technique — Instagram's decision to crop all photos to a fixed square to avoid the inconsistent zoom/scaling caused by mixing portrait and landscape rectangles in a fixed-width feed. Apply: When a feed must display heterogeneous content consistently, normalize to a fixed shape at the feed level rather than solving it photo-by-photo.
Pivot via usage-driven repositioning — Instagram founders' method of honestly examining actual usage of their underperforming broader app (Bourbn/Burbn) to find what people actually used it for, then studying that narrower category for a differentiation angle. Apply: When a product isn't gaining traction, analyze real usage patterns rather than the original vision to find the sub-behavior with pull, then run the grid exercise against that narrower category's incumbents.
Needs evolve on a clock set by category competitiveness: Instagram's filters were a delighter in 2010 but would be a laughed-out-of-the-app-store must-have by 2024, illustrating that a delighter-based strategy has a shelf life and gets copied.
A common startup failure mode: falling behind schedule and shipping an MVP with just the must-haves creates no real customer value, and teams wrongly blame the MVP methodology itself rather than the missing performance/delighter component.
Instagram's famous upload-speed advantage wasn't a compression or engineering trick — its own UX team later revealed it came from starting the upload in the background the instant the photo was taken (since ~95-99% of taken photos get posted), a workflow-sequencing fix rather than a technical one.
Instagram's square crop was a feed-level fix, not a photo-level one — it existed to avoid inconsistent zoom/scaling when mixing portrait and landscape photos in a fixed-width feed, even though individual users (including Dan) were initially annoyed by having their photos cropped.
Uber's benefits slide is structured deliberately: two problem bullets about cabs, two about limos, then a single synthesizing comparative line (faster and cheaper than a limo, but nicer and safer than a taxi cab) — a reusable slide-writing pattern Dan says he only noticed after presenting it many times.
Performance benefits compound with usage frequency — Dan's Google-search example shows 2 seconds saved per query is only ~100 seconds/day for a 50-query power user but much less for a light user, meaning the same per-unit improvement is worth more to heavier users.
Dan calls himself a product archaeologist: successful companies almost never publish an explicit product-strategy grid, so deliberate strategy can only be inferred after the fact from artifacts like old pitch decks or later UX-team retrospectives — Airbnb was considered but excluded from his examples because its artifacts weren't as clear-cut.
Instagram's pivot from its earlier broader app Bourbn/Burbn came from founders honestly examining what people actually used the app for (photo sharing) rather than defending the original broader vision, then deliberately studying that narrower category to find a differentiation angle.
«The PM motto is... with great responsibility comes power.»
— 05:59
«People think focus means saying yes to the thing you're focusing on, but that's not what it means at all — it means saying no to the hundred other good ideas that there are... innovation is saying no to a thousand things... for me, strategy means saying no.»
— 09:09
«Problem space is basically a customer problem, need, or benefit that the product should address... solution space is a specific implementation or design to meet the need.»
— 12:24
«I hear you saying we should build feature X — can you help me understand how's that going to benefit the customer, how is that going to create value for the customer?»
— 15:38
«A must-have in the Kano model is actually... let's assume for a minute the product fully 100% meets the must-have need — it doesn't actually make the customer happy... the way it works is as you fail to meet the need it makes them increasingly unhappy — that's the Kano model definition of a true must-have.»
— 19:15
«You don't compete on must-haves — you just have to have them.»
— 20:39
«Yesterday's delighters become today's performance, become tomorrow's must-haves — and the pace with which that evolution happens just depends on the level of innovation and competition in your space.»
— 22:11
«Anytime you see a new product enter a crowded market, crowded category, and become number one and take off like a rocket ship, you must be able to figure out what was it in the product strategy grid — they have to have outperformed the other people somehow and/or have some unique delighters.»
— 28:59
«the second they take the photo start uploading that sucker in the background»
— 32:58
«faster and cheaper than a limo, but nicer and safer than a taxi cab»
— 39:49
«gosh you're lucky to outperform on one — these guys had three»
— 41:19
Reception
Audience reception is strongly positive, with viewers praising the video as clear and valuable, tempered by one detailed critique about repetitive examples.
The talk turns an abstract concept into a concrete, repeatable method (problem space to Kano categorization to product strategy grid to Lean Product Process), and grounds it in two detailed, well-sourced case studies (Instagram, Uber) — though as one viewer noted, those same two or three examples have anchored Dan Olsen's talks for roughly a decade.
42:42