Remove Product Goals Remove Roadmap Remove Workshop
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 337
article thumbnail

Three Qualities of Great Product Roadmaps

Roman Pichler

Goal-oriented (a.k.a. Traditionally, product roadmaps are output-focussed plans that map features like registration, search, and reporting onto a timeline. Such a roadmap essentially states when a piece of functionality will be delivered. Listen to this article: [link]. Outcome-based).

Roadmap 290
Insiders

Sign Up for our Newsletter

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

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 234
article thumbnail

The Product Strategy Cycle

Roman Pichler

Based on this insight, I have come up with the product strategy cycle shown in the picture below. It’s a model of an iterative process that systematically links the product strategy with the product roadmap , the product backlog , the development work, and the key performance indicators (KPIs).

article thumbnail

My Product Strategy Model

Roman Pichler

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? How does it differ from a product roadmap and how do the two plans relate? And what’s their relationship to the product vision and the product backlog?

article thumbnail

Seven Product Backlog Mistakes to Avoid

Roman Pichler

Third and most importantly, focus the backlog on a specific product goal. Then decline and remove items that do not serve this goal, as I discuss below. The Product Backlog is Too Detailed. The former means that there is no product goal that guides the decision if an item should be added to the product backlog or not.

article thumbnail

Making Effective Product Decisions: Tips for Deciding with Stakeholders and Dev Teams

Roman Pichler

In practical terms, involve stakeholders and dev teams in decisions that affect the product strategy and the product roadmap —be it that you create the plans or that you make bigger changes to them. Additionally, include the development team members in product backlog decisions , and always choose sprint goals together.