In our recent Advanced Product Owner course, the homework for the week was to take a stakeholder request and turn it into a situational interview. Participants practiced starting with questions like, “When you needed this capability, what was going on?” and then using follow-up questions to understand the problem underneath the request.
One participant picked a request from a particularly upset stakeholder. He had submitted a ticket asking for an urgent change, and the language was unusually terse and demanding. When they met, she started to use the situational question from class, which lowered the temperature enough for her to see what was really at stake. There was an audit finding involved. Leadership was asking questions. He wanted to move quickly.
And as they explored the situation, it became clear to both of them that the problem was not actually in the tool. It was a process interpretation issue that had built up over time through manual workarounds. The audit finding turned up the pressure, and under that kind of pressure people often point at the most visible thing. In this case, a system fix would have taken time and still left the actual risk in place. What they needed was training so people could follow the process well enough to stop creating the workarounds.
That shift happened because she did not start by arguing with his solution or rushing to accommodate it. She started by asking what had been happening. If she had taken the request at face value, her team could easily have burned a sprint solving the wrong problem.
There was more to this, though. When she brought the story back to class, everyone was excited about the better outcome, of course. But what really got our attention was what happened to the relationship.
Pressure changes the conversation
When a stakeholder shows up stressed and already attached to a solution, the conversation can start to feel like an argument. They are pushing for their answer. You are trying to figure out whether that answer makes sense, whether it is feasible, and whether there is a better way to handle it. Even when everyone stays polite, the conversation can turn into a quiet tug of war.
Good questions interrupt that. Instead of debating solutions too early, they move the conversation back toward the situation itself. What happened? What did you notice? What have you tried? What is making this feel urgent now?
That shift matters, not because it is a clever technique, but because it helps both people get out of advocacy mode long enough to look at the same reality. Roger Schwarz calls that mutual curiosity.
In her case, the questions did more than clarify the problem. They also helped her see the pressure this stakeholder was under. He was dealing with leadership scrutiny, an audit finding, and a problem his team had likely been compensating for for a long time. She left with a much better sense of what he was carrying, not just what he had asked for.
There’s usually more going on than the stated request
This pattern applies well beyond Product Owners.
When someone brings you a tense request, they are rarely bringing only the request. They are also carrying concern about how the problem reflects on them, what it means for their team, and how exposed they may feel if it is not handled well. They do not usually say that part out loud, but it still shapes the conversation.
It affects how urgent they sound, how flexible they are, and how quickly they latch onto a preferred solution. It also affects whether the request comes back again next week in a slightly different form.
When you ask about the situation instead of jumping straight to the fix, you are more likely to get to the source of the pressure. That changes what you recommend, what gets built, and often keeps the team from spending time on work that was never going to solve the real problem.
What the class noticed
When this participant told her story, what stood out was not just that she got to a better answer. It was that a conversation that could have turned into another stressful round of solution-pushing ended up giving both people a clearer view of the problem.
He felt heard at a moment when he was under real pressure. She left with more empathy for his situation and a better understanding of what needed to happen next.
The hardest stakeholder conversations, handled well, often do the most to improve the relationship. Not because they go smoothly, or feel comfortable, or because everything gets resolved in the room, but because someone takes the time to sort out what is actually going on before the team charges ahead.
We teach effective techniques for mapping stakeholders and creating a system to stay in touch at the right times. That is an important starting point. It helps you remember who matters, who needs to stay informed, and where attention is needed. But it will not do the most important part for you. That part happens in the conversation itself.
We cover situational interviewing and stakeholder work in our Advanced Product Owner program. It is useful for Product Owners, managers, coaches, and leaders who work closely with them. Sign up to learn how to apply for the next cohort!
Last updated