The “Why” Behind Your Product Roadmap

In the very best companies, roadmaps support key objectives with very specific measures impacting the business. These key objectives capture details like who is responsible, how it will be measured, and specifically when it will get done. Roadmaps are great at showing a direction, but they often don’t tell the story of “why.” Great companies have systems and processes and a way to talk about the “why” behind what they are doing. For companies to get to the “why,” they need to be clear on these strategic questions.

The vast majority of product roadmaps move the product in a positive direction, but desired results are only achieved if there is clarity around where it is taking you, and why. Well-run companies are honest about the reality of their current products. Companies that can be clear about where they want to go and know how to talk about it in a meaningful way have a strategic advantage over competitors. Their teams are aligned on a strategy that is supported by specific objectives and resources. They start with a strategy and the results they want to achieve. They have clarity on the “why” before talking about “how.”

And while strategy and Roadmaps set the direction, they are not enough to deliver results. The best companies are also insanely great at execution. For example, Google instituted a process called Objectives and Key Results (OKR) early on. OKR’s are a robust version of business and individual objectives that have clear accountability and links to results. OKR’s are way to translate strategy into action by having teams think in context of results they want to achieve prior to developing a roadmap.

This sets up the product roadmap so that it can be used as a tool to help drive results and link back to the business objectives and strategic direction. For companies with no clear strategy or objectives, the net result is teams setting their own strategy and objectives, which can distract companies from achieving the results they want. Product Management teams need to pivot from asking “What do we want to build?” to high gain questions like:

• What features do we need to support the strategy?
• What results will this drive?
• What objectives are we trying to meet?

Using this process, the Roadmap is more tightly driven by the corporate objectives and strategy. There is an emerging set of tools to do this and make the linkage between the roadmap, objectives, and strategy more visible to employees. Aha! has a strategy tool that allows users to clearly define the vison the “why” to your product roadmap. www.aha.io/product/features/strategy.

You can also link the product roadmap to your objectives. blog.aha.io/business-strategy-link-roadmap
Product managers are uniquely placed to tie these pieces together, and best practices follow a process that results in strategic linkage between strategy, objectives, and roadmap. This brings clarity to what product managers deliver and how they communicate with external stakeholders and customers. The result is:

• A detailed strategy independent of the budget and product roadmap
• Clear business objectives with accountable owners and specific dates (OKR’s)
• A product roadmap that links back to the strategy and objectives
• Roadmap deliverables and objectives with key measures defined

The deeper companies can align strategy and business objectives with the product roadmap, the more clarity teams will have on the “why” setting up companies to achieve desired results.

About Don
Don Stoddard is a Product Management Leader and graduate of Bentley University. He has worked for both small and large companies in the B2B and B2C software industry. You can connect with Don on LinkedIN www.linkedin.com/in/donstoddard