Delivering Bad News to a Team or Stakeholders Without Losing Trust
GongSoftware Engineer · OtherLast updated
A behavioral interview question about a time you had to deliver bad news such as a missed deadline, a serious defect or an unpopular decision. It tests timing, choosing the right audience, delivering facts with options and a recommendation, owning the problem without blame, and following through afterward.
Describe a time you had to deliver bad news, such as a missed deadline, a serious defect, a cancelled project, or a decision people would dislike. Explain who needed to hear it, how you prepared, how and when you delivered it, and what happened afterward.
Clarifying Questions
- Should the news be bad for my own team, for a stakeholder or for a customer, or does any of those work?
- Do you want a case where I was responsible for the problem, or one where I only had to communicate it?
Hints
Hint 1
Timing is part of the story: Be ready to say when you first knew and how long it took you to tell the people affected.
Hint 2
Bring a path forward: Think about what the listener needs besides the news itself in order to make a decision or move on.
Follow-up questions
- How did the recipient react, and how did you handle that reaction?
- What would have happened if you had waited another week to say it?
- How would you deliver the same news to an executive versus to your own team?
- Tell me about a time you delivered bad news badly.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.