The PO vs PM Madness: Is it OK to Highlight Your Own Stuff?

The PO vs PM Madness: Is it OK to Highlight Your Own Stuff?

In the world of product development and management, there seems to be a never-ending debate about the roles and responsibilities of Product Owners (PO) and Product Managers (PM). Some argue that they are essentially the same, while others believe they should be separate positions. This article aims to shed some light on this ongoing madness and explore the concept of highlighting one's own work.

Madness 1: PO is the same as PM

One school of thought argues that the PO and PM are essentially the same role, just with different titles. They believe that in Scrum, the PO is responsible for ensuring that the product increment satisfies the Sprint Goal and meets the Definition of Done. The focus here is on delivering output rather than true innovation on behalf of customers. This perspective sees the PO as an administrative role, while true product innovation falls under the purview of the PM.

Madness 2: The PM plus PO

Another perspective suggests that it may be convenient to have both a PM and a PO in a team, especially for feature factories. This allows for a clear separation between the "business person" who works with developers and manages the backlog (PO) and the person responsible for ensuring value, viability, usability, and feasibility (PM). However, this approach may not optimize outcomes across a diverse and complex adaptive system, as emphasized by the SAFe framework.

Madness 3: The PO as a PM overnight

If the goal is to build innovative and profitable products that customers love, having both a PO and a PM in the same team may not be the most effective approach. Moving towards an empowered product team model with true Product Managers requires a shift in mindset and skill set. In such a model, it is crucial to train POs in Product Management and empower them to take on a different role. This transformation may be necessary for organizations that currently operate on a delivery/feature/project team model with Product Owners.

Is it OK to highlight your own stuff?

Now, let's shift gears and explore the concept of highlighting one's own work. Highlighting has become a popular feature in various digital platforms, as it enriches the reading experience and creates a lightweight way for readers and writers to connect. For readers, highlighting allows them to share their favorite parts with their followers, making the reading experience more social. It also helps them notice things they might have skimmed over, thanks to highlights from people they follow.

For writers, highlighting serves as a feedback mechanism. It lets them know that their message is resonating with readers and that they appreciate their work. It provides validation and encouragement, especially when a specific sentence or idea is highlighted repeatedly. Writers can gauge their impact and make adjustments based on the parts that receive the most attention.

Three actionable advice for navigating the madness:

1. Understand the nuances: Take the time to understand the differences between the roles of a PO and a PM. Recognize that while there may be overlap, each role brings unique value to the product development process. This understanding will help you make informed decisions about team structures and responsibilities.

2. Foster collaboration: Regardless of whether you have a separate PO and PM or a combined role, fostering collaboration is essential. Encourage open communication, cross-functional discussions, and a shared understanding of product goals. By working together intensively, teams can discover solutions that satisfy all stakeholders.

3. Embrace continuous learning: For organizations looking to transition from a delivery-focused model to an empowered product team, investing in continuous learning is crucial. Provide training and resources to empower POs to take on the role of PM effectively. Encourage a growth mindset and create opportunities for skill development to ensure success in the new paradigm.

In conclusion, the debate between the PO and PM roles will likely continue, but what is clear is that both positions play a vital role in product development. Understanding the nuances and finding the right balance for your organization is key. Additionally, highlighting one's own work can be a valuable tool for both readers and writers, enhancing the reading experience and providing feedback. By embracing these concepts and taking actionable steps, organizations can navigate the madness and drive successful product outcomes.