Product Strategy and Product Roadmap Practices for the Digital Age
Roman Pichler tackles the topic of strategy and product roadmap. He not only gives a high-level overview of what a good strategy and roadmap is, but also presents powerful frameworks and canvases to visualise them.
Whether our strategy is a few sentences summary or a fully-fledged business model, it’s just a hypothesis until verified. Thus, we should approach strategy work the way we approach product work. Treat it as a series of assumptions and devise experiments to test the hypothesis.
At any given moment, we should be aware what’s the riskiest assumption we are making about our strategy and have a plan to test that assumption.
A good tactic is to use timeboxes for strategy validation. Set a limited timeframe, up to 4 weeks, and devise an experiment to test the most critical assumptions. After the timebox, make one of three decisions:
A good practice is to hold regular strategy review meetings to ensure it’s still relevant and the risk associated with it are acceptable.
The best way to ensure the strategy isn’t just another document gathering dust is to visualise it and keep it in the centre of team activities.
One of the techniques to do so is to use [extended] product vision board.
Depending on the maturity of the strategy and individual needs, we can easily adjust the board to reflect what’s the most important for us.
We should also track metrics relevant to our strategy to evaluate its overall health. It’s surprisingly easy to get carried away by day-to-day priorities and detach from the strategy. Reviewing strategy metrics frequently can help us stay grounded.
One of the ways to choose which market segments to target is to use the GE/McKinsey matrix. It takes into account two main drivers.
Pros:
Cons: