The Confidence Gap

We might ask whether there’s any research behind the claim. We might suggest treating it as a hypothesis and testing it. We might point out that confidence and correctness are not the same thing.

The problem is that words like research, hypothesis and testing do not sound decisive. They sound slow. They sound like someone has interrupted a moment of agreement to reopen the question.

From the designer’s point of view, this is sensible. We do not want to attach certainty to something we do not yet know to be true. We want to check. We want to understand the edge cases. We want enough evidence that we will not have to reverse course six months later.

To everyone else, it can look like a lack of conviction.

This is one of the recurring tensions between designers and their business partners. Designers are often trying to establish what is true. Their colleagues may be trying to get an idea through the gears of the organisation.

Those are not always the same job.

A surprising amount of business runs on truthiness: something that feels true, sounds plausible and can be repeated convincingly enough to create momentum. Once an idea has acquired senior sponsorship and a confident narrative, the burden of proof shifts. The person asking questions starts to look obstructive, while the person making the unsupported claim looks like a leader.

Designers sometimes make this worse through the way we speak. We hedge. We qualify. We add caveats. We say “it depends” when it genuinely does depend. All of this may be intellectually honest, but it rarely carries much weight against someone willing to say, “This is what customers want.”

AI has made this dynamic more obvious.

AI is the ultimate confident business partner. It states things cleanly, quickly and with very little visible doubt. Even when we know it can be wrong, the fluency is persuasive. A well-structured answer feels researched, even when it is not.

And because the reason we are using AI is usually speed, we are not especially inclined to check its work. If it includes a source, we may glance at the link. We probably will not read the underlying paper, inspect the methodology or check whether the source says what the summary claims it says.

We accept the answer because it sounds like an answer.

This is not limited to design or technology. It is increasingly what people seem to want from politicians too. Complexity is interpreted as weakness. Caution sounds evasive. Nobody wants to hear that the situation is difficult, that the evidence is mixed, or that several experts need to spend six months working through the consequences.

They want someone who says they understand the problem and knows exactly what to do.

Simple answers feel reassuring. They are also often wrong.

Designers should not respond by becoming equally careless with the truth. The answer is not to replace uncertainty with bluster. But we do need to get better at expressing uncertainty without sounding paralysed by it.

There is a difference between saying, “We don’t really know, so perhaps we should do some research,” and saying, “We are about to make an expensive decision based on an untested assumption. Here is the fastest way to find out whether it is true.”

The second statement contains no more certainty than the first. It simply makes the cost of being wrong more visible.

That may be the real communication problem. Designers often explain why they are uncertain, but not why everyone else should care.

As more of our colleagues begin to rely on AI, the ability to distinguish confidence from evidence will become more useful, not less. The world is filling up with systems and people that can produce a convincing answer on demand.

Our job is not to be the least confident voice in the room.

It is to make doubt harder to dismiss.