How do you handle an unavailable Product Owner?
Tests your ability to solve process bottlenecks collaboratively. A great answer starts with data, then direct communication with the PO, proposes solutions like office hours, and escalates only as a last resort.
What's really being asked
This question tests your ability to proactively diagnose and solve process problems beyond your immediate coding tasks. It assesses your leadership, communication skills, and understanding of Agile principles. Interviewers want to see if you take ownership of the team's overall success and can navigate interpersonal challenges constructively, rather than just complaining or blaming.
The full answer
A strong answer outlines a measured, multi-step approach. First, you gather objective data. This means tracking the number of blocked tickets, the hours lost per sprint, and specific examples where a lack of clarity caused rework. Second, you initiate a direct, private conversation with the Product Owner, presenting the data not as an accusation, but as a shared problem to solve. Third, you collaboratively propose concrete solutions, such as establishing daily 30-minute 'PO Office Hours', designating a proxy for tactical questions, or improving story readiness criteria. Fourth, you explicitly mention involving the Scrum Master, whose job is to remove impediments. Finally, you state that escalation to management is a last resort, only to be used if sprint goals are consistently missed and all other avenues have been exhausted.
The mistakes people make
A major red flag is suggesting an immediate escalation to the PO's manager or your own. This shows poor conflict resolution skills. Another common mistake is suggesting the engineering team should just make product decisions on their own; this usurps the PO's role and introduces significant business risk. Simply blaming the PO in the sprint retrospective without having tried to solve the problem during the sprint is a passive-aggressive approach that signals a lack of leadership. Finally, saying you would do nothing and just wait is a sign of a junior, passive mindset.
What usually comes next
Be prepared for follow-ups like: "What if the Product Owner becomes defensive when you present the data?" or "What if your company doesn't have a Scrum Master?" or "At what specific point do you decide it's time to escalate? What metric would trigger that?"
A concrete example
"On a previous project, our PO was stretched thin, and we calculated we were losing about 15% of our sprint capacity to blocked stories. I brought this data to our Scrum Master, and together we met with the PO. We proposed a new system: we'd batch non-urgent questions in a shared doc for async answers, and we scheduled two 45-minute protected 'PO Sync' blocks on the calendar each week for urgent clarifications. This reduced our blocked time to under 5% within two sprints and made the PO feel more in control."
Interview question
When a Product Owner's unavailability consistently impedes the development team's progress, what is the recommended first course of action?
- a.Document specific instances of blocked work and lost time, then initiate a private discussion with the Product Owner.Correct
- b.Immediately inform the Product Owner's manager about the performance issue.
- c.The development team should proceed with their best judgment on product decisions to unblock themselves.
- d.Raise the issue during the next sprint retrospective as a team impediment to be addressed by the Scrum Master.
Why? this is the answer
The recommended first step is to gather objective data on the impact of the PO's unavailability, then engage in a direct, private conversation with the PO to collaboratively find solutions. Immediate escalation or the team making product decisions are premature and can be counterproductive, while waiting for the retrospective is a delayed and less proactive approach.
Just read this? Test yourself on what you have been reading.
- #agile
- #scrum
- #communication
- #problem-solving
- #leadership
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles