product-strategy
/layers:product-strategy
Assumes /layers:intro has been loaded for framework context.
Strategy is the first layer of the solution space — the point where problem space understanding converts into deliberate decisions about scope and direction. It is about choices: which user needs to serve, and which business outcomes to target.
Decisions this layer needs to make:
- What is the business outcome this work serves?
- Which user opportunities (needs, pains, desires) connect genuinely to that outcome?
- What solution bets are we placing on those opportunities?
- How do we test the riskiest assumptions cheaply?
- Which bets to pursue first, and why?
Methods:
| Method | When |
|---|---|
| Opportunity Solution Tree (OST) (Teresa Torres) | Default. Makes outcome → opportunity → solution → experiment connections explicit. Good for ongoing discovery cadences. |
| Impact mapping (Gojko Adzic) | B2B products with multiple stakeholders who each need to change behaviour. |
More from jamiemill/layers-skills
layers-conceptual-model
Defines the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer
160layers-domain
Maps domain concepts, terminology conflicts, and bounded contexts — produces a noun harvest for the conceptual model layer
158layers-orient
Diagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus
157layers-intro
Framework orientation for Layers of Product Design — load this first; provides the context all other skills depend on
157layers-product-strategy
Connects user opportunities to business outcomes and solution bets — produces a strategy tree and prioritised experiments
157layers-interaction-flow
Maps interaction structure and flow — produces breadboard notation with edge cases, failure paths, and open decisions
157