Product Owner Availability as a Critical Impediment

Definition

The Problem With Proxies: when a product owner cannot be reached during a sprint, teams do not solve the problem by appointing a proxy to make decisions on the PO's behalf. Proxies reduce uncertainty but fail to address the root cause. Even trusted proxies misunderstand what the real product owner wants. The deeper issue is organizational—the product owner is overloaded or deprioritized—and the solution is to address that, not to layer indirection.

A good ScrumMaster ensures the team has access to a product owner (including a proxy). A great one ensures the team has access to the product owner. Only true product owners should be the interface between the team and customer needs.

In the Book

Watts shares the story of the Oscars team and their product owner Phillip. Phillip worked on many pieces of work and made the team take a requirements document as gospel. When the team built a feature exactly to spec but Phillip rejected it at sprint review—"That's not what I meant"—the cost became visible: rework, rolled-back features, lost velocity.

The team suggested a proxy solution. Frank, the ScrumMaster, initially accepted it. But at the next retrospective, Frank came prepared with a breakdown of the cost: wasted effort on misunderstandings, rework, time spent waiting for decisions. He multiplied the hours by the daily cost of the development team. The business case for freeing Phillip's time became irrefutable.

Frank and Phillip then went to management with two options: keep using a proxy (band-aid), or free up Phillip's time by hiring someone to handle the work Phillip could delegate—testing, backlog management, stakeholder herding—leaving Phillip free to interact with the team during the sprint.

The second approach worked. As Phillip worked closer with the team, they began to create what he actually wanted. More importantly, Phillip and the team liked and trusted each other, which fostered creative solutions neither could have produced alone.

Watts is clear: great ScrumMasters avoid sticking plasters. They work to resolve the real issue. Showcasing the true costs of features that have to be rolled back because the team didn't understand all requirements can help a product owner justify dedicating time to the team during the sprint.

Why It Matters

Proxy solutions feel pragmatic but they're systemic failures in disguise. They trade a visible problem (unavailable PO) for a hidden cost (cascading misunderstandings). The framework-agnostic insight: when a critical information source is unavailable, handoffs and proxies compound the problem rather than solve it. The remedy is to quantify the cost and work upstream to unblock the source, not to add another layer of intermediary.