The reading room · Digna Legi
What is Good Product Strategy?
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. Evidence appears substantive, but visual elements and any material outside the supplied text were not evaluated.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Original article ↗ · about 7 min (text estimate)
Why read this
Melissa Perri treats product strategy as disciplined learning toward outcomes, not a feature roadmap pretending uncertainty has disappeared.
AI brief · Checked against source text
The main idea
Melissa Perri argues that product strategy fails when it is reduced to a roadmap of features, because plans create false certainty and shift attention from outcomes to outputs. Her alternative is a layered system: a long-term vision, a nearer challenge, measurable target conditions, and a quantified current state, with teams experimenting against obstacles until they close the gap.
Go a little deeper
Plans answer the wrong question
The piece’s sharpest distinction is between knowing what to build and knowing what must become true. Feature plans can be useful later, but when they stand in for strategy they freeze assumptions before learning has happened. The failure mode is not execution sloppiness; it is measuring progress by shipped output while leaving the actual business and customer outcome under-examined.
The hierarchy narrows uncertainty
Perri’s structure works by decomposing ambition without pretending the path is already known. Vision stays qualitative and long-term; the challenge selects the first major business objective; target conditions turn that challenge into measurable near-term progress; current state prevents wishful thinking by recording the baseline before intervention. Each layer reduces ambiguity while preserving room to discover the right solution.
Experimentation has ownership boundaries
The framework is not pure team autonomy. Senior leaders set vision, the next management layer sets challenges, direct managers help define target conditions, and product teams identify user problems and obstacles. That matters because strategy becomes a chain of accountability: each level owns a different altitude of decision, while teams still learn how to reach their assigned outcome.
Customer problems are instrumental, not decorative
The final definition refuses the common split between business strategy and product craft. Product management is framed as solving customer problems in order to reach business objectives. That is narrower than simply pleasing users and broader than shipping revenue-driven code; both sides have to be present for the product to be more than implementation theater.
A case from the article
Uber wait time as a strategic chain
The hypothetical Uber example shows the framework moving from ambition to work. A vision of replacing car ownership and public transportation becomes a challenge to reduce long waits in weak cities. That challenge becomes a target condition around driver supply, such as one driver per 50 people, which sends the product manager to measure the current ratio and experiment against onboarding obstacles.
How the case is made
The case is made through practitioner observation, a Toyota Kata-inspired framework, and a hypothetical Uber example explicitly labeled as improvised.
Where the idea has limits
The Uber example is illustrative rather than factual strategy; Perri says she has no affiliation with Uber and is improvising everything after the CEO vision statement.
A question to take away · from Digna Legi
Where are you calling a feature sequence a strategy because uncertainty feels politically inconvenient?
What the original adds
The source includes the author’s 2016 qualification, concrete sample strategy statements, role-level ownership for vision/challenge/target conditions, and a follow-on note about roadmaps and stakeholder communication.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.