A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.
How to answer
Two words carry this question: “quietly” and “before”. This is not the person who argues in meetings; it is the one who agrees in the room and then doesn’t deliver. And the question asks what you did before escalating, so most of your answer belongs there.
Build it in five steps, and give the third the most time:
- The signal, as behavior. What you saw, not what you assumed: “The data extract we agreed on at kickoff kept slipping, and each time the reason was new.” Leave motive out of this sentence.
- Their incentive. What your project cost them: a report your system replaced, a budget it moved, a number it exposed. Say how you found out, whether from a one-on-one, a question to someone who knew them, or the org chart.
- The direct move. A private conversation that names the pattern without accusing, and an offer aimed at the incentive: credit, a role in the rollout, or a change of scope. End it with a date you both commit to, and say what you will do if it passes: “If we miss Friday, I’ll take this plan to the sponsor, and I’ll tell you before I do.”
- The escalation, if it came. That you told the stakeholder first, who you went to, and the proposal you brought, framed as a decision for the sponsor rather than a complaint.
- Where it ended. The project, and the relationship.
Say the incentive as one plain sentence: “His team’s weekly backlog report was how the VP saw their work, and our dashboard replaced it.” That line shows you looked for a reason before assuming bad faith.
Hold back how sure you were about the incentive and how the stakeholder took the escalation. Both are likely follow-ups, and a first answer that pre-empts them runs long.
The first trap is the villain story. If the stakeholder has no reason in your telling, you sound like someone who escalates when people disagree. The second is escalating with only a problem: the sponsor has to solve it, and you have spent their attention on something you could have framed as a choice.
Follow-ups
What the interviewer may ask next, once your first answer is on the table.
- How did you find out what they stood to lose, and how sure were you?
- What would you have done if the direct conversation had changed nothing?
- How did the stakeholder react when they learned you had gone to the sponsor?
Where answers go wrong
- Tells a villain story in which the stakeholder has no reason for resisting, which makes the speaker sound like someone who escalates whenever people disagree.
- Escalates with a complaint instead of a proposal, handing the sponsor a problem to solve.
Answer this in two minutes
Write the answer you would say out loud. The clock starts with your first word.
Compare with the model answer
Illustrative answer about a fictional project
Written in the first person to show the structure. Tell yours from your own work.
I was deploying claims triage for a property insurer, sponsored by its COO. We needed a nightly extract from Marcus’s claims reporting team. Agreed for week two, it had slipped three times by week four, each time for a new reason, though Marcus was friendly in every meeting.
I asked the claims operations lead what Marcus’s team produced: a hand-built backlog report the VP of claims read every Monday, which our dashboard would replace.
So I asked Marcus for a one-on-one and said: “The extract has moved three times, each for a different reason, and I’d rather ask the bigger question than plan a fourth date. This dashboard covers ground your Monday report covers today. What would it need to look like for your team to come out ahead?” He paused, then said the Monday report was the only time the VP saw his team’s work.
I offered his team ownership of the triage definitions and a weekly accuracy review, work we needed, with their name on the dashboard. He liked it. We agreed the extract would ship on the 14th, and that if it slipped I’d take the plan to the COO.
The 14th passed with no extract. When I asked, Marcus said the review hours would come out of his VP’s budget, and he couldn’t approve that alone, so he’d been waiting on a yes that wasn’t his to give. That afternoon I told him: “The 14th has passed, so I’m taking the plan to the COO today. It asks her to approve your team’s role, not to push you, and I’d like you in the room.” I brought the COO a one-page plan asking her to approve Marcus’s team owning the triage definitions and the weekly accuracy review, with the review hours funded and the extract date written into it. Marcus came, and walked her through the part his team would own. She approved it; the extract arrived four days later.
Time to first contact on claims fell from 3.2 days to 1.1, and Marcus asked for his team to join the insurer’s next project.
If they ask how Marcus took the escalation: “He was relieved more than annoyed, because I’d told him first and the plan gave his team the credit. He presented the accuracy review at the next steering meeting himself.”
What I do differently now: “On every project since, I ask in week one whose report or number our system replaces, and I talk to that person before kickoff, not after the first slip.”