Review
Pichler writes the way I wish more product authors did: short chapters, no anecdote padding, and a working artefact at the end of most of them. This is his book on product strategy and roadmaps, and it's the most practical treatment of the roadmap problem I've read.
The core argument is that a roadmap is not a list of features with dates. It's the path from your product vision to the outcomes you expect, and the things you build are the least interesting part of it. The goal-oriented roadmap format he proposes forces you to state what each release is meant to achieve before anything gets named.
I've handed the vision board to teams and watched it do real work, mostly by exposing that nobody could agree on the target group. That's the value: the templates are simple enough that the disagreement surfaces immediately instead of hiding behind a shared document nobody reads the same way.
The weakness is that it assumes a degree of autonomy plenty of product managers don't have. If your roadmap is negotiated with sales quarterly, the book has less to say about how to get from there to here. Read it for the artefacts, and expect to fight for the conditions that make them usable.
Key Takeaways
The parts worth keeping:
Vision, strategy, roadmap are different things
- The vision is the change you want to create and should outlive every plan. The strategy is how you intend to realise it. The roadmap is the path, expressed as outcomes over time.
- Conflating them is the most common failure. A roadmap standing in for a missing strategy turns into a queue of commitments nobody can prioritise.
- Each layer should be revisable at a different rate. If your vision changes as often as your roadmap, it was never a vision.
The goal-oriented roadmap
| Column | What goes in it |
|---|---|
| Date | A timeframe, deliberately coarse |
| Name | A label for the release, so people can talk about it |
| Goal | The outcome this release is meant to produce |
| Features | The few things likely to achieve it, held loosely |
| Metrics | How you will know the goal was met |
- Putting the goal before the features is the whole trick. It makes the feature list negotiable and the outcome the commitment.
The vision board
- One page covering the vision, the target group, their needs, the product itself, and the business value it creates.
- Its usefulness is diagnostic. Teams that cannot fill in the target group box in one sitting have found their real problem.
Strategy needs validating too
- Treat the strategy as a set of assumptions rather than a decision, and test the riskiest ones before committing a roadmap to them.
- Revisit it on a fixed cadence. A strategy reviewed only when something goes wrong is a strategy reviewed too late.