02 · Territory · Decide what matters
Strategy
Where should we invest our limited time and resources?
Map32 skills
7 capabilitiesClick a tile to open a skill
- 02.1Product visionThe long-term picture of what the product is for and why it should exist. It gives a team a direction to check daily decisions against.
- 02.2Product positioningHow the product is framed in the minds of the right customers, relative to the alternatives they already know.
- 02.3Goal settingTurning direction into measurable targets, so a team knows whether it is making progress and can say no to work that does not move them.
- 02.4PrioritizationDeciding what to do first given limited time. It weighs value, cost, risk and timing instead of following whoever asks loudest.
- 02.5Product scopingCutting an idea down to the smallest version that still delivers value and produces learning. Good scoping is often the biggest speed gain a team has.
- 02.6Product planningArranging work over time so a team can coordinate, while staying ready to change course when evidence changes.
- 02.7Business modelsHow the product creates, delivers and captures value. Every technical and product decision eventually shows up in the costs or the revenue.
About Strategy
02Strategy is choosing what to work on and, just as often, what to leave alone. It covers where the product is heading, who it is for, how success is measured, and how the business makes money. A product engineer does not need to own the strategy, but needs to understand it well enough to make hundreds of small decisions that point the same way.
What a product engineer should be able to do here
Explain why something should be built now rather than later, which assumptions matter most, and what the smallest valuable investment would be.