Remove Management Remove Meeting Remove Vision Remove Weak Development Team
article thumbnail

Common Product Vision Board Mistakes

Roman Pichler

This article assumes that you are familiar with the product vision board or the key elements of a product strategy : market, value proposition, standout features, and business goals. Vision Captures Product Idea or Business Objective. Additionally, such a vision is hardly inspiring. Target Group is (too) Big and Heterogenous.

Vision 303
article thumbnail

10 Tips for Effective Product Management Meetings

Roman Pichler

Be clear on the reason why the meeting is needed. What’s the meeting about? Contrast this with a sprint review meeting , which might help you determine if users can easily sign up for the product. Carefully consider who should participate in the meeting to achieve the objective you have set. 1 Set an Objective.

Insiders

Sign Up for our Newsletter

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

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] I certainly don’t intend to make anyone feel bad.

article thumbnail

One Bad Meeting Can Create a Culture of Silence

Business of Software Conference

Elizabeth O’Neill, People & Culture expert, BoS participant and this year speaker, explains the difference between having one bad meeting and creating a culture of silence in this guest blog post. One Bad Meeting Can Create a Culture of Silence. Excitedly, he pulls together his small team and describes his idea. .

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. Treat the Team as an Equal Partner. The team members are not your resources but the people who create your product. Assume that the team members want to do their best.

article thumbnail

Good Product Team/Bad Product Team

Amplitude

As VP of Product at Amplitude, I get the opportunity to work with hundreds of different products teams every year?—?ranging So in the mode of Ben Horowitz’s classic essay Good PM/Bad PM , I’ve captured my thoughts on what I believe makes a good product team vs a bad product team. PM, Design and Engineering?—?are

article thumbnail

A Learning Roadmap for Product People

Roman Pichler

I’ve chosen quarters in the sample roadmap above, but you can use shorter time frames, of course, if you can meet your learning goals more quickly. The fourth and final line states how you intend to meet the learning goals. This can help you tie individual learning goals to team and department goals.

Roadmap 323