"The PO vs PM Madness: Why Finding Common Ground is Essential for Successful Product Development"

Glasp

Hatched by Glasp

Jul 10, 2023

4 min read

0

"The PO vs PM Madness: Why Finding Common Ground is Essential for Successful Product Development"

In the world of product development, there is often a debate about the roles of the Product Owner (PO) and the Product Manager (PM). Some argue that the two roles are one and the same, while others believe they serve different purposes. This article aims to shed light on this ongoing debate and explore the importance of finding common ground between the two roles for successful product development.

Madness #1: PO is the same as PM

One common misconception is that the PO and PM roles are interchangeable. However, this is not the case. The PO is responsible for ensuring that the product meets the requirements set by the Scrum team and satisfies the Sprint Goal and Definition of Done. On the other hand, the PM is tasked with ensuring the value and viability of the product, while the designer focuses on usability and the tech lead ensures feasibility. Each role has its own unique responsibilities and contributions to the product development process.

Madness #2: The PM plus PO

In some organizations, there is a tendency to add Product Owners as a separate position to work with Product Managers. This separation is often seen as a way to divide the responsibilities between "the business person" and "the person that talks with the developers and manages the backlog." However, this approach may not be the most effective in optimizing outcomes across a diverse and complex adaptive system. It is important to consider the overall goals and objectives of the product development process and ensure that all team members work collaboratively towards achieving them.

Madness #3: The PO as a PM overnight

Another challenge arises when organizations attempt to transition from a delivery/feature/project team model with Product Owners to an empowered product team model with true Product Managers. This transition requires training and empowering the POs to take on the responsibilities of a PM, which is a very different role. Without proper training and support, expecting a PO to suddenly become a PM can lead to confusion and ineffective product development. To ensure a successful transition, organizations should invest in training and empowering their POs to excel in their new roles.

Finding Common Ground and Unique Insights

While the debate between the PO and PM roles continues, it is important to focus on finding common ground between the two. Both roles have a shared objective of building products that customers love within sustainable and innovative business models. By aligning their goals and collaborating effectively, POs and PMs can leverage their unique skills and insights to drive successful product development.

One unique insight that can be derived from this debate is the importance of understanding the needs of users. Y Combinator, a renowned startup accelerator, emphasizes the significance of founders who understand a specific group of users and can create products that cater to their needs. This aligns with the Scrum approach, where the PO focuses on meeting the requirements of the users and ensuring the value of the product.

Actionable Advice

To navigate the PO vs PM madness and ensure successful product development, here are three actionable pieces of advice:

  • 1. Foster Collaboration: Encourage collaboration between the PO and PM to leverage their unique perspectives and insights. By working together, they can ensure that the product meets the needs of the users while also being viable and valuable.
  • 2. Invest in Training: If transitioning from a delivery/feature/project team model to an empowered product team model, provide training and support to POs to excel in their new roles as PMs. This will help them adapt to the new responsibilities and contribute effectively to the product development process.
  • 3. Focus on User Needs: Prioritize understanding the needs of the users and building products that satisfy those needs. This will ensure that the product has a market from the beginning and increase the chances of success.

Conclusion

In conclusion, the debate between the PO and PM roles can be seen as a "madness" in the world of product development. However, finding common ground and understanding the unique contributions of each role is crucial for successful product development. By fostering collaboration, investing in training, and focusing on user needs, organizations can navigate this madness and build products that customers love within sustainable and innovative business models.

Hatch New Ideas with Glasp AI 🐣

Glasp AI allows you to hatch new ideas based on your curated content. Let's curate and create with Glasp AI :)