What Do You Tell Your Team When You Don’t Know What Happens Next?

There’s a moment every leader eventually faces that no amount of preparation fully readies you for: standing in front of a team that needs direction, when the honest answer is that you don’t yet have one. A restructuring that hasn’t been finalized. A market shift whose full impact isn’t clear. A deal that could change everything or fall through entirely. The team is watching, waiting for something to hold onto, and what you actually have is genuine uncertainty.

The instinct in that moment is almost always to manufacture more certainty than actually exists—to give the team a clean narrative, a confident timeline, a version of events with the rough edges smoothed off, because that’s what leadership is supposed to sound like. That instinct is understandable and it’s also usually the wrong move, for a reason that has nothing to do with honesty as a virtue and everything to do with how trust actually gets built and lost.

What Your Team Is Actually Tracking

A team doesn’t need you to have all the answers. What they’re actually tracking, often without articulating it this way, is whether you can be trusted to tell them the truth as you know it, updated as it changes. That’s a different bar than having the answer, and it’s one you can meet even in a moment of genuine not-knowing. The leader who says “here’s what I know, here’s what I don’t, and here’s how I’ll keep you posted” is passing that test. The leader who fabricates certainty to fill the silence is failing it, even if the fabricated version sounds more reassuring in the moment—because the fabrication gets discovered eventually, when the timeline slips or the confident narrative doesn’t hold, and what gets damaged then isn’t just this one update. It’s the team’s baseline trust in every future update you give them.

Why Manufactured Certainty Costs More

This is worth sitting with because the failure mode of manufactured certainty is genuinely costly, and it compounds. The first time a leader’s confident prediction turns out to be wrong, the team recalibrates—not necessarily consciously, but they start quietly discounting what you say, hedging their own planning against the possibility that your read is off. That discounting doesn’t reverse easily. It’s far more expensive, over time, than the discomfort of saying “I don’t know yet” would have been in the original moment.

Process, Timeline, Principles

The more useful discipline is separating what you genuinely don’t know from what you do—because even in a moment defined by uncertainty, there’s usually more solid ground under your feet than it feels like. You may not know the outcome, but you likely know the process for getting an answer, the timeline for the next real update, and the principles that will guide the decision whichever way it goes. Those three things—process, timeline, principles—are often enough to give a team real footing, even without the outcome itself. “I don’t know if this deal closes, but I do know we’ll have clarity by the fifteenth, and whatever happens, we’re not making any structural changes to the team before then” is a genuinely different statement than either false confidence or an unstructured “we’ll see.” It’s honest about the uncertainty and still gives people something concrete to plan around.

Here’s what I know, here’s what I don’t, and here’s how I’ll keep you posted.

The Cost of Going Quiet

There’s a related mistake worth naming, because it runs in the opposite direction from false confidence and is just as damaging: using uncertainty as a reason to withdraw from communication entirely. Going quiet until there’s something definitive to say feels responsible—why create noise or anxiety around a situation that isn’t resolved yet? But silence doesn’t read as caution to a team. It reads as either you don’t know something is wrong, or you know and you’re not telling them, and people will generate their own explanation for the gap, almost always a worse one than reality. Regular contact during an uncertain period—even when the update is “no material change since last time, still expect clarity by X”—does more to hold a team steady than an eventual single announcement once everything is finally settled.

None of this requires you to project confidence you don’t have, or to pretend the situation is more comfortable than it is. It requires a specific kind of honesty: naming what’s actually known, what isn’t, and what the team can count on regardless of how the unknown part resolves. That’s a harder thing to do well than either false reassurance or silence, and it’s also the thing that actually earns the trust leaders reach for in exactly these moments.

If you’re navigating a period where you owe your team direction you don’t fully have yet, that’s precisely the kind of judgment call worth working through before you’re standing in the room. Explore coaching services.

Frequently asked questions