The Intersection of Product Critique and the PO vs PM Debate

The Intersection of Product Critique and the PO vs PM Debate

Introduction:
In the world of product development, understanding people's desires and how they interact with a product are two core tenets. By observing and being curious about people, we can create great products that provide value and are well-crafted. However, the ongoing debate between the Product Owner (PO) and Product Manager (PM) roles adds another layer of complexity to the product development process. This article aims to explore the common points between product critique and the PO vs PM madness, while also providing actionable advice for product teams.

Understanding First Impressions and Value Propositions:
When conducting a product critique, it is crucial to consider how first impressions shape our perception of an app's value proposition. Most opinions of a product are formed within the first few minutes of interaction, which highlights the importance of creating a positive initial experience. By understanding what motivates and delights users, designers and product thinkers can craft experiences that resonate with their target audience.

The Role of Product Owners and Managers:
The confusion surrounding the roles of PO and PM is a common point between product critique and the PO vs PM debate. In Scrum, the PO is responsible for ensuring that the product increment meets the Sprint Goal and Definition of Done. However, this role is primarily focused on delivering output rather than driving true innovation for customers. On the other hand, the PM is explicitly responsible for ensuring value and viability, collaborating with the team to discover solutions that work for everyone.

The Pitfalls of Combining PO and PM Roles:
The PO plus PM approach, often seen in feature factories, can lead to inefficiencies and hinder the creation of customer-centric products. Optimizing for outcomes across a complex adaptive system is challenging under this model. It is crucial for organizations to recognize the need for empowered product teams with dedicated Product Managers to drive sustainable profitability and innovation. Training POs in Product Management and empowering them in their new role is essential for a successful transition.

Actionable Advice:

1. Foster a culture of curiosity and observation: Encourage your product team to be curious about people's desires and behaviors. By closely observing users and their interactions with the product, you can gain valuable insights to inform your decision-making process.

2. Seek diverse perspectives: Don't rely solely on your own opinions when critiquing a product. Reading reviews, comments, and social media discussions can provide additional perspectives on what works and what doesn't in the broader market. This broader view helps you identify areas for improvement and innovation.

3. Invest in proper role definition and training: If you aim to transition from a delivery/feature/project team model with POs to an empowered product team model with dedicated Product Managers, invest in training your POs in Product Management. This will equip them with the necessary skills and knowledge to succeed in their new role, ensuring the success of your product development efforts.

Conclusion:
Product critique and the PO vs PM debate intersect in the pursuit of creating great products that customers love. By understanding people's desires, observing user interactions, and being curious, we can build innovative and valuable products. However, it is crucial to recognize the distinct roles of PO and PM and avoid the pitfalls of combining them. Three actionable pieces of advice include fostering curiosity and observation, seeking diverse perspectives, and investing in role definition and training. By following these recommendations, product teams can navigate the complexities of product development more effectively and drive sustainable success.