# What's NOT a Product Owner?  ## Metadata - Author: [[David Pereira & David Pereira On Linkedin]] - Full Title: What's NOT a Product Owner? - Category: #articles - Summary: The text discusses common misunderstandings that can lead to failure as a Product Owner, such as acting like a waiter, manager, architect, or backlog manager. It emphasizes the importance of embracing Product Management competencies, collaborating with the team, and maximizing business value while respecting boundaries. To be successful as a Product Owner, one must focus on continuous learning, prioritize effectively, and foster collaboration within the Scrum Team. - URL: https://www.linkedin.com/pulse/whats-product-owner-david-pereira/?trackingId=twWH8PzJSZ%2BYXDqkeZruJw%3D%3D ## Highlights - The Product Owner’s Mutation So let’s go now to the anti-patterns. What are the most common mutations I have ever seen? • **Waiter**: receives orders and sends them to the team directly. The waiter’s behavior results in low-business value and many pointless features. • **Manager**: micromanage the team and behave as developers’ manager. • **Architect**: defines all the solutions alone. Developers don’t have a voice in how to solve problems. • **Backlog Manager**: protect the product backlog and lock it to ensure no one can handle it. Only the Product Owner can touch this kid. ([View Highlight](https://read.readwise.io/read/01hxfagxqhbb5vp5yrf94xx48w))