Most teams don’t make decisions based on facts alone.
From my experience working with leaders during change, they decide from stories.
Stories about why something happened.
Stories about who’s responsible.
Stories about what will or won’t work.
And the dangerous part?
Those stories feel like reality.
At Shift, this is one of the most common patterns I see inside teams that feel stuck, frustrated, or divided: people defending explanations instead of examining them. Not because they’re careless. Because the human brain is built to close the story fast.
That’s why one of the core thinking disciplines we teach leaders is this:
Treat every explanation as a hypothesis, not as a fact — including your own.
This single shift changes how teams think, speak, and decide under pressure.
Why this matters more than leaders realise
When an explanation hardens into “the truth,” three things happen fast:
- Curiosity shuts down.
- Disagreement feels personal.
- Decisions get made on confidence, not accuracy.
Cognitive science calls the alternative intellectual humility — the ability to hold your view lightly enough to update it when new information appears. Teams that practise this learn faster, argue better, and make calmer decisions in complex situations.
This isn’t about being vague or indecisive.
It’s about being decisive on action, slower on story.
Here’s how leaders can teach this discipline in practice.
Step 1: Name the story without believing it
The first move is simple and surprisingly powerful: separate the story from reality.
In meetings, I often hear leaders say things like:
- “This happened because they don’t care.”
- “Senior leadership is blocking us.”
- “The team resisted again.”
Instead, teach your team to say:
“Let’s name this for what it is — this is the story we’re holding, not the truth we’re defending.”
Make it visible. On a board or document, literally label:
- Story A: what senior leadership says happened
- Story B: what the frontline experienced
- Story C: my own assumptions
When people label thoughts as thoughts, emotional intensity drops. The brain gains distance. Reactivity softens. Better choices become possible.
I’ve watched tense rooms physically relax when this step is done well.
Step 2: Suspend certainty on purpose
Strong teams don’t rush to be right. They delay certainty deliberately.
Give your team explicit permission to pause judgment:
“For the next 15 minutes, we are not proving anything right or wrong.”
Time-box it.
Name the mode:
“This meeting is information-gathering, not conclusion-making.”
Then add one rule:
Every conclusion must be paired with a question.
“If this story is true, what else should we see?”
“If it isn’t, what would be missing?”
This interrupts confirmation bias — the brain’s habit of collecting only evidence that supports what it already believes. Slowing the story doesn’t weaken leadership. It strengthens decision quality.
Step 3: Hunt for disconfirming data
This is where teams usually resist — and where thinking quality jumps.
Before closing any decision, require one thing that doesn’t fit.
Ask:
- What behaviour contradicts this story?
- Where are the exceptions?
- Who sees this differently — and what do they see that we don’t?
I often say to leaders:
“Strong teams hunt for exceptions, not just patterns that flatter the first idea.”
When teams learn to look for what challenges their explanation, blame softens and system thinking increases. People stop protecting positions and start improving outcomes.
Step 4: Update the hypothesis — without ego damage
The final step is critical.
Updating the story must feel safe.
Model this language:
“Given what we’ve seen, our story needs updating.”
Use versioning:
- Version 1 of the story was X.
- Version 2, after more data, is Y.
Shift the focus away from personal failure:
“Nothing was a lie. We were each holding a partial picture.”
This protects identity while improving accuracy. It tells the team: we weren’t wrong — we were working with a draft.
Leaders who do this consistently are seen as more credible, not less.
What this changes inside teams
When leaders coach teams to treat explanations as hypotheses:
- Disagreement becomes safer.
- Blame loses its grip.
- Decisions improve under pressure.
- Learning speeds up during change.
Most importantly, people stop defending stories and start testing reality together.
That’s not a communication trick.
It’s a thinking discipline.
If you want your team to handle complexity without turning on each other, start here.
Teach them to slow the story, not the action.
Trust your team and make space for their best.
