article thumbnail

3 Empowerment Levels in Product Management

Roman Pichler

Listen to the audio version of this article: [link] Introduction To discuss empowerment in product management, I find it helpful to distinguish three main levels of decision-making authority, product delivery, product discovery, and product strategy, as the model in Figure 1 shows. [1]

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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

What Do We Owe Our Teams?

Mironov Consulting

Many of my discussions with product leaders (CPOs, VPs and others who manage teams of product folks) are about the substance of product management: portfolios, competing stakeholders, pricing & packaging, tarot cards as a revenue forecasting model.  Last

article thumbnail

Seven Product Backlog Mistakes to Avoid

Roman Pichler

The Product Backlog is Too Big. A few years ago, I was asked to help a healthcare company with their agile transition and its impact on product management. One of the challenges the agile transition team was concerned about was the choice of the right product backlog tool, which at first seemed odd to me.

article thumbnail

How Agile Has Changed Product Management

Roman Pichler

Before the advent of agile frameworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together product roadmap, write a requirements specification, and then hand it off to a project manager.

Agile 249
article thumbnail

10 Product Roadmapping Mistakes to Avoid

Roman Pichler

Your job is not to please the stakeholders, but to achieve product success. If you say yes to every request, you are in danger of creating a Frankenstein product—a product that is a collection of unrelated features, offers a weak value proposition, and gives rise to a poor user experience.

Roadmap 316
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.