Read time: 5 mins
Most for-purpose leaders I work with are carrying an invisible script that says: “I’m the one who’s meant to know.” Boards want assurance, funders want confidence, staff want stability, and communities expect you to live your values in every decision, all in a context of volatility and constraint. In that world, “I don’t know” can feel like something to avoid at all costs.
When leaders talk with me about why they don’t say “I don’t know”, what sits underneath is usually a mix of things. It might be that you hold a strong sense of accountability, that the job is to absorb uncertainty on everyone else’s behalf and turn it into a clear plan. You might feel the need to deliver without hesitation so that people who depend on services don’t miss out. Perhaps your career is built on being the safe pair of hands, the one who can walk into a mess and make sense of it. Admitting “I don’t know” can feel like betraying that identity, or confirming a private fear of being an imposter. Or maybe you work in an organisation where uncertainty has been labelled as weakness. People have seen leaders punished for changing their minds, or for surfacing risks too early. They learn that it’s safer to sound certain than to be transparent.
The understandable response is to tighten your grip: answer quickly, decide alone, project confidence. Over time, that comes with serious costs.
So while the reluctance to say “I don’t know” is completely understandable, it’s also unsustainable.
When we work with this in coaching, the aim isn’t to get you saying “I don’t know” all the time. It’s to help you use it deliberately, as a way of being truthful about uncertainty without abandoning your role.
In practice, that often sounds like:
Three shifts sit underneath those sentences:
Over time, people experience you as both human and solid: not someone who has all the answers, but someone who won’t hide the unknowns and will help the organisation navigate them.
On the other side of the conversation, your team will say “I don’t know” for different reasons. In my work with leaders and teams, I tend to hear people using it when they’re overwhelmed (“There’s too much in my head to even think right now”), afraid (“If I guess and it’s wrong, I’ll be blamed”), de-skilled (“You’ve usually had the answer, so I’ve stopped stretching my own thinking”) or they genuinely don’t know (“I don’t have the information, skill or mandate”).
Your response can either reinforce those patterns or shift them. A few simple coaching moves:
Sometimes the right move is to tell – “Here’s the call and why.” Sometimes it’s to consult – “I’ll decide, but I want your view first.” And sometimes it’s to coach – “This is yours to lead; I’ll help you think it through.” The discipline is pausing long enough to choose, instead of reflexively stepping in.
In leadership coaching sessions, “I don’t know” is often the moment we move from surface problem-solving into the real work.
Sometimes it comes early:
Sometimes it shows up when we get beneath the surface of a familiar story. A leader will start with a concrete problem - a performance issue, a tricky funder, a restructuring - and then reach a point where the old scripts don’t quite fit anymore: “Honestly, I don’t know what kind of leader this organisation needs me to be next.”
From there, we can work out what needs to change: what story you tell yourself about leadership, how you frame issues with the board, what you delegate, what you stop carrying alone, and what support or data you actually need. The goal isn’t certainty; it’s a more honest, sustainable way of leading in a complex system.
In those moments, I don’t rush to fill the gap. Instead, I might:
Often “I don’t know” is the doorway to a more honest conversation about fear, values, power and limits. In a sector that asks a lot of its leaders, having a confidential space to do that work, away from internal politics, board dynamics and performance reviews, can be the difference between sustainable leadership and quiet resignation.
If you’d like to play with this in your own practice over the next month, you might try: