The product strategy is a crucial product management artefact. But what exactly is it? Who should create the strategy? How often should it be reviewed and updated? How does AI influence strategic decisions? And what product strategy mistakes should you avoid? These are some of the strategy questions that I am frequently asked in my workshops and coaching sessions, and that I answer in this article.
As helpful as they can be, product roadmaps are not always enough. To closely align a group of products and ensure that they all move in the same direction, you’ll benefit from a portfolio roadmap. In this article, I explain what a product portfolio roadmap is. I show how you can use the template below to build your own outcome-based portfolio roadmap. I discuss how you can connect your portfolio roadmap to the portfolio strategy and use it to direct the product roadmaps, and I describe who should be involved in developing the plan.
As helpful as they can be, product roadmaps are not always enough. To closely align a group of products and ensure that they all move in the same direction, you’ll benefit from a portfolio roadmap. In this episode, I explain what a product portfolio roadmap is. I share a template to help you build your own outcome-based portfolio roadmap. I show how you can connect your portfolio roadmap to the portfolio strategy and use it to direct the product roadmaps, and I describe who should be involved in developing the plan.
Outcome-based product roadmaps offer many benefits over traditional, feature-based ones including a strong focus on the value a product should create. But how can you introduce this new approach when an organisation is used to feature-based plans and stakeholders find it difficult to trust an outcome-based roadmap? To address this challenge, I introduce a four-step process in this article.
OKRs—objectives and key results—are a popular goal-setting technique. But can and should you use OKRs on product roadmaps? What benefits does this approach offer and are there any drawbacks? These are the questions I’ll answer in this article.
OKRs—objectives and key results—are a popular goal-setting technique. But can and should you use OKRs on product roadmaps? What benefits does this approach offer and are there any drawbacks? These are the questions I’ll answer in this podcast episode.
The product roadmap can be an incredibly useful planning tool that aligns the stakeholders and development teams and communicates how a product is likely to evolve. Sadly, that’s not the case for all roadmaps. To ensure that your product roadmap is effective, you should make it goal-oriented or outcome-based, shared, and actionable, as I explain in this article.
Whether product roadmaps should show dates is a controversial topic in product management. Some people passionately argue that dates should be banned from roadmaps. Others claim that they are useful. This article discusses the pros and cons of using dates on product roadmaps to help you decide which option is right for you.
A product roadmap is a high-level plan that shows how a product is likely to develop over the next few releases. While that’s true for any roadmap, there is no one right product roadmap format. Instead, you should choose the roadmapping approach that works best for your product. This post shows you how to do it.
The product backlog is a great tool to capture ideas and requirements. But it is less suited to describe how the product is likely to develop in the longer term. This is where the product roadmap comes in. But how do the product backlog and the product roadmap relate? Is the backlog derived from the roadmap or is it the other way round? Should the product owner be responsible for both artefacts? Read on to find out my recommendations.