Review
Bassino wrote the book about the gap between a product vision and a sprint backlog, which is exactly where most product organisations quietly fall apart.
He treats strategy, roadmaps and objectives as one connected system rather than three artefacts produced by different rituals, and that framing is the contribution. Plenty of teams have all three and no relationship between them: a vision nobody references, a roadmap negotiated with sales, and quarterly objectives invented separately. The book's argument is that if changing one doesn't force you to revisit the others, they aren't connected.
What I found most useful is the treatment of strategy as a set of choices about where to focus that can be tested rather than a document to be approved. He's concrete about how you decide between opportunities, which is the part most strategy writing skips by assuming the choice has already been made somewhere upstream.
It sits close to Pichler's Strategize in both content and audience, and if you already have that one the overlap is significant. Bassino goes further on scale, specifically how direction survives multiple teams, which is where the two diverge and where this one earns its place.
Key Takeaways
The parts worth keeping:
Three layers, one system
- Strategy, roadmap and objectives should be derived from each other. When they're produced independently, teams end up executing three different plans at once and nobody notices.
- The test is whether changing one forces changes in the others. If not, they're decorative.
- Most organisations have all three artefacts and no connection between them, which looks like maturity from outside.
Strategy as testable choices
- A strategy is a set of decisions about where to focus and where not to, expressed clearly enough that being wrong is possible.
- Treat the reasoning as assumptions and validate the riskiest before committing a roadmap to them.
- A strategy nobody could disagree with has not made any choices.
Direction at scale
| Problem as you grow | What it needs |
|---|---|
| Teams optimising locally | Shared outcomes rather than shared feature lists |
| Duplicate and conflicting work | Explicit ownership of problem areas |
| Strategy known only to leadership | Context distributed far enough down to be usable |
Objectives connect it to the week
- Objectives are the mechanism that turns direction into something a team can act on this quarter, not a separate performance ritual.
- When they are set independently of strategy, they measure activity and drift from the thing they were meant to advance.