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

Building a Great Product Management Organization

Melissa Perri

I then do various interviews with executives all the way to Product Management team members and surrounding functions. But that’s okay, because once we know where the weak spots are, we can fix them. Siloed Teams : Teams work in isolation rather than collaboratively, resulting in inefficiencies and a lack of unified vision or approach.

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

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.

article thumbnail

Everything You Need to Know about Product Portfolio Strategy

Roman Pichler

Their visions, target groups, needs, standout features , and business goals must comply with the overall portfolio strategy. [1] To get started, create your own Portfolio Vision Board by downloading and adapting the Product Vision Board or by recreating it in your favourite tool.

article thumbnail

Product Goals in Scrum

Roman Pichler

The Scrum Guide released in November 2020 states that “the product goal describes a future state of the product … [It] is the long-term objective for the Scrum team.” The product owner is accountable for “developing and explicitly communicating the product goal.” The entire Scrum team is “focused on one … product goal” at a time.

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 347
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.