Remove Product Goals Remove Product Strategy Remove Roadmap
article thumbnail

OKRs and Product Roadmaps

Roman Pichler

What are Product Roadmaps? A product roadmap is an actionable plan that describes how a product is likely to evolve. [3] Fortunately, in the last ten years, outcome-based, goal-oriented roadmaps have become more popular. Let’s take a quick look at the roadmap’s five elements. and Android 14.0.

Roadmap 283
article thumbnail

GO Product Roadmap Checklist

Roman Pichler

Listen to the audio version of this article: [link] Overview The GO Product Roadmap consists of five elements, as the image below shows: Date, name, goal, features, and metrics. The most important element is the goal: It describes the outcome you want to achieve or the benefit you want to provide.

Roadmap 299
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Product Goals in Scrum

Roman Pichler

Product Goals Defined. The Scrum Guide released in November 2020 states that “the product goal describes a future state of the product … [It] is the long-term objective for the Scrum team.” It also suggests that “the product goal is in the product backlog. Figure 1: The Product Goal in Context.

article thumbnail

My Product Strategy Model

Roman Pichler

An effective product strategy is key to successfully create, enhance, and manage a product. There is no point in worrying about the product details and writing user stories if a sound product strategy is missing. But what exactly is a product strategy? Figure 1: My Product Strategy Model.

article thumbnail

10 Product Roadmapping Mistakes to Avoid

Roman Pichler

1 The Product Roadmap is a Feature-based Plan. Traditional product roadmaps are usually output-focussed plans that map a list of features, like registration, search, and reporting, onto a timeline. Such a roadmap essentially states when a piece of functionality will be delivered. I don’t think so.

Roadmap 328
article thumbnail

How to Get Started with Outcome-Based Product Roadmaps

Roman Pichler

Listen to the audio version of this article: [link] Traditional vs Outcome-based Roadmaps Before I share the four steps, let me briefly describe the main differences between a traditional, feature- and an outcome-based product roadmap. A traditional roadmap is essentially a list of features, which are mapped onto a timeline.

Roadmap 231
article thumbnail

The Product Strategy Cycle

Roman Pichler

Traditionally, strategy and execution are often viewed as separate, sequential pieces of work that are carried out by different people. For example, a product manager might determine the product strategy and one or more development teams might be tasked with executing it. I call these outcomes product goals.