Two titles, one product, and a gap in accountability that's quietly costing you more than you think.

In this solo episode, Yuval Yeret tackles one of the most common structural problems in product organizations: the split between product manager and product owner that creates ambiguity instead of clarity. Drawing on client patterns across hardware, software, and platform organizations, Yuval unpacks the misunderstanding at the root of this confusion — and makes the case that product ownership is an accountability, not a workload. The result is a practical framework for knowing when one role is enough, when splitting genuinely makes sense, and how to tell the difference.

• Accountability vs. workload: Product ownership means being accountable for the value the team creates — not writing every story or attending every standup. Confusing the two leads to a split that solves the wrong problem.
• The proxy problem: When someone gets the product owner title but not real decision-making authority, you've created a proxy. Proxies manage queues. Teams that work with proxies quickly learn the real decisions happen somewhere else.
• The no test: Can the person who's supposed to own your product say no to a feature request without escalating? If not, the structure isn't supporting the accountability.

"Product ownership doesn't mean doing all the inbound work yourself. It means being accountable for the value the team creates. Owning the outcome."

"When you split the role and give someone the product owner title but not the real decision-making authority — when they're essentially relaying direction from the product manager to the team — you've created a proxy. Someone who manages a queue rather than owns a product."

"Teams pick up on this pretty quickly. They learn that the real decisions happen somewhere else. So they start going around the product owner, escalating directly, or just making calls themselves and hoping it works out."

If you're not sure whether your product org is set up to make real product decisions or just manage requests, that ambiguity is worth resolving.

Experiment to try this week: Ask your product owner (or product manager) to say no to the next non-critical feature request that comes in — without checking with anyone first. Watch what happens. The reaction will tell you whether the authority matches the title.

Yuval Yeret helps leaders maximize outcomes through strategic, nuanced agility. As both a SAFe Fellow/SPCT and Professional Scrum Trainer, Yuval is frequently brought in to help organizations evolve from agile theater and feature factories toward product-oriented agility — building on existing investments rather than starting over.

📩 Start here: Scaling w/ Agility Crash Course — a free email course to help you scale without falling into the process theater trap.

🔗 Follow Yuval on LinkedIn: linkedin.com/in/yuvalyeret