When to use me
- The team is very busy and ships a lot, but can't clearly say what value it brought → use [Feature Trap Self-Check]
- Strategy is a pile of slogans and doesn't reach what the team does every day → use [Four Layers of Strategy Deployment]
- Want to systematically "choose the problem → set direction → validate" → use [Product Kata]
- Not suitable for: specific interview scripts (see pm-method-mom-test), structured slicing of requirements (see pm-method-story-mapping). This book addresses "why the organization is doing useless work at the organizational level, and how to shift to outcomes."
Core frameworks
Framework 1: Feature Trap Self-Check (The Build Trap, Part One)
Applicable scenario: judging whether a team/organization is using "output" to impersonate "value."
Steps:
- Look at what the team is measured on: the number of features delivered (output) or the outcomes achieved (outcome)?
- Look at the shape of the roadmap: is it a list of features with dates, or a set of business/user outcomes to achieve?
- Look at where requirements come from: are they features pushed in by the boss/sales, or derived from strategy and user problems?
- Output: a diagnosis of the degree of the trap + the one signal that should be changed first (measurement method/roadmap/source of requirements)
Framework 2: Four Layers of Strategy Deployment (Strategy Deployment, Part Three)
Applicable scenario: connecting high-level strategy to the team's daily work and eliminating the "disconnect between strategy and execution."
Steps:
- Vision → where we ultimately want to go
- Strategic Intent → the few key company-level directions for the current stage
- Product Initiative → the problems the product must solve / the outcomes it must pursue in order to realize the intent
- Options / Experiments → candidate solutions for solving the problem and validation Align layer by layer; each layer can answer "what does it serve in the layer above?"
- Output: an alignment map that runs from vision through to specific product initiatives
Framework 3: The Product Kata (The Product Kata, Part Two)
Applicable scenario: systematically moving from the "current condition" toward the "direction," advancing through experiments rather than guesswork.
Steps (loop):
- Direction: what outcome are we trying to achieve?
- Current Condition: how far are we from it now, and what does the data say?
- Target Condition: the measurable state to be reached in this step
- Obstacles and experiments: what is blocking the way? What will the next smallest experiment validate?
- Run the experiment → learn → return to step 2 and loop
- Output: a repeatable "goal—obstacle—experiment" rhythm
Decision rules (with source annotations)
- If the team measures success by "how many features were delivered," then you are in the feature trap—switch to outcome metrics. (Part One)
- If the roadmap is a "dated feature list," rewrite it as "outcomes to achieve + options to validate." (Part 3)
- If a requirement cannot answer "which strategic intent does it serve / which user problem does it solve," then pause it and first fill in this connection. (Part 3)
- If you are unsure whether the solution is right, use the product kata to set up a minimal experiment to validate it, rather than directly scheduling it to completion. (Part 2)
- The product manager's role is "manager of value exchange," not "project manager taking requirements"—use this to calibrate the PM's daily work. (Part 2)
- If the strategy has only a vision and no middle layer, the team will inevitably work in silos—fill in the two layers of strategic intent and product action. (Part 3)
- Good strategy is a framework for "deciding what not to do," not a list of "wanting everything." (Part 3)
Checklist: Escape the feature trap (synthesis of the whole book)
- The team's success metric is outcomes (user behavior/business results), not the number of features
- The roadmap expresses the outcomes to achieve and options to validate, not a committed feature list
- Everything being worked on can be connected to a strategic intent and a user problem
- The team has a clear direction and uses experiments (product kata) to approach it
- The time the PM spends on "understanding problems and validating" is no less than on "writing requirements and delivering"
- There is a complete chain from vision → strategic intent → product action → options
- Have the courage to say no to "requirements that do not serve the strategy"
Anti-patterns (explicitly warned against in the book)
- Feature factory—treating busyness and delivery volume as value, with no one accountable for outcomes. (Part 1)
- Treating the roadmap as a commitment list—locking in a bunch of dated features, losing the ability to adjust based on learning. (Part 3)
- Project-based thinking—disperse once done, responsible only for launch, not for outcomes. (Part 2)
- Strategy reduced to slogans—having a vision but no middle layer, so the execution layer can only fill in the gaps on its own. (Part 3)
- Relying on "heroic PM/boss making the call" rather than a replicable product process and organizational capability. (Part 4)
Boundary statement
- Published in 2018, the method is stable; it diagnoses "wasted effort at the organizational/strategic level" and does not provide operational details for specific interviews or delivery slices
- Applicable to: product organizations of a certain scale that need strategy-execution alignment; for very early single-person/small teams, the four-layer strategy deployment can be streamlined
- "Outcome orientation" depends on an environment that can define and measure outcomes; when outcomes are hard to quantify (platform, compliance, infrastructure), apply it with caution
- Highly resonates with Cagan's "product operating model," and the two can corroborate each other; where they overlap, prioritize this book's operational layer of "strategy deployment + product kata"
- If the chapter attribution differs when distilled from secondary sources, the original book shall prevail
Workflow
After receiving a user question:
- Match the scenario → choose a framework (feature trap self-check / strategy deployment / product kata)
- Missing core inputs (team goals, current roadmap form, strategy) → list the information that needs to be filled in all at once; use WebSearch for industry facts when needed, do not fabricate
- Execute according to the framework steps, providing step-by-step intermediate outputs (diagnostic conclusions / strategic alignment map / kata loop)
- Review using the "Escape the feature trap checklist," and mark items that do not pass
- End with a boundary statement, suggesting that another perspective can be used for cross-validation (e.g., "For which specific assumption should be tested, use the assumption test in pm-advisor-torres")
This Skill was generated by career-skill-factory. The content is distilled from the original work, and the copyright belongs to the original author Melissa Perri; it is for personal learning only.