Tell me about a time you had to give a stakeholder news they did not want to hear.
answer
- name the commitment and who cared
- the moment you knew it was at risk
- told them directly, same day
- options plus your recommendation
- reset expectation held, with a number
basics
~10 sTests candor and stakeholder judgment. Tell it early and in one clear sentence, bring two or three options with the one you recommend, and end on a reset expectation that actually held.
how to answer
6 beats- the commitment and who was counting on itOne or two sentences: what had been promised, to whom, and why it mattered to them. Keep setup plus the discovery to roughly fifteen to twenty percent of your airtime.
- the moment you knew it was at riskName the signal and the day. A concrete trigger, a forecast crossing your commitment or a dependency coming back differently, is far stronger than a general sense that things felt tight.
- how and when you delivered itSay the channel, the audience and the interval between knowing and telling. State the headline sentence you actually opened with, before any cause or context, so the interviewer hears that you led with the news.
- the options and your recommendationGive two or three real paths with their costs, then say which one you recommended and why. This beat and the previous one are the heart of the answer and should carry about sixty percent of it.
- the outcome and the expectation you resetWhat they decided, what you then committed to, and whether you hit it, with a number. A revised commitment you met is the proof that the early conversation was worth having.
- what you changed so it surfaces earlier next timeClose with the habit or signal you left behind. Keep the outcome and this reflection together to about a quarter of the answer; two sentences here is plenty.
your answer
5 story prompts- Pick a moment you told someone a date, scope or quality bar was slipping before it actually slipped.
- Write down the exact interval between when you knew and when they knew.
- Choose a story where you offered at least two options and said which one you recommended.
- Have one number ready for the reset commitment and whether you met it.
- This can be the same project as your competing-priorities story, re-angled onto the conversation.
draft and rehearse your own answer in a learn session
go deeper
This probes candor under social pressure and stakeholder management: whether the people depending on you hear about a problem from you, early, or discover it when the date passes. Interviewers also listen for judgment about audience and timing, and for whether you arrive with options and a recommendation instead of handing over a problem. A strong answer leaves both the relationship and a revised commitment intact.
I was the engineer running the rollout of hardware security keys to just over four thousand staff at an enterprise, and our sponsor had told the audit committee that everyone would be enrolled by the end of the quarter. Three weeks in I pulled the enrollment report and saw we were at 58.4 percent, and that the flat part of the curve was almost entirely contractors, whose accounts came from a separate directory our enrollment flow could not read. I did not save it for the weekly report. I asked the sponsor for fifteen minutes that same afternoon and opened with the headline: the all-staff date will not hold for contractors, and here is why. Then I put up three paths. Buy the extra directory connector and take a two-week integration. Run a manual enrollment desk for the contractor population. Or split the milestone and commit only to employees this quarter. I recommended the split, because it protected the date for the group the auditors had actually asked about and avoided manual work we would have to redo anyway. He took the split and told the committee himself the next morning, which mattered, because the news reached them from him rather than from a date going past. Employees closed at 96.2 percent on time and contractors finished six weeks later. Afterwards I started sending the enrollment curve broken out by population every Monday, so a stall showed up as a number instead of a surprise.
The signal here is timing plus a recommendation: the sponsor hears it the same afternoon, gets three real paths with their costs, and hears which one you would pick and why. The weekly curve at the end turns a one-off save into a habit. Drop the recommendation and this becomes problem-handing, which downlevels it immediately.
I owned identity engineering for an enterprise with eleven business units, and we were moving everyone off push-approval MFA onto phishing-resistant methods after our own red team walked straight through a push-fatigue test. Two of those units had audit commitments that assumed the old method stayed available through their cutover window. The migration was going to push their enrollment share down before it came back up, and I knew that during planning rather than after. I put the two business-unit leads and our security leadership in the same room deliberately, because I did not want either side hearing a softened version from me separately. I said plainly that they would sit below their audit floor for roughly five weeks, showed the red team finding, and gave two paths. Hold the old method for those units and carry a known phishing exposure through the audit. Or move now, take the dip, and let me write the compensating-control memo their auditors would want. I recommended moving, and I named the cost to them out loud: uncomfortable questions in an audit meeting, which I offered to attend alongside them. They chose to move. Enrollment share dropped from 91.3 to 84.7 percent, passed its old level within five weeks, and neither unit missed its audit. Since then the program brief carries a standing section listing whose commitments a given change would break, so we know whose calendar we are touching before anything gets scheduled.
Senior scope shows in the audience design, both sides in one room with no separately softened version, and in naming the cost of your own recommendation aloud rather than selling it. The standing section mapping changes to other people's commitments is the mechanism; without it this reads as a well-handled one-off.
At your level the stakeholder is usually your lead or a peer team. Show that you spoke up the day your own picture changed, and that you said what you needed from them rather than only that you were behind.
Expect the news to touch someone outside your team: another team's lead, a support function, a customer contact. The bar is options here, two or three real paths with the one you would take and its tradeoff named out loud.
You are usually the person the commitment came from, not just the one who spotted the problem. Show a deliberate choice of audience and timing, and a signal you put in place afterwards so that class of surprise cannot build up quietly again.
Your scope is programs and other leaders' calendars. Describe how bad news travels by default in the org you shaped, what forecasting and escalation norms you set, so the story reads as one instance of a mechanism rather than a personal save.
saying these in an interview costs you the question
- Burying the news in a long status update nobody reads
- Waiting until the date passed before saying anything
- Bringing the problem with no options and no recommendation
- Blaming another team or a vendor for the whole situation
- Softening it so much the stakeholder leaves thinking everything is fine
- No evidence the revised commitment was one you actually met
- How long was it between you knowing and them knowing?Answer with a real interval and the reason for it. Hours or a day reads as candor; a week reads as hoping the problem would solve itself. If you did wait to confirm something first, say what you were confirming and why that confirmation changed the message rather than just delaying it.
- What did they push back on?Interviewers want a real reaction, not gratitude. Name the objection, whether it was the date, the cost or your read of the risk, and how you handled it without either caving or arguing. Showing that you adjusted the plan when their information was better than yours is a strength, not a retreat.
- Would you have delivered that differently to a customer than to your own leadership?Say yes and explain the difference. External audiences usually need the impact on them, the new commitment and what you are doing about it, with less internal cause detail; internal leadership needs the cause and the tradeoffs so they can decide. Mention who you would align with internally before an external message goes out.
## The prompt family This one arrives in many wordings: - tell me about a time you had to deliver bad news; - how did you tell a customer their date was moving; - describe a time you had to disappoint a stakeholder; - tell me about an unpopular message you had to carry. They are one question. The interviewer is not testing whether you have had bad news to deliver, everyone has, but whether the people depending on you hear it **from you, early, in a form they can act on**. ## The failure mode being screened for Engineers rarely fail this question by delivering the news badly in the room. They fail it by **having waited**: the answer opens with weeks of quiet effort to rescue the situation, and the stakeholder appears only once the situation is unrecoverable. That is a heroism story wearing a communication story's clothes, and experienced interviewers hear the gap immediately. If your story has that gap, name it and say what your trigger is now, rather than hoping nobody counts the days. ## Weak versus strong on the same facts - **Weak:** I realised we might not make it, I worked hard to catch up, eventually I let my manager know, and we moved the date. - **Strong:** on the day my forecast stopped agreeing with the commitment, I asked the sponsor for fifteen minutes, opened with the headline in one sentence, gave three options with the cost of each, recommended one, and left with a decision. Same events, but the second version has a **trigger**, an **audience choice**, a **structure** and a **decision**, which are the four things being scored. ## Evidence that lands - The interval between knowing and telling. - The seniority and the side of the house of the person you told, since telling a peer is not the same as telling the person who made the promise. - The number of options you brought and whether you had a recommendation. - Whether the tradeoff was named out loud, including a cost to you. - Whether the revised commitment held, with a figure. - And, at higher levels, the standing mechanism you left behind so the next stall shows up as a number rather than as an apology. ## Structure and airtime - **Setup** deserves fifteen to twenty percent, and it needs only the commitment, who was counting on it, and how you found out. - **The bulk**, around sixty percent, belongs to the delivery itself: when, to whom, in what channel, what you actually said first, and what you put on the table. - **The last quarter** is the outcome and the reflection. The commonest structural failure is the reverse, a two-minute setup explaining every technical cause and a ten-second landing. ## How the bar moves - **A junior answer** is credible if it shows the reflex, speak when your estimate moves, and a specific ask. - **A middle answer** needs options and a stakeholder outside the immediate team. - **A senior answer** needs deliberate audience design, the news arriving before the date does, and a prevention signal. - **A principal answer** is about the norms, whether bad news in that organisation travels without requiring courage from the person carrying it. ## One caution Do not choose a story where the bad news was somebody else's fault and you were merely the messenger. It reads as neutral at best. Pick the one where the commitment was yours.