When your team stops asking questions about an AI rollout, it is tempting to call that acceptance.
It may be. It may also mean the change feels irrelevant, the meeting feels performative, or people have decided the decision is already made. Silence alone cannot tell you which.
But it is a reason to look at what your own communication may have taught them.
Consider a manager who hears about a new AI tool at the same time as the team. The announcement promises a dramatic productivity gain. The manager has no clear timeline, has not tested the tool, and cannot explain what the change means for the work. Still, the team looks to the manager for an explanation.
The pressure is to sound ready. Repeat the announcement. Emphasize the opportunity. Invite questions.
But if your confidence is borrowed from language you do not believe, people may hear the gap. They may ask privately whether you knew more than you are saying. A usually engaged employee may arrive at a one-on-one with nothing to discuss.
That does not prove the employee has lost trust. They may be busy, cautious, unconvinced, or simply unsure what you can change. Yet when people stop bringing concerns to you, it is worth asking whether another invitation to “share feedback” will feel any different from the last one.
People do not only judge whether you have an answer. They notice whether you can distinguish what you know from what you are repeating, and whether raising a concern leads anywhere.
This is where many managers get trapped. You may have little control over the decision and less information than your team assumes. You cannot promise that jobs are safe, that the tool will improve the work, or that leadership will change course if employees object. Saying you do not know is not a failure. Pretending you do know can make every later reassurance harder to trust.
And candor has limits. It will not make a real threat disappear or turn an imposed decision into a collaborative one. Your team may have valid concerns about the tool, the quality of the work, or what the rollout means for them. Listening does not obligate you to pretend you can fix what is outside your authority.
In this scenario, Reyes repeats the CEO’s slides, and the team stays polite and distant.
That distance does not tell Reyes exactly what the team thinks. It does show that repeating the announcement has not opened the conversation.
If you lead a team through a change you did not choose, be precise. Say what has been decided and what is still open. Do not speculate about confidential matters or offer reassurance you cannot support. When someone raises a concern, explain what you can do with it: answer now, ask someone who knows, pass it to the people making the decision, or be clear that the decision is not yours to change.
Then follow through. An invitation to speak is cheap if nothing happens after people do.
Your team may still be quiet. They may not trust the process, or they may have reasons that have nothing to do with you. You cannot force the questions.
You can stop making certainty the price of having a conversation.
