Skip to content
← All posts Critical Thinking

How to Lead Through Uncertainty When You Don't Have the Answer

Leaders fail in uncertainty two ways: faking certainty or hiding behind it. Five practices from the episode keep a team's trust while you work the problem out loud.

Early in his career, one of the hosts of The Leader Factor podcast worked inside a company whose executives kept telling the organization, “We’re going to grow, and we’re going to be fine.” Nothing backed it up. Other members of the executive team doubted the message. Employees saw the same uncertainty the executives did. They just weren’t invited to name it. The company went into bankruptcy.

The failure was not optimism. The failure was that no one could say “I don’t know,” so no one could test whether the optimism was true. That story opens the latest episode, 5 Ways to Lead When You Don’t Have the Answer, with Dr. Timothy R. Clark and Junior. This piece walks through the argument and the first of the five practices.

Sounding certain shuts down dissent without ever punishing it

Most leaders were taught the oracle model: the leader is the expert, holds the answers, and shows no weakness. Teams learned their half of the deal and look to the leader for certainty. Both sides were socialized into it, which is why it survives even when the future is, in the hosts’ words, an ocean of uncertainty.

Two slides follow. First, assumptions drift into facts. Nobody decides to promote them. Repetition does it. Second, opinions harden into dogma, stated so forcefully that the message is don’t challenge this. As the hosts put it on the episode, they take on the status of a fact and we all look around like, is that a fact in evidence? No, but we treat it that way.

Then the team faces a choice: raise a hand or stay quiet. Raising a hand is expensive. Push on a leader’s confident story long enough and you get branded disloyal, when you may be the most committed person in the room, trying to absorb reality while others look away.

Here is the part most leaders miss. You don’t have to punish disagreement to suppress it. You can be warm, approachable, even welcoming of questions, and still shut down dissent by sounding certain. Nobody challenges what looks settled. There is no pushback because there is no opening.

Do this week: label what you say. Before you state a view in your next meeting, tag it out loud. “This is an assumption.” “This is my opinion.” “This is a fact, and here is the evidence.” Watch who speaks up once the label is on.

Only one quadrant of reality and mood keeps a team moving

The episode puts two axes side by side. One runs from denial to acceptance of reality. The other runs from pessimism to optimism. The hosts named one corner, optimistic denial, and suggested the rest of the grid was worth building.

Pessimistic moodOptimistic mood
Accepts realityResigned uncertainty. “Nobody knows what’s coming, so I won’t commit to anything.” The team stalls.Grounded optimism. “Here is what we know, here is what we don’t, and here is where we’re headed.” The target.
Denies realityPessimistic denial. A bleak story told with the same confidence and the same lack of evidence.Optimistic denial. “Everything’s going to be okay,” while the team looks at obstacles no one has a plan for. Credibility drains.

Place your last three communications to your team on the grid. Then ask one person you trust to place them without seeing your answer. Grounded optimism can carry energy and encouragement while you are openly unsure.

Hiding behind uncertainty is the newer failure

Overconfidence gets the attention, but the opposite failure has become common in a dynamic environment: leaders who respond to uncertainty by saying, “Nobody knows what happens next year, or in 18 months.” It sounds responsible. Play it forward and it isn’t. If the leader is unmoored, the organization has nothing to steer by. People stop following someone who isn’t leading anywhere.

OverconfidentCalibratedAbdicating
Sounds like”We’re going to double the business.""Here is what I’m sure of and what I’m not.""I have no idea. Nobody does.”
Team responseGoes quiet. Doubts privately.Brings evidence. Pushes back.Waits, or looks for someone else to follow.
Your moveName your assumptions. Invite disproof.Keep doing this on a steady cadence.Do the homework. Commit to a next move.

If you live on the uncertain side, the question to ask yourself is blunt: how much homework have you really done? A lot can be known. Some executives in the episode had put AI in a drawer. They knew it had implications, shut the drawer, and ran the business as before. That is denial in a polite form. A topic labeled “too uncertain” is a reason to explore, not an excuse to skip the work.

The job is the process, not the prediction

The old maxim says the leader should have the answer. The episode replaces it with a different job: the leader has the question and the process to go find the answer. Your confidence belongs in your ability to problem-solve, not in a prediction. As the episode puts it, you are not responsible for having the answer. You’re responsible for finding out how to get one.

That reframe changes what your team is evaluating. They know you can’t see around the corner. What they want to know is whether you are the person they want in the uncertainty: someone with a record of working problems out collaboratively, who will apply themselves again this time.

Do this week: pick one topic you’ve been treating as unknowable. Write down three things about it you could find out in the next five days, and who could help you find them.

Test reality out loud, and say what would change your mind

Reality testing is the first practice, and it never ends. The episode’s framing, borrowed from Peter Drucker, is that your job is to interpret the meaningful outside and bring it into the organization. The hosts say they now make these distinctions at least twice as often as they used to, because something can shift two days after you’ve told the team what to expect.

Sort what you tell the team into four buckets, and say which bucket each item belongs in.

BucketThe questionHow to say it
KnownWhat do we know for sure?”This is confirmed: …”
PlausibleWhat seems likely but isn’t proven?”I think this is likely, based on …”
OptionsWhat are we weighing?”We’re considering three paths: …”
UnknownWhat can’t we know yet?”We don’t know …, and here is how we’ll find out.”

Then say what would change your mind: “To think something else, this would have to be true.” That sentence turns an assumption back into a hypothesis the team can help test.

Keep the interpretation shared. The hosts describe the adaptive challenges you face in three baskets: opportunities, threats, and crises. The mix changes week to week. If only you hold your read on them, your team can’t commit to it. Shared interpretation of the meaningful outside is what lets people move together.

The remaining four practices are where the guide does its work. Admit what you don’t know, with the damaging admission and a say-this-not-that table for the five things leaders say when they’re unsure. Set decision rights before you ask for input, with the four decision modes, what you tell the team in each, and what that clarity prevents. Give people something to work toward, and why vision lowers the cost of every decision along the way. Make the call, and the checklist to run before you take any decision to your team. Then a five-day practice, one move per day, with the words to use.

Ready to bring it to your team? Talk with us →