Remove Roadmap Remove Vision Remove Workshop
article thumbnail

Product Vision FAQs

Roman Pichler

What is the Product Vision? The product vision describes the ultimate purpose of a product, the positive change it will bring about. As the product vision, I could then choose “help people eat healthily” or just “healthy eating.” What Makes a Good Product Vision? Who Owns the Product Vision?

Vision 336
article thumbnail

Six Qualities of a Great Product Vision

Roman Pichler

An inspiring vision creates a meaningful purpose for everyone involved in making the product a success including the stakeholders and development team members. If the vision resonates with you, then this will help you do a great job, especially when the going gets tough. The vision pulls you.”. A shared vision unites people.

Vision 334
Insiders

Sign Up for our Newsletter

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

article thumbnail

MVP Roadmapping

The Product Guy

You have to work with different stakeholders to define the product vision and strategy, define the set of features that the product will have and figure out a rollout plan. Define Product Vision and Strategy. I recommend you also add to this board the product vision as suggested by Roman Pitchler’s Product Vision Board.

Roadmap 334
article thumbnail

10 Tips for Creating an Agile Product Roadmap

Roman Pichler

Whenever you are faced with an agile, dynamic environment—be it that your product is young and is experiencing significant change or that the market is dynamic with new competitors or technologies introducing change, you should work with a goal-oriented product roadmap, sometimes also referred to as theme-based. 2 Do the Necessary Prep Work.

Roadmap 350
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 238
article thumbnail

My Product Strategy Model

Roman Pichler

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? At the heart of the model in figure 1 are four artefacts: the product vision, the product strategy, the product roadmap, and the product backlog.

article thumbnail

Scaling a Product Organization

The Product Guy

Decision-making process for PMs: No common process, standardized No journey from OKRs to problems and solutions No articulation of the roadmap with uncertainty Not ahead of the needs Problems for making streamlined decisions, for articulating decisions. Low accountability Limited visions of the product by PMs. Low transparency.