Tell me about a time when you had to deliver bad news to a team or a stakeholder.

Illustrative answer

This is a fictional example of delivering a missed-commitment update.

I coordinated a customer integration whose required validation was taking longer than our plan allowed. Once the evidence showed the agreed delivery date was no longer credible, I needed to tell the customer. I confirmed the known facts with the technical owner but did not wait for every uncertainty to disappear.

I opened the conversation directly: we would miss the agreed date, and I was sorry for the disruption. I explained the specific validation still outstanding, what the customer could and could not use, and which estimate remained uncertain. I took responsibility for our earlier planning assumption without sharing private personnel details or blaming a teammate.

I asked which customer commitments depended on the integration. We discussed a verified partial option and a later full delivery, with the limitations and approval needed for each. I promised a specific next update rather than a completion date the team could not support.

The customer chose to postpone its rollout. I sent a written record of that decision and followed through on the updates, including one update where the uncertainty had not yet been resolved. The later accepted delivery did not erase the inconvenience. I learned that a useful difficult conversation states the consequence early, makes room for the other person's needs and follows disclosure with dependable action.

Follow-up to practice

How would you respond if the recipient was angry or demanded certainty you did not have?