What to say when you don’t have the answers yet

← Playbook

ISSUE

15

·

What to say when you don’t have the answers yet

EXECUTIVE OVERVIEW

Skip to the full story ↓

THE SITUATION

A reorganization has been announced, the details are not settled, and your team is waiting for you to say something. Silence reads as bad news. Guessing reads as a promise.

THE CALL

Say what you know, what you don’t, and when you will know more.

SAY THIS

“Here is what I know today. Here is what I don’t know yet. I will update you on Thursday, even if the update is that nothing has changed.”

AVOID

Guessing at outcomes Going quiet until it is final Promising what isn’t yours

TRY THIS WEEK

Write down three things you know and three you don’t. Pick the date of your next update and put it on the calendar. Hold one conversation with the person most affected.

THE FULL STORY ·

9

MIN

Picture the morning after the announcement. The email went out at four the previous afternoon. It said a reorganization was coming, that leadership was working through the details, and that more would follow. By nine, your team has read it a dozen times.

Nobody has asked you a direct question yet. That is the first sign something is wrong. People do not stop wondering when the room goes quiet. They start asking each other.

Why silence feels like an answer

When a leader says nothing, the team does not hear nothing. They hear one of two things: that you know and cannot say, or that you do not know and are worried too. Both are uncomfortable, and neither is true. The honest position is usually in the middle. You know some things, you do not know others, and some of what you know you have been asked to hold back for now.

The instinct to wait until the picture is complete is a good one for a decision and a poor one for a conversation. A decision benefits from complete information. A team benefits from hearing, early and plainly, where things stand.

The three-part update

Every update during a period of change can use the same three parts. Keep them in the same order each time so people learn the shape of it.

1 · WHAT I KNOW

Facts only. A date, a decision that has been made, a decision that has not. Short sentences.

2 · WHAT I DON’T KNOW

Name the open questions out loud. If people are already asking them, say so. It lowers the temperature more than any reassurance.

3 · WHEN YOU’LL HEAR MORE

A specific day, not “soon.” Commit to the update even if the update is that nothing has changed.

A promised update that says “no news” builds more trust than a surprise announcement that says a lot.

The questions you will be asked

Sooner or later someone will ask the question underneath all the others: is my job safe? If you do not know, say that. If you know it is not yours to answer, say that too. What you cannot do is offer comfort you cannot back up.

A workable reply sounds like this: “I don’t know yet, and I won’t guess. What I can tell you is when I expect to know, and that you will hear it from me before you hear it anywhere else.” Then keep that promise.

Other questions are easier. Who decides? When? What happens to the project we were in the middle of? These have answers, or at least owners. Find them and bring them back.

Keep the cadence

The first update gets the attention. The fourth one decides whether the team believes you. Pick a rhythm you can sustain, weekly is usually enough, and hold it even when there is nothing new. A five-minute check-in with the same three parts costs you little and tells the team the channel is open.

It also gives you somewhere to put the rumors. Ask at the end of each update what people are hearing. You will learn more from that answer than from any status report.

When the answer arrives

At some point the details will be settled, and some of them will be hard to hear. The work you did earlier pays off here. A team that has been told the truth in small pieces can take a hard piece. A team that has been told nothing takes it as proof of what they feared.

Deliver the hard part directly, in person where you can, and give people time to react before you move on to the plan. Then return to the three parts: what is decided, what is still open, and when you will talk again.

The short version

You do not need the answers to lead through uncertainty. You need a pattern people can rely on: here is what I know, here is what I don’t, here is when you’ll hear more. Say it early, say it the same way each time, and keep the date.

On my shelf

Switch: How to Change Things When Change Is Hard

Chip Heath and Dan Heath

Switch: How to Change Things When Change Is Hard

Chip Heath and Dan Heath

A practical look at why change stalls even when people agree it is needed, and what makes it stick. It pairs with this issue because people follow a clear next step more readily than a big announcement.

Some book links are affiliate links. I may earn a small commission if you buy, at no cost to you.

Written by Casey Sisterson, who leads technology operations and platform services for a manufacturing organization. More about me