When a Judgment Problem Looks Like a Knowledge Problem

There's a particular kind of discomfort circulating in senior leadership right now that doesn't get named very often.

It's not confusion about AI exactly, though that's part of it. It's the vulnerability of being expected to lead clearly through something you're still working out yourself, in real time, in front of people who may understand aspects of the technology better than you do.

The conversation about AI is loud, and most senior leaders are in it, at least visibly. They're attending briefings, sitting through demonstrations, forwarding articles, asking their teams what they're doing with it and, increasingly, experimenting themselves.

I've spoken with executives who have started generating code, building simple applications or creating AI workflows, despite having no particular technical background. Sometimes that's driven by genuine curiosity and a desire to understand the technology first-hand.

Sometimes I find myself wondering whether something else is going on, whether there's an unspoken belief that leaders need to prove they "get it" before they're allowed to lead through it.

Understanding the technology matters, and first-hand experience can be enormously valuable, but that doesnt remove the responsibility to decide what to do with it.

What's less common in these conversations is hearing leaders articulate a position. Not a position on the technology itself, but a position on the decisions that sit with them.

Where do we want human judgment to remain in the loop? What level of risk are we prepared to accept? What work do we believe should change, and what should remain intentionally human? If AI creates additional capacity, what would we actually want people to do with it?

These aren't technical questions. They're leadership questions.

And yet in many organisations, the conversation seems to have become heavily weighted towards tools, pilots, governance frameworks and experimentation. All of those things matter. But they can also create the impression that progress is being made before the more fundamental judgements have been surfaced.

One of the things I've noticed in executive conversations is how often leaders describe their uncertainty as a knowledge problem.

The thinking goes something like this: once I've attended a few more briefings, spent more time experimenting, or developed a better understanding of the landscape, then I'll be in a position to decide.

Sometimes that's true. But not always.

At a certain point, the conversation stops being primarily about understanding the technology and starts becoming about judgment. The information is still useful, but it no longer resolves the thing that's making the decision difficult.

That's often the point at which leadership starts to feel uncomfortable.

Because the decisions that matter most are rarely the ones that can be delegated to the technology team, the legal team, or an external advisor. They sit with senior leaders precisely because they involve trade-offs. They require a view about risk, values, priorities and direction.

In that sense, AI may be creating a challenge that feels new while simultaneously exposing one that is very familiar.

Leaders have always been expected to provide direction before certainty is available. They have always had to make decisions while the picture remained incomplete. The technology may be changing quickly, but the underlying leadership task is surprisingly consistent; the challenge is not allowing activity to become a proxy for judgment.

Building a prototype may help you understand what's possible. Running experiments may reveal opportunities that would otherwise remain hidden. But there comes a point where experimentation stops being the constraint.

The harder questions are often the ones that can't be answered through another pilot or proof of concept. They require a view about what matters, what risks are acceptable, and what direction the organisation intends to take.

In some cases, the experimentation becomes a way of postponing those conversations. Not intentionally, but because learning feels productive and judgment feels exposed.

The organisational consequences are rarely dramatic at first. Assumptions fill the space where decisions haven't been made. Teams interpret signals. Local choices become established practice. A collection of sensible decisions gradually accumulates into a direction that nobody explicitly chose. By the time senior leaders realise this is happening, they often find themselves responding to momentum rather than creating it.

The scale of the opportunity created by AI is real, and it's equalled by the uncertainty. When I listen to the conversations leaders are having about it, I'm often struck by how familiar the underlying challenge sounds. It has less to do with technology than it does with the enduring demands of leadership itself: navigating ambiguity, exercising judgement, and making decisions before certainty arrives.

The question worth sitting with is whether you're participating in the conversation about AI or doing the harder work of leading through it.