How untested assumptions shape decisions, relationships and behaviour
Two executives stopped trusting each other over an email.
Neither of them realised that was what had happened.
The email itself was unremarkable. One executive had asked the other for information needed for a board paper. The response arrived late and consisted of three short sentences.
The recipient read it and thought:
“Here we go again. She doesn’t see this as a priority.”
By the afternoon, the thought had evolved:
“She never really supports my team.”
By the next morning:
“She’s protecting her own area.”
Nothing had actually happened beyond a late, brief email but a story was already forming.
We rarely experience facts as facts
Chris Argyris used a model known as the Ladder of Inference to describe how quickly human beings move from observation to interpretation and action. We observe something, select certain parts of what we have observed, give those details meaning, make assumptions, draw conclusions, adopt beliefs and then act as though those beliefs are reality.
The whole process can happen in seconds.
Someone looks at their phone while we are speaking. We notice it, interpret it as disinterest and conclude that they do not respect us. We become cooler towards them, they sense our irritation and withdraw, and suddenly we have evidence that they are distant.
The story begins to confirm itself.
The executive email
When the two executives eventually discussed the issue, the explanation for the late email was almost embarrassingly ordinary.
The sender had spent the afternoon dealing with a serious staffing issue. She assumed the request was not urgent and sent a short response from her phone between meetings because she did not want to leave it unanswered.
That was it.
No territorial behaviour. No lack of support. No hidden agenda.
The other executive’s interpretation had been understandable but it was based on assumptions and conclusions that didn’t fit all of the data, specifically the data she didn’t know.
This happens constantly in organisations because leaders work in conditions of incomplete information. We have to interpret. The problem begins when we forget that interpretation has taken place.
Our story becomes “what actually happened”, at least in our own minds.
Certainty is seductive
Senior leaders are particularly vulnerable to this because organisations reward confidence. People want leaders to make sense of complexity, and over time leaders can become very good at pattern recognition. This skill can be useful but it can also mean we become highly skilled at reaching conclusions quickly, not necessarily accurately.
The dangerous phrase is:
I know what’s going on here.
Perhaps, but perhaps not.
A leader sees resistance to a change program and concludes, “People don’t like change.”
A manager sees someone repeatedly questioning a proposal and concludes, “He’s being negative.”
An executive sees a colleague withholding support and concludes, “She’s playing politics.”
Each conclusion may be correct, but each is still a conclusion, based on a series of interpretations which is not the same as the absolute, objective truth we often mistake it for.
The discipline is to test the story before organising our behaviour around it.
One question can change the conversation
There is a simple question I often encourage leaders to ask:
What else could be true?
Or
What other story equally fits the data, but feels better or is kinder or more generous?
This may sound like an invitation to become endlessly uncertain but it’s not. It’s a way of loosening the grip of our first interpretation.
The person questioning the proposal may not be negative; they may see a risk nobody else sees. The employee resisting change may not fear change; they may have lived through three previous initiatives that disappeared within six months. The colleague who seems territorial may be responding to commitments you do not know about.
Curiosity does not require us to abandon judgement, rather it improves the quality of the judgement.
Advocacy and inquiry
One of the most useful leadership disciplines is learning to balance advocacy and inquiry.
Advocacy means making our thinking visible:
“My concern is that we’re moving too quickly because two major dependencies haven’t been resolved.”
Inquiry means genuinely exploring the other person’s thinking:
“What are you seeing that gives you confidence we can manage that risk?”
Weak dialogue often contains one without the other. Too much advocacy becomes argument or can come off as arrogant; too much inquiry can become polite avoidance in the best case or interogation in the worst.
Good leadership conversations contain both.
“Here’s how I’m seeing it. What am I missing? ”
Just that sentence can save a team months of unnecessary conflict and result in greater team coherence and collaboration.
The stories become culture
This matters beyond individual relationships. Organisations develop collective stories too.
“Head office doesn’t understand the frontline.”
“Operations always blocks innovation.”
“Finance only cares about cost.”
“The executive team has already decided.”
Once these stories take hold, people interpret new events through them. Soon the organisation is not responding to what is happening; it is responding to what it expects to happen.
Leadership requires interrupting that cycle, not by insisting everyone think positively, but by helping people distinguish between what we know, what we think, and what we have not yet tested.
That distinction sounds simple, but in practice, it can transform the quality of conversation in a team.
And sometimes the most useful leadership question in the room is not:
“What should we do?”
It is:
What story have we started telling ourselves about what is happening here?
Then we can truly create the culture we want, served by stories that actually work for our benefit rather than undermining it.