Remove Product Strategy Remove Technical Review Remove Weak Development Team Remove Workshop
article thumbnail

10 Product Strategy Mistakes to Avoid

Roman Pichler

Listen to the audio version of this article: [link] 1 No Strategy The first and most crucial mistake is to have no product strategy at all. When that’s the case, a product is usually progressed based on the features requested by the users and stakeholders. The strategy is therefore either too big or too narrow.

article thumbnail

10 Product Roadmapping Mistakes to Avoid

Roman Pichler

You can avoid these drawbacks by using a different roadmap type: a goal-oriented or outcome-based product roadmap. As its name suggests, this roadmap focuses on product goals and outcomes, such as acquiring customers, increasing engagement, and future-proofing the product by removing technical debt.

Roadmap 316
Insiders

Sign Up for our Newsletter

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

article thumbnail

10 Tips for Effective Product Management Meetings

Roman Pichler

For example, a product strategy workshop might have the objective to identify the key changes required to achieve product-market fit. Contrast this with a sprint review meeting , which might help you determine if users can easily sign up for the product. Assess product strategy and adjust if necessary.

article thumbnail

8 Tips for Collaborating with Development Teams

Roman Pichler

Manage the Product, not the Team. Focus on your job as the product manager or product owner, and manage the product, not the team. Provide guidance on the product, including its market, value proposition, business goals, and key features. Treat the Team as an Equal Partner.

article thumbnail

Collocation, Trust, and Distributed Teams

Roman Pichler

I once worked with a telco company that was developing a brand-new commercial product. Product management and development were located at separate sites in different countries. But this didn’t seem to matter much as everybody was in great spirits and had high hopes for the new product. To Collocate or Not.

article thumbnail

Collocation, Trust, and Distributed Teams

Roman Pichler

I once worked with a telco company that was developing a brand-new commercial product. Product management and development were located at separate sites in different countries. But this didn’t seem to matter much as everybody was in great spirits and had high hopes for the new product. To Collocate or Not.

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.

Roadmap 331