Because honesty about what you don’t know builds more trust than confidence about what you do.
Leaders are trained to have answers.
To project confidence. To signal certainty. To speak with the authority that their position implies and their people expect.
And in stable environments, that works reasonably well.
But in moments of genuine uncertainty — during organizational change, during difficult decisions, during the long middle of a transformation where the answers aren’t yet formed — the pressure to perform certainty produces one of the most expensive habits in organizational leadership.
Saying things you don’t actually know.
Because the alternative — “I don’t know yet” — feels like weakness. Like failure. Like a leader who isn’t on top of things admitting it publicly.
It isn’t.
“I don’t know yet” is one of the most powerful phrases available to a leader navigating uncertainty. And the leaders who understand this — who have learned to say it clearly, specifically, and with genuine composure — consistently build more trust than those who perform a certainty they don’t have.
Why leaders avoid saying it
The pressure against “I don’t know yet” is real and comes from multiple directions simultaneously.
Organizational culture often rewards the appearance of having answers. Leaders who project confidence get read as competent. Leaders who acknowledge uncertainty get read as unprepared — even when the uncertainty is genuine, even when no reasonable person could have the answer yet, even when the honest answer is that the situation is still developing.
The hierarchy creates pressure too. People look to leaders for certainty precisely because leaders are supposed to have more information, more context, and more control than the people they lead. When a leader says “I don’t know,” it can feel to some people like a failure of that function — like the person who is supposed to know things doesn’t know them.
And there’s a personal pressure as well. Most leaders have internalized the expectation of certainty deeply enough that admitting uncertainty feels privately uncomfortable — like a gap in their own capability rather than an honest response to a genuinely uncertain situation.
All of these pressures push in the same direction: toward performed certainty, toward confident-sounding answers that are more complete than the actual situation warrants, toward language that manages perception rather than reflects reality.
And all of them produce the same outcome: communication that employees don’t fully trust, because they can sense the gap between the confidence being projected and the reality they’re experiencing.
What “I don’t know yet” actually signals
Here’s what most leaders don’t fully understand about honest uncertainty.
Employees are not primarily evaluating whether their leader has all the answers. They’re evaluating whether their leader can be trusted to tell them the truth.
Those are different assessments. And they produce different responses to “I don’t know yet.”
When a leader who has consistently been honest says “I don’t know yet” — when the acknowledgment of uncertainty is consistent with everything else they’ve communicated — employees don’t hear weakness. They hear honesty. They hear a leader who respects them enough to tell them what’s actually true rather than what sounds best. They hear a signal that when this leader does claim to know something, they actually know it.
That’s trust. Not the kind built through confidence. The kind built through reliability — through the accumulated experience of a leader whose words match their reality.
When a leader who has consistently performed certainty says “I don’t know yet” — when the acknowledgment comes only after the performed certainty has been contradicted by events — employees hear something very different. They hear confirmation that they were right not to fully trust what they were being told. The admission of uncertainty, in this context, doesn’t build trust. It confirms its absence.
The power of “I don’t know yet” is not in the phrase itself. It’s in the pattern of honesty that gives the phrase its credibility.
The three versions of “I don’t know yet”
Not all acknowledgments of uncertainty are equal. The phrase lands very differently depending on what surrounds it.
The complete version — and the only one that builds trust:
“I don’t know yet — and here’s what I do know, here’s what’s still being worked through, and here’s when I expect to be able to tell you more.”
This version does four things simultaneously. It acknowledges what’s genuinely unknown. It provides what is known, which prevents the unknown from feeling like everything is uncertain. It signals that the unknown is being actively worked on rather than ignored. And it gives people a timeline — which tells them when to expect clarity rather than leaving them to decide for themselves how long to wait before filling the silence with speculation.
This version requires preparation. You need to know what you do know before you can be honest about what you don’t. You need to have a genuine sense of when more information will be available. And you need the composure to say it in a way that signals steadiness rather than anxiety — because “I don’t know yet” delivered with visible anxiety is not calming. It’s alarming.
The incomplete version — honest but insufficient:
“I don’t know yet.”
Full stop. No context. No timeline. No signal of what is known or when more will be available.
This version is honest. It’s also unsatisfying in a way that produces exactly the speculation it was supposed to prevent. People hear the acknowledgment of uncertainty and have nothing to anchor to. The phrase tells them what isn’t available. It gives them nothing to hold in its place.
Honest uncertainty without containment is not reassuring. It’s destabilizing. The full version works because it contains the uncertainty inside something solid. The incomplete version leaves the uncertainty exposed.
The hedged version — neither honest nor useful:
“We’re still working through some details but we’re feeling good about the direction.”
This is the most common version — the one that tries to acknowledge uncertainty while managing the perception of it. It signals that something is unknown while simultaneously trying to prevent the anxiety that acknowledgment would produce. It’s designed to be reassuring.
It isn’t. Employees hear the hedge and read it as confirmation that something uncertain is being managed rather than communicated. The reassurance reads as spin. The “feeling good about the direction” reads as the kind of performative optimism that experienced employees have learned to discount.
The hedged version builds neither the trust of honesty nor the stability of certainty. It produces the worst of both.
When “I don’t know yet” is the right answer — and when it isn’t
“I don’t know yet” is the right answer when the uncertainty is genuine — when the answer truly isn’t available yet, when claiming to know would require saying something that isn’t true or isn’t final.
It’s not the right answer when it’s used as avoidance — when the answer exists but is uncomfortable, when the information is available but hasn’t been prepared, when “I don’t know yet” is a way of deferring a conversation that needs to happen.
Employees are sophisticated readers of organizational communication. They can usually distinguish between a leader who genuinely doesn’t know yet and a leader who knows but isn’t saying. The first builds trust. The second erodes it — even when the avoidance is tactful, even when the timing isn’t right for disclosure, even when there are legitimate reasons the information isn’t being shared yet.
When information exists but can’t be shared yet — when legal constraints, timing considerations, or sequencing requirements make disclosure premature — the honest version isn’t “I don’t know yet.” It’s “I’m not in a position to share that yet — and here’s when I expect to be.” That’s a different acknowledgment. It’s still honest. It doesn’t pretend to uncertainty that isn’t real. (For how to navigate the timing of disclosure during change, read When to Communicate Early During Change — and When to Wait.)
What “I don’t know yet” looks like across different leadership situations
In a town hall when someone asks about the timeline for a decision that hasn’t been made:
“That decision is still being worked through — we expect to have more clarity by the end of the month. What I can tell you is that the factors we’re weighing are X and Y, and the process for making the decision involves Z. I’ll share more as soon as we have it.”
In a team meeting when a direct report asks about the impact on their role:
“I don’t have that answer yet — and I want to be honest with you about that rather than tell you something that might change. What I do know is that your role is in this function, that this is the timeline we’re working to, and that I will come back to you with specifics as soon as I have them. My commitment is that you’ll hear it from me before you hear it from anyone else.”
In a leadership communication when the program is facing uncertainty:
“We’re in a period where we don’t have all the answers, and I think it’s important to name that directly. Here’s what we know. Here’s what we’re still working through. Here’s what you can count on in the meantime. And here’s when we expect to have more to share.”
In each of these, the same structure applies. Name the uncertainty. Provide what’s solid. Signal what’s in motion. Give a timeline. The words change with the context. The structure is consistent.
The organizational case for leaders who say it
Beyond the individual trust it builds, there’s an organizational case for normalizing honest uncertainty at the leadership level.
When leaders model “I don’t know yet” — when they say it clearly and without shame — they create permission for the people around them to do the same. Managers who hear their executives acknowledge uncertainty are more likely to acknowledge it honestly with their own teams rather than performing a certainty they don’t have. Employees who hear honest uncertainty from their leaders are more likely to surface genuine questions and concerns rather than performing alignment they don’t feel.
This matters enormously during change. The organizations that navigate transformation most effectively are the ones where honest uncertainty is culturally safe — where saying “I don’t know” is more respected than pretending you do. Where gaps in understanding surface early because people feel safe naming them rather than late when they’ve compounded into adoption failures.
That culture doesn’t arrive fully formed. It’s modeled — by the leaders at the top, whose behavior signals what’s safe and what isn’t, whose honest uncertainty gives everyone below them permission to be honest too.
The calm cascade operates here as directly as anywhere. Honest uncertainty at the top produces honest uncertainty throughout. Performed certainty at the top produces performed certainty throughout — until reality contradicts it, and then it produces the trust collapse that performed certainty always eventually creates. (For the full treatment of how leadership tone replicates through organizations, read The Calm Communicator.)
What this looks like in practice
I worked with a senior leader preparing for a town hall during a period of genuine organizational uncertainty. A significant strategic review was underway. Outcomes were unknown. The leadership team had been advised to communicate confidence and focus on what was stable.
The leader’s instinct was to follow that advice — to project confidence, emphasize the positive, and avoid naming the uncertainty directly. It felt safer. It felt like the right leadership posture.
We talked through what the employees in that room already knew. They knew the review was happening. They knew outcomes were unclear. They had been watching the leadership team communicate with increasing polish and decreasing specificity for three months. The confidence wasn’t landing as stability. It was landing as confirmation that something was being managed.
We rebuilt the town hall communication around honest uncertainty. Named the review directly. Acknowledged what was unclear. Provided what was genuinely stable. Gave a specific timeline for when more would be available.
The response from employees was the most positive that leader had received in eighteen months of the review period. Not because the news was good — it wasn’t. Because for the first time, the communication felt real.
“I don’t know yet” — said with composure and surrounded by what was known — had done what three months of managed confidence hadn’t.
It had made people feel informed.
Final thought
Leaders are not paid to know everything.
They’re paid to navigate uncertainty well.
And navigating uncertainty well — in a way that builds trust rather than erodes it, that stabilizes rather than destabilizes, that gives people something real to hold rather than something polished to discount — almost always requires saying the thing that feels most vulnerable.
“I don’t know yet.”
Not as admission of failure. As an act of leadership.
Because the leaders people trust most are not the ones who always have the answer.
They’re the ones who are always honest about whether they do.
FAQs: Leadership transparency and uncertainty
Because employees are not primarily evaluating whether their leader has all the answers — they’re evaluating whether their leader can be trusted to tell them the truth. “I don’t know yet,” said honestly and with a clear structure around it, builds the reliability-based trust that performed certainty consistently erodes. When a leader acknowledges genuine uncertainty, employees learn that when this leader does claim to know something, they actually know it.
With four elements: acknowledge what’s genuinely unknown, provide what is known, signal that the unknown is being actively worked on, and give a timeline for when more clarity will be available. “I don’t know yet — here’s what I do know, here’s what’s still being worked through, and here’s when I expect to be able to tell you more.” That structure contains the uncertainty inside something solid rather than leaving it exposed.
When it’s used as avoidance — when the answer exists but is uncomfortable, when information is available but hasn’t been prepared, or when “I don’t know yet” is a way of deferring a conversation that needs to happen. Employees can usually distinguish between genuine uncertainty and managed avoidance. The first builds trust. The second erodes it. When information exists but can’t be shared yet, the honest version is “I’m not in a position to share that yet — and here’s when I expect to be.”
By establishing a pattern of reliability. Leaders who consistently acknowledge what they don’t know — and who follow through by sharing more when they said they would — build the kind of trust that makes employees willing to wait for clarity rather than filling the silence with speculation. The trust isn’t built by any single instance of honesty. It’s built by the accumulation of honest moments over time.
Performed certainty is communicating confidence about outcomes that aren’t actually certain — projecting a completeness and clarity that the situation doesn’t warrant. It’s dangerous because employees can almost always sense the gap between the confidence being projected and the reality they’re experiencing. When that gap is confirmed by events — when the certainty turns out to have been premature — it doesn’t just undermine that specific communication. It casts doubt on everything the leader has said before.
It models permission. When leaders acknowledge uncertainty honestly, the people around them are more likely to do the same — managers with their teams, employees with their peers, everyone in the system with everyone else. It creates a culture where gaps in understanding surface early rather than late, where honest questions are asked rather than avoided, and where the communication environment is safe enough for people to be genuinely rather than performatively aligned.
The Clarity Framework™ starts with diagnosing what’s actually unclear before adding more communication — which requires leaders to be honest with themselves about what they know and don’t know before they speak. The define principle builds the narrative structure that contains uncertainty inside what’s solid. The design principle creates the predictable rhythm that makes “I’ll have more for you by Friday” a commitment rather than a deflection. And the deliver principle explicitly addresses the emotional honesty that makes “I don’t know yet” land as leadership rather than weakness.
Ana Magana is a change management and communications strategist based in Calgary, Alberta. She helps leaders communicate with the honest clarity that builds genuine trust — through The Clarity Framework™.
Leading through uncertainty and not sure how to communicate it? Work with Ana →
Related reading: How to Communicate When You Don’t Have All the Answers → When to Communicate Early During Change — and When to Wait → The Calm Communicator: Leading Change With Clarity →