The vocabulary the exams and the daily work both assume you already have. Every entry gives the definition, the source it is drawn from, and the misreadings that follow from getting it wrong.
36 concepts in Strategy, page 2 of 2
Define competitive context and translate it into credible messages for buyers and users. Includes a positioning workflow and a worked maintenance example.
Strategy
Choose what customers pay for, estimate contribution and test pricing assumptions through realistic buying decisions.
Strategy
The roadmap shows the vision and the phases of deliverables and is a plan rather than a commitment. The release plan is the dated one. Keeping them separate is what stops a direction becoming a promise.
Strategy
Write clear exclusions with a reason, owner and review condition. Respond to competing requests without turning a temporary choice into a permanent ban.
Strategy
Use the five layers of the product strategy stack to check alignment and diagnose gaps between company direction and product work.
Strategy
Apply the course to a fictional maintenance business. Produce a market estimate, strategy brief, experiment plan, economics model and roadmap with a downloadable workbook.
Strategy
Compare project, product, rolling and staged funding. Define spending limits, evidence reviews and decision authority without losing financial control.
Strategy
Richard Rumelt's three part structure for a strategy, covering the diagnosis of the obstacle, the guiding policy chosen to deal with it and the coherent actions that carry the policy out, and why the three have to chain.
Strategy
Proactive communication with the people affected by the product, from strategy through execution, on a rhythm rather than in response to escalation.
Strategy
Use scenarios and staged commitments when forecasting is unreliable. Includes a practical example of preserving an option without postponing every decision.
Strategy
Turning a validated opportunity into a proposal the business can fund, with a market size, a financial model and the risks stated rather than buried.
Strategy
Thirty-seven product activities arranged into seven categories, used as a shared vocabulary and as a checklist for finding which activities nobody in the organisation currently owns.
Strategy
Distinguish a product feature from a customer advantage and explain how capabilities, costs and evidence support a reason to win.
Strategy
Define a product strategy with a target customer, a reason to choose the product, resource choices and evidence. Includes a worked example and a strategy writing exercise.
Strategy
Define who develops, approves and carries out a product strategy. Includes a decision rights example and a practical strategy approval record.
Strategy
Distinguish delivery problems, weak adoption and unsupported strategic assumptions before deciding whether to improve execution or change direction.
Strategy