Trust Comes Before the Technology
June 2026

Trust Comes Before the Technology

Trust Comes Before the Technology

There's a pattern that repeats in almost every conversation I've had with an experienced leader from an established company -- industry, insurance, infrastructure, it doesn't matter. They know AI is changing things. They've read the articles. Someone on the board has asked the question. Perhaps they've even tried ChatGPT in private.

But in a formal setting -- with consultants in the room, with a budget decision pending -- they behave as though they understand more than they do.

That's not dishonesty. It's healthy self-preservation.

The Trust Problem

A senior CEO of a mid-size industrial company shouldn't have to ask a selling consultant what a context window is. That creates an unequal dynamic he knows he'll lose. So he doesn't ask. He nods instead, makes a decision based on incomplete information, and hopes it works out.

It rarely does.

What we call "resistance to AI transformation" is often nothing more than this: a leader who has never had a safe space to be honest. To say: I don't understand enough to make this decision. What do I actually need to know?

That conversation has never happened. And it shows clearly in the results.

What's Actually Blocking

The AI Sweden Leadership Report 2026 identifies the mandate question as the critical dividing line -- transformation succeeds when owned by someone at the top with genuine ownership. I share that picture entirely. But it leads to a follow-up question the report doesn't answer:

How is someone at the top supposed to take genuine ownership of something they don't understand well enough?

The answer is: they can't. Not until there's a safe space for the honest conversation.

It's not a lack of will. It's a lack of a specific kind of context: a room without a sales agenda, without prestige at stake, where the leader can actually locate where they are -- and where they need to get to.

The Missing Map

The first thing I do in a new leadership conversation is try to understand where the person actually is on the AI scale. Not where they want to be. Not how they present themselves. Where they are.

It comes down to simple, concrete questions. Do they have personal AI settings? Have they uploaded their own documents and got answers from them? Have they seen the difference between a generic answer and one grounded in their own data? Do they know what it costs to run that in production versus a test environment?

The answers to those questions are a map. An honest map. And without that map, all recommendations about "AI strategy" and "transformation" are built on sand.

Consulting reports often deliver a map -- but it's the consultant's map, not the leader's. It's the map of where they should want to go, not an honest inventory of where they actually are.

The Safe Room

What's needed is a format where the leader can be genuinely curious without that being interpreted as incompetence. Where they can say "I don't understand this" and get a straight answer, not an unmediated sales pitch.

That format looks something like this:

A first informal meeting -- not a meeting with presentations and proposals, but a conversation. What do you know about AI today? What have you tried? What are you worried about? What would you actually need to feel confident about this decision?

From those answers you map where the leader is. Not to judge, but to know what to show. A leader who has never uploaded their own document and received a grounded answer needs to see that -- live, with their own data -- before anything else is meaningful.

That experience is what creates trust. Not a 60-page report.

Initiatives That Survive

Organisations that succeed with AI transformation always have someone at the top who understands well enough to take genuine ownership. Not necessarily a technician -- but someone who can tell hype from reality, who can challenge vendors' claims, who can steer without depending on someone else to interpret the world for them.

That person doesn't come into being by reading a report. They come into being through an honest conversation -- usually the first one -- where they're allowed to be exactly as unknowing as they actually are, and from there begin building real understanding.

Trust must come before the technology. That's not a soft opinion. It's the prerequisite for anything else to hold.

See also: The Impressive and the Billable Are Not the Same Thing (series 28) -- the same silence mechanism, but on the practitioner side: no one in the technical circle says they haven't delivered. And The Leader Who Can't Delegate (series 21) -- on why the mandate must come from the top.

Was this helpful?