Implementing Scrum · Case Studies · Podcast Episode·September 28, 2025·4 min read

Your Product Owner is MIA? It's Costing More Than You Think.

The 'Weekend at Bernie's' Product Owner problem: propped up in meetings but providing no real direction. Four counter-intuitive strategies for tackling this expensive organizational problem.

Introduction: The “Weekend at Bernie’s” Problem

We’ve all been there (if not, you may encounter this in your not-so-distant future). The sprint is underway, but the one person accountable for maximizing the value of the product is present in name only — the “Weekend at Bernie’s” Product Owner, propped up in meetings but providing no real direction or decisions.

Scrum Masters and Developers are left starved of direction, feeling like they’re going through the motions but not getting anywhere useful. This isn’t just frustrating — it’s an expensive organizational problem. Four counter-intuitive strategies for tackling this silent drain on your company’s bottom line:

Takeaway 1: Stop Arguing About Rules. Start Talking About Risk.

When faced with an absent Product Owner, the first instinct is to point to the Scrum Guide. This is almost always ineffective — Scrum isn’t a prescriptive solution, it’s a lightweight framework for navigating complexity using empiricism, resting on three pillars: transparency, inspection, and adaptation.

An absent PO shatters the first pillar. When backlog items are vague, unordered, and disconnected from market value, you have critically low transparency — which guarantees failure at inspection (unusable increments, wasted sprint time, rework from guesswork) and adaptation (you can’t adapt the organization’s focus without clear insights).

The problem isn’t that the PO is breaking a rule — it’s that their absence breaks your team’s fundamental ability to learn and adapt. Shift the conversation from process compliance to quantifiable business risk. A typical development team of 6-8 people can represent an organizational investment of around $80,000 for a single two-week sprint. When that team is blocked for two full days waiting on clarification, that’s 16 person-days of lost productivity — roughly a $10,000 loss. You’re not arguing about “doing Scrum right” anymore; you’re protecting the organization’s investment.

Takeaway 2: Don’t Wait for the “Unicorn.” Fight for the Essentials.

The ideal Product Owner is often called a “Unicorn” because they’re incredibly rare, needing three non-negotiable attributes:

• Available — to provide continuous feedback and communication.
• Knowledgeable — deeply understanding the customer’s problems, not just requested features.
• Authoritative — genuine power to make backlog decisions, including saying “no.”

Across thousands of teams, I’ve seen maybe two or three people like that. You cannot wait for the perfect combination — instead, relentlessly fight for Authority and Availability. Authority prevents the team from wasting entire sprints building the wrong things due to committee-driven decisions. Availability prevents the team from being blocked while trying to build the right things.

Takeaway 3: Your Most Powerful Tool Isn’t a Meeting — It’s a Conversation.

A Scrum Master’s most powerful tool here isn’t a formal event but an ongoing activity: Product Backlog Refinement — the continuous process of adding detail, estimates, and order to backlog items, where developers and the Product Owner collaborate so work is understood before it’s brought into a sprint.

When a PO consistently skips refinement, they create a hellish situation for developers — the direct cost materializes in long, painful Sprint Planning sessions, where the team wastes half the meeting just trying to define what the work even is. The PO’s disengagement stops being a vague complaint and becomes a visible, immediate bottleneck burning through the sprint budget before work even starts.

Takeaway 4: The Product Owner Must Be a Storyteller, Not a Clerk.

A great Product Owner is far more than a requirements gatherer — they’re a storyteller. This connects to Simon Sinek’s “Golden Circle”: people don’t buy what you do, they buy why you do it. The PO’s primary storytelling duty is connecting the team’s work (the “what”) to the larger Product Goal (the “why”).

When the PO is absent from critical conversations like refinement, this connection breaks. The team builds features without a deep understanding of the customer problem — almost inevitably delivering lower-value increments, operating on assumptions rather than shared understanding.

Conclusion: From Process Police to Value Advocate

The most effective way to solve the absent Product Owner problem is to shift your own role — stop being a process enforcer, become a value advocate. This embodies the true spirit of the Scrum Master as a “leader who serves,” leading through influence, not direct power. Your greatest influence comes from making the business impact of the PO’s absence transparent through data — focusing on risk and wasted investment, not rules.

What Next?

What’s one small change you can make tomorrow to make the true cost of an unavailable Product Owner visible to your organization? Let me know via LinkedIn.

Need some real-world assistance? Contact me today.

Full disclosure: this article was created using NotebookLM, an AI tool by Google, based on my own curated sources about Implementing Scrum in the real world. Content has been carefully reviewed for accuracy. Opinions and insights shared are my own.