leading through change: how to tell your team what nobody wants to hear

Why bad news goes wrong

A founder in Kochi runs a 20-person digital agency. A large client has paid two months late, and this month's salaries will be delayed by ten days. He has known for a week. He has told nobody, and the team has already noticed that he looks worried.

An engineering manager in Bengaluru learns on a Friday that her team of nine will be split across two other groups. She opens the Monday call with ten minutes of slides about "exciting new synergies" before anyone understands what is actually happening.

An account director in Dubai loses the agency's biggest retainer. She tells the team, "Nothing will change, don't worry." Three weeks later, two contracts are not renewed.

The pattern is the same. Leaders delay because they want to have all the answers first. They soften because they want to protect people. They reassure because silence feels cruel. Each of these is kind in intention and costly in effect. While you wait, people fill the gap with rumour, and rumour is almost always worse than the truth.

The three-part shape: known, not known, next

Almost every difficult announcement can be built from three short parts.

• What we know. The facts, in plain words, with the hard part in the first or second sentence.
• What we do not know yet. Be honest about the gaps. Uncertainty spoken aloud is easier to bear than uncertainty discovered later.
• What happens next. A concrete step and a date. People can tolerate a lot if they know when they will hear more.

Here is the Kochi founder, using it with his team on a Monday morning call:

"I need to tell you something difficult, and I want you to hear it from me directly. This month's salaries will be paid on the 10th, not the 1st. A client owes us a large payment that is two months late. That's the reason, and it's not about anyone's work."

"What I don't know yet is whether the payment arrives this week or next. What I do know is that I've arranged a short-term loan so that the 10th is a firm date, not a hope."

"Next: I'll send you a written note today. If the 10th causes you a real problem with rent or an EMI, message me privately and we'll work something out. I'll update all of you on Friday, whatever happens."

Notice what is missing: no long history of the client relationship, no "as you all know, times are tough", no promise he cannot keep.

Say the hard part first

The instinct is to warm up: context, gratitude, the market. But while you warm up, people are scanning your face and imagining the worst. Give them the headline in the first minute. Context can come after, when they are ready to hear it.

The Bengaluru manager's second attempt sounded like this:

"From the 1st of next month, our team will be split. Five of you will join the platform group, four will join payments. Nobody is losing their job. I'll tell you exactly who is going where in a minute, and then I want to hear your questions."

Thirty seconds, and the room can breathe.

Handling the questions

Questions after bad news are rarely calm. Some will be sharp. Some will be personal. A few habits help.

• Take every question, even the angry ones. A hard question asked in the room is better than ten asked in the corridor.
• Say "I don't know" when you don't. Then add when you will know. "I don't know yet. I'll have an answer by Thursday."
• Name the feeling before the fact. "I can hear this is frustrating. Here's what I can tell you."
• Do not argue with someone's reaction. "You shouldn't feel that way" closes the conversation. "That makes sense" keeps it open.
• Offer a private channel. Some people will never ask the real question in front of colleagues.

When someone asks the question you dread, "Is this going to happen again?", resist both false comfort and gloom:

"I can't promise it won't. I can promise that if it does, you'll hear it from me early, the way you did today."

Say it again, and then again

One announcement is never enough. People in shock hear about half of what you say. Some were on leave. Some were on a bad connection from Thrissur. Some will replay a single phrase all evening and forget the rest.

So repeat the message, in the same words, across channels:

• The same day, in writing. A short note with the three parts. No new information, no softer version.
• In one-to-ones. Ask each person, "What's the question you didn't want to ask in the group?"
• To other leaders. If your team leads describe the change differently, the team will notice. Give them your exact words.

Repetition can feel awkward to the person repeating. To the person listening, it feels like stability.

The second conversation, a week later

This is the step most leaders skip, and it matters most. A week after the announcement, the shock has settled and the real questions have surfaced. Go back to the team and do three things: report what has changed since, answer what you promised to answer, and ask what you missed.

"Last Monday I told you salaries would be paid on the 10th. The client paid on Thursday, so they'll go out on the 8th. I said I'd find out about the March projects too. Here's what I know. What have you been wondering about this week that I haven't addressed?"

That last question often brings out the worry that was never spoken: a team member planning a wedding, someone quietly applying elsewhere, a misunderstanding that started in a family WhatsApp group. The second conversation is where trust is rebuilt.

In a second language, and under pressure

Bad news is one of the hardest things to say in a language that is not your first, because stress shortens sentences and speeds up speech. Write the first three sentences in full. Read them aloud twice before the call. Slow down on numbers and dates, and pause after each one. If the team is mixed, a few words in a shared language can help, but keep the key facts in one language so the written note matches what people heard.

Published by The Full Stop, the journal of Brightside English. Reviewed by a Brightside senior coach. Corrections: see our editorial standard.