Leading Through Ambiguity: Stop Pretending You Have a Map
The only thing worse than the fog is a leader who pretends they can see through it. Here is how to navigate the unknown.
We need to be honest about something.
Most leaders have a love-hate relationship with ambiguity. We put “thrives in chaos” on our resumes. We talk about being “agile” in town halls. We say we embrace the unknown.
Until it actually shows up.
Then, we freeze. We hedge. We write 40-page strategy decks filled with buzzwords to hide the fact that we have no idea what is going to happen next quarter.
In cybersecurity, ambiguity is the default state. It is threat intel you can’t verify. It is a regulator changing the rules mid-audit. It is a board demanding a guarantee of safety that mathematically cannot exist.
Here is the blunt truth: Ambiguity isn’t a bug in the system. It is the condition of leadership.
And most leaders are failing the test. Not because they don’t have the answers, but because they are terrified to admit that the questions have changed.
Ambiguity is Not Uncertainty (There is a Difference)
We tend to use these words interchangeably, but in the C-suite, the distinction matters.
Uncertainty is when you know the variables, but you lack the data. It’s a math problem.
Example: “I don’t know if this patch will break the server, but I know the risk probability is 15%.”
Ambiguity is when you don’t even know the variables. It’s a definition problem.
Example: “We need to secure our AI strategy, but we don’t know how the business intends to use AI, or what the regulations will be next year.”
Uncertainty asks for a calculator. Ambiguity asks for a compass.
When you treat ambiguity like uncertainty, trying to “solve” it with more data, you get analysis paralysis. You burn out your team hunting for facts that don’t exist yet.
The “Empowerment” Trap
Here is the darkest side of ambiguous leadership, and I see it constantly.
Some leaders use ambiguity as a shield. They stay vague. They refuse to set boundaries. They push the decision down to a Director or Manager and say, “I’m empowering you to own this.”
That isn’t empowerment. That is evasion.
When you pass the fog downstream without a framework, you aren’t building leaders; you are setting people up to fail. You are protecting your own ego so that if the initiative goes sideways, you can blame the execution rather than the lack of direction.
Real leadership isn’t about knowing the destination. It’s about building the scaffolding so the team can climb safely, even in the dark.
Model “Calm Confusion”
So, what does good leadership look like in the fog?
It looks like Calm Confusion.
Weak leaders hide their confusion. They hold 45-minute meetings to “gain alignment” without ever stating the problem, leaving everyone more confused than when they entered.
Strong leaders anchor the room in reality. They say:
“I don’t know the answer yet. I don’t even know if we’re asking the right questions. But here is what we do know, and here is the next step to figure out the rest.”
This isn’t “soft” vulnerability. It is strategic precision. By admitting the unknown, you give your team permission to explore it. You stop them from wasting energy pretending they have a plan, and focus their energy on building one.
Frameworks Over Polish
When the map is gone, you don’t need a polished slide deck. You need a framework.
One of the best ways to tackle a massive, foggy problem is to break it down into Provisional Decisions.
Isolate the Knowns: What is undeniably true right now?
Name the Assumptions: What are we guessing at? (Write these down. Explicitly.)
Set the Hypothesis: “We are going to proceed as if X is true for two weeks, then re-evaluate.”
In cybersecurity, this saves lives. You can’t wait for perfect attribution before blocking an attack. You make a provisional call based on the framework you built before the crisis.
Leading the Fog
Ambiguity isn’t going away. The market is too volatile, and the tech is moving too fast.
If your team shuts down when the goals are vague, don’t blame them. Look at the context you set.
Did you frame the chaos as a failure of planning?
Or did you frame it as a moment for discovery?
Leading through ambiguity means owning the fog, not outsourcing it. It means moving with the uncertainty, encouraging experiments, and recognizing that “I don’t know” is a valid strategic position… as long as it’s followed by “but here is how we find out.”
When the fog rolls in, you have a choice. You can hide. Or you can light the lantern.
References
Thinking Fast and Slow (Stanford News)
Why it matters: Insights on how communication breakdowns happen when shared mental models (context) are missing during ambiguous times.
Leading in Ambiguity (Conversant)
Why it matters: Practical frameworks for breaking down “foggy” decisions into manageable components.
Ambiguity and Team Decision Quality (PMC)
Why it matters: Research showing how ambiguity can actually improve collaboration - if the culture supports open exchange.
Role Ambiguity and Stress (PMC)
Why it matters: The hard data on what happens to employee health and productivity when leaders fail to provide a “shared frame.”