When leaders do not know how a consequential change will affect their teams, silence can feel responsible. You do not want to speculate, create unnecessary anxiety, or promise something you cannot deliver.
But silence still communicates.
A manager forwards an announcement about an AI pilot, holds one conversation with the team, and then lets the subject drop. Two employees raise concerns about job security. The manager has no reliable answers, so they wait until there is something concrete to share.
The intention may be caution. From the team’s side, the silence leaves a different question hanging: Are we going to be included in this conversation, or are we on our own?
That does not mean every leader should schedule another vague check-in or turn uncertainty into a running discussion. Repeating “we don’t know yet” without saying what is unknown, or when anything might change, can make anxiety worse. And you may have little authority over the decisions people are worried about.
You cannot give people certainty you do not have. You can tell them where your certainty ends.
Say what you know. Say what you do not know. If you are waiting for a decision or information, name it. Then say when you will return to the question—even if the update is that there is still no update.
Make room for the concern without rushing to solve it. If someone says they are worried about their role, a fast “your skills still matter” may sound reassuring to you. It may sound like you are trying to close the conversation before hearing what they mean.
Ask what feels most uncertain. Listen before you answer.
This is uncomfortable because a leader is often expected to bring clarity. When you cannot, it is tempting to wait until you can show up with a plan. That protects you from the awkwardness of saying, “I don’t know.” It also makes your team carry the uncertainty without knowing whether you are willing to face it with them.
I understand the appeal of waiting. No one wants to make a difficult moment harder with speculation. But caution and avoidance can look very similar from the outside. Your team cannot know which one is driving your silence.
You do not have to manufacture an AI strategy or stage a conversation people do not want. You do have to be honest about the questions that remain, and make it possible for people to raise what is at stake for them.
At your next team conversation, be specific: “I don’t know yet how this will change our work. I’m waiting on ____. I expect to know more by ____, and I’ll update you then. In the meantime, what concerns or questions should we make sure aren’t getting lost?”
Then keep the commitment to return.
You may still have no answer. But your team will know whether you are willing to stay in the conversation while you look for one.
