Paweł Huryn’s Post

View profile for Paweł Huryn

Let’s Learn AI PM Together | Actionable Insights & Step-by-Step Playbooks for AI PMs | Join 125,000+

In 2025, we need to end this madness. Product Owner is not a job title. When you split the roles: - Product Manager talks to the business and customers. - Product Owner (“backlog administrator”) works with developers and documents “the requirements.” I consider this one of the worst anti-patterns in Product Management. A typical argument is that combining two roles is "too much work for a single person." That might happen if you spend days attending useless meetings or writing detailed instructions. But if you empower others, prioritize work, and focus on value without BS, things go smoothly. I agree with Marty Cagan, who wrote that to succeed as a Product Manager, you need: - Direct access to users and customers - Direct access to business stakeholders - Direct access to engineers and designer Without proxies. Product Owner included. The only valid setup is that the Product Manager and Product Owner are the same person with the end-to-end responsibility. In particular, it’s essential that the Product Manager, Product Designer, and at least one Engineer perform Product Discovery together. Finally, if you work in Scrum, as PSPO III, I’d like to emphasize that Product Owner is just accountability, and Product Manager is a job title. The Product Owner’s accountability is best fulfilled by an experienced Product Manager. And frankly, it's October 2025. The backlog work can be delegated to AI. Do you agree? Disagree? Let me know in the comments. --- Enjoy this? ♻️ Repost to help PMs avoid this anti-pattern. Want a hi-res PDF of this picture? 📌 Download 50+ high-res PM infographics, like this one, by subscribing here: https://lnkd.in/dkBsZ-ZY

  • Product Owner vs. Product Manager

There. We fixed it for you (again) 😇

  • No alternative text description for this image
Paulina Grodzicka

Product Hive Conferences in Warsaw

1w

I disagree. But it's something that you learn through working experience, not just theory and books. It's also called a reality check. I understand what the perfect world would be and the idea that product teams are empowered, and Product Managers always well seasoned and strong enough to gain respect without formal authority. But I believe that people need to learn and understand the basics first, before they can work around strategies and discovery. There are many talented people, for sure, but let's be honest and look at the market. People learn at their own pace and time, while escalations run daily and technical debt covers a horizon for a better life. There are brave people doing their best, often at hostile corporate environment. I believe that they deserve respect, it doesn't matter what is their job title. Someone has to do the job in those environments and they do it. Don't undermine what they're doing, the fish starts going bad from the head. What needs to be fixed is the board of directors and the company structure, not poor Product Owners. Please write on how to work with the top management on fixing the system.

David Pereira

Running the 100X PM Mastermind: Transforming PMs into Product Leaders | Product Advisor & Speaker | CPO • Hands-On Workshops • d-pereira.com

1w

Interestingly enough, I just read a misleading post that contradicts yours. https://www.linkedin.com/feed/update/urn:li:activity:7378689206342090752/ What disappoints me is the fact that your content is what makes teams more empowered, and therefore, more people should get to know. Yet, the LinkedIn algorithm distributed the other post, which is clearly misleading, a classic misunderstanding. What do you think? Paweł Huryn

Robbin Schuurman

Moving Product Management Forward 🎓| Product Leader | Professional Scrum Trainer | Author | Speaker

1w

You are completely right Paweł Huryn! This has always been the intention behind Professional Scrum too and it has been the way I’ve been teaching Product Managers AND Product Owners for many years. I believe it’s just hard for people and leaders in (large) corporations to imagine that one person can lead a product both strategically and tactically, while leaving many operational responsibilities to an empowered team (and to AI nowadays).

Karol Dulat

Product Design and Product Leader. I help VC-backed startups accelerate their product growth and find market fit by blending product/design/research skills. Both strategic and hands-on. Offshore sailor/racer

1w

Desing industry still debates UX/UI/Product Design so I think this one will take couple more years. In Belgium most of the organisations use them differently than the rest of the world. Especially the big ones, with crazy structures…

Abhishek Shah

PhD | Product Manager | Curious 🤔 | Synergist | Empathetic | Open | Team

1w

Vell written post!! I frequently find myself clarifying/discussing these concepts to/with colleagues and management. Furthermore, the widespread adoption of SAFe, where individuals can become certified Product Owners after minimal training, often leads to a misunderstanding of the role, with a pattern that POs is about focusing solely on backlog management. This situation highlights a broader organizational deficiency in understanding the Product Manager role, resulting in a critical gap in essential training and skill development for personnel.

Abid Quereshi

Scrum Alliance Certified Enterprise Coach, Certified Scrum Trainer and active Software Developer

1w

In the paper that first presented Scrum at OOPSLA in 1995, the original name of Product Owner was Product Manager. Product Owner is a better name for a number of reasons. 1. Management of a Product is a shared responsibility ( Developers also manage the Product) 2. Product Owner indicates authority. A property owner has more authority than a property manager. Unfortunately what I have seen in some organizations is that the traditional Business Analyst just gets rebranded to Product Owner but they don't give them final authority or accountability on decisions that affect the value of the product.

Amy Mitchell

Principal Product Manager @ Dell | Managed Services and Cloud Product Management | Author of Product Management IRL

1w

Agree product manager and product owner needs to be one role and called product manager Paweł Huryn. It's crazy that we still debate this point in 2025!

Shawn Wallack

Follow me for unconventional Agile and AI opinions and insights shared with humor.

1w

Amen.

Andrew Tomin

AI Product Manager @EPAM

1w

Absolutely agree Paweł Huryn, PO is a dead end. I would say even BA title have more value and meaning now. On the other hand for some people PO can a step to PDM role. But the problem is also in the people who hire PO's to manage backlogs instead of the focus on problems and users, researches.

See more comments

To view or add a comment, sign in

Explore content categories