The Problem Decomposition Discipline
Separate tangled strategic problems into distinct, solvable components
The Problem Decomposition Discipline addresses Horowitz's observation that bad product managers combine all problems into one while good product managers decompose problems. When facing a competitive challenge, bad PMs conflate delivering customer value, matching competitive features, pricing strategy, and achieving market ubiquity into a single amorphous problem. This makes the challenge feel overwhelming and impossible. Good PMs separate these into distinct problems, each with its own analysis and solution. Decomposition reveals that not all sub-problems are equally important, that some are easier to solve than others, and that addressing them in the right sequence can create cascading advantages. The discipline applies beyond product management to any complex strategic situation where multiple interrelated challenges create paralysis.
- Combined problems feel impossible; decomposed problems become individually addressable
- Different problem components require different expertise, timelines, and strategies
- Decomposition reveals which sub-problems are most critical and which can be deprioritized
- The sequence in which you address decomposed problems matters—some solutions enable others
- Name the Combined Problem ExplicitlyWrite down the overwhelming challenge as your team currently experiences it. This is usually a vague, emotionally charged statement like 'the competitor is killing us' or 'we are losing market share.' By writing it down, you create an artifact that can be examined and decomposed rather than an ambient anxiety that resists analysis. The act of naming the problem is the first step toward controlling it.Pro tipIf your problem statement contains the word 'and,' it is almost certainly a combined problem that can be decomposed.
- Identify the Distinct Sub-ProblemsBreak the combined problem into its constituent challenges. Horowitz identifies four common product strategy dimensions: delivering superior value, matching competitive features, pricing strategy, and market ubiquity. Your specific decomposition will vary, but the pattern is universal—every overwhelming problem is actually a bundle of distinct, smaller problems that have been mentally fused together. List each sub-problem separately with its own definition.WarningResist the temptation to create too many sub-problems. Three to six is usually the right range. More than that and you are creating complexity rather than reducing it.
- Analyze Each Sub-Problem IndependentlyFor each decomposed sub-problem, assess: How critical is this to overall success? How difficult is it to solve? What resources does it require? What is the timeline? By analyzing sub-problems independently, you often discover that some are already close to solved, some are less important than they seemed, and one or two are the actual drivers of the combined problem. This focused analysis is impossible when everything is jumbled together.Pro tipRate each sub-problem on a two-by-two matrix of importance versus difficulty. The high-importance, low-difficulty quadrant contains your quick wins.
- Sequence Your Solutions StrategicallyDetermine the optimal order for addressing decomposed sub-problems. Some solutions enable others—for example, solving your value proposition problem might make your pricing problem disappear. Some solutions are prerequisites—you cannot address market ubiquity until you have a product worth distributing broadly. Create a sequenced plan that builds momentum by solving enabling problems first and deferring dependent problems until their prerequisites are met.
- Assign Ownership and Track IndependentlyAssign clear ownership for each sub-problem to specific individuals or teams. Track progress on each sub-problem independently rather than monitoring the combined problem as a single metric. This prevents the common failure mode where progress on one dimension masks stagnation on another. Each sub-problem should have its own success criteria, timeline, and accountable owner.
When competing against Microsoft, Netscape PMs faced what felt like an insurmountable combined problem: a competitor with vastly more resources, distribution, and market power. Good PMs decomposed this into specific dimensions: where could Netscape deliver superior technical value (innovation speed), where should they match features (baseline browser capabilities), how should they price (free versus paid), and which market segments should they target versus yield.
Horowitz specifically identifies that bad PMs get confused about the differences among delivering value, matching competitive features, pricing, and ubiquity—treating them as one problem. A PM might simultaneously try to add every competitor feature, lower prices, expand distribution, and improve core value—spreading resources across four different strategies that require different approaches and potentially contradict each other.
Horowitz developed this insight watching PM teams at Netscape struggle against Microsoft. The bad PMs would say 'Microsoft is crushing us' as if that were a single problem requiring a single solution. The good PMs would decompose this into specific challenges: where exactly is Microsoft winning on features, where is our value proposition stronger, what pricing strategy could neutralize their distribution advantage, which market segments should we attack versus yield. This decomposition transformed an overwhelming competitive threat into a set of manageable strategic decisions, some of which Netscape could actually win.