Three Questions Your Team Is Asking (That You're Not Answering)

You announced the new process. You explained the rationale. You outlined the timeline. You sent the FAQ.

Your team still seems uncertain.

Not because they're difficult. Not because they weren't paying attention. Because you answered the questions you thought were important, not the ones they're actually asking.

Here are the three questions on repeat in your team's heads—even if they're not saying them out loud.

"Does this affect me specifically?"

Most organizational announcements are written broadly. New software rollout. Policy change. Department restructure. All-hands language that applies to everyone.

But your team members aren't thinking broadly. They're thinking about their desk, their projects, their Tuesday afternoon workflow.

When you say "we're implementing a new approval process," they hear: "I don't know if I have to do anything differently or if this is someone else's problem."

Generic announcements create false alarms. Half your team assumes they're affected when they're not. The other half assumes they're exempt when they're not.

Say who this applies to. Say what doesn't change. Say when people will know if it affects them.

"What are you expecting me to do, exactly?"

People can't act on implications. They can act on instructions.

"We're moving to a customer-first approach" is not an instruction. It's a value statement. Your team is left guessing what that means for their actual work.

Do they route requests differently? Escalate faster? Change how they respond to complaints? Stop doing something they're currently doing?

If you want different behavior, say what the different behavior is. If you want them to keep doing what they're doing, say that too.

Vague direction doesn't create flexibility. It creates paralysis.

"When will I know what I don't know yet?"

Change is rarely fully baked when it's announced. Details are still being finalized. Timelines are tentative. Decisions are pending.

That's fine. What's not fine is pretending everything is locked when it isn't.

Your team knows when you're holding information back. They know when details haven't been decided. The question running in their heads isn't "what's the answer?" It's "when will you tell me?"

If you don't have a complete answer yet, say when you will. If the timeline is still being finalized, say when it will be confirmed. If certain decisions are dependent on other factors, name those dependencies.

People can handle uncertainty. They can't handle uncertainty about uncertainty.

The silence you're hearing isn't agreement

When you finish your announcement and no one asks questions, that doesn't mean everything is clear. It often means people don't know what to ask yet.

Or they're still processing. Or they're waiting to see what their manager says. Or they assume the questions they have are stupid.

The real questions surface later. In sidebar conversations. In Slack channels. In meetings two weeks later when someone says "I thought we decided..." and you realize they heard something completely different.

You can prevent this. Not by talking more, but by answering the questions that are actually running underneath the surface.

Does this affect me? What am I supposed to do? When will I know more?

Start there.