%20(1).png)
It’s 09:17.
A patient is transferred from one unit to another.
The nurse is kind. Focused. Slightly rushed.
The handoff happens quickly. A few key points are shared. Others are implied.
Two minutes later, the receiving team asks three questions that should already have answers.
The patient watches the exchange.
No one is rude. No one is careless.
Still, something feels off.
Not unsafe.
But not smooth either
And that moment, small as it seems, becomes part of the patient’s experience.
Not because of what anyone did wrong.
But because of what didn’t connect.
When patient experience falls short, most organisations look in the same places.
Communication training.
Patient journey mapping.
Satisfaction surveys.
All useful. All necessary.
But often, not enough.
Because the issue rarely sits in how people speak to patients.
It sits in how work moves between professionals.
In the gaps between teams.
In the assumptions that go unchecked.
In the decisions that hesitate or travel too far upward.
Patient experience does not break in a single interaction.
It erodes across transitions.
And those transitions are not a people problem.
They are a coordination problem.
Fixing coordination does not require a full redesign.
It starts with small shifts in how teams think and act, in the middle of real work.
Three, in particular, show up again and again.
They are simple.
Often overlooked.
And when applied consistently, they change more than expected.
In fast-paced environments, certainty feels efficient.
“We already discussed this.”
“They must know.”
“It’s obvious what comes next.”
These phrases save time.
Or at least, they seem to.
But they come at a cost.
Because what feels obvious to one team is often unclear to another.
And what is assumed to be known is rarely verified.
That is how gaps appear.
Information is partially transferred.
Context is diluted.
Responsibility becomes blurred.
Not because people lack competence.
But because they rely on assumptions.
This gets worse when teams think in silos.
Each unit focuses on its own task, its own pressure, its own priorities.
The logic makes sense locally.
But the patient does not experience care in fragments.
Patients do not experience your silos separately. They experience the gaps between them.
Curiosity changes that.
It introduces a small pause.
Just enough to check what is actually needed for the next step to work.
Not more information.
Better-targeted information.
A simple practice makes this visible:
These questions take seconds.
But they reduce repetition.
They reduce back-and-forth.
They reduce the quiet friction that patients feel without being able to name it.
Curiosity does not slow care.
It prevents rework.
Healthcare teams carry strong expectations.
“This should have been done.”
“They always forget this part.”
“We shouldn’t have to deal with this.”
These reactions are understandable.
They come from a desire to do things well.
To protect patients.
To maintain standards.
But over time, they create something else.
Tension between teams.
Defensive conversations.
A quiet sense that “others” are the problem.
And in siloed environments, this intensifies.
Once teams stop seeing the pathway as shared work, it becomes easy to read every gap as someone else’s failure.
Learning slows down.
Because frustration points outward.
It rarely asks what in the system made this outcome likely.
Appreciation, in this context, is not about being positive.
It is about paying attention to what reality is showing.
Every repeated issue carries information.
A missing piece in a handoff.
A delay in a decision.
A misunderstanding between roles.
These are not random.
They are signals.
When teams shift from expectation to appreciation, they begin to ask different questions.
Not “who missed this?”
But “why does this keep happening?”
A simple ritual can support this shift:
This takes very little time.
But it changes the tone of conversations.
It reduces blame.
It increases shared understanding.
It reconnects teams to what matters.
Appreciation is not soft.
It is how systems improve.
When situations become complex or uncomfortable, escalation feels like the safest option.
“Let’s check with management.”
“This needs validation.”
“This is above our level.”
Sometimes, escalation is necessary.
But when it becomes the default, something else happens.
Decisions slow down.
Senior levels become overloaded.
Teams lose momentum.
And over time, a pattern sets in.
Wait before acting.
Defer instead of deciding.
Protect instead of moving forward.
In many organisations, this is reinforced by a top-down reflex.
Decisions travel upward by habit, not always by necessity.
Teams learn to wait.
Middle managers learn to check first.
Senior leaders end up carrying decisions that should never have reached them in the first place.
When every difficult decision moves upward, ownership drains out of the system.
This is rarely about willingness.
It is about clarity.
When ownership is unclear, escalation fills the gap.
Shifting away from this does not require pushing people to “take more responsibility.”
It requires making decision boundaries visible.
What can be decided at team level.
What truly needs escalation.
Under what conditions.
And one simple rule can change behaviour quickly:
If you escalate, come with a proposal.
Not a perfect answer.
But a point of view.
This changes the dynamic.
It keeps thinking close to the work.
It turns escalation into contribution, not transfer.
It helps leaders support instead of replace decisions.
Ownership is not about hierarchy.
It is about clarity.
When curiosity replaces assumptions, handoffs become clearer.
When appreciation replaces frustration, teams learn faster.
When ownership replaces reflex escalation, decisions move closer to where work happens.
None of this requires new structures.
None of this adds significant workload.
It changes how existing work connects.
And that changes the experience of both staff and patients.
Because what patients perceive is not your organisational design.
They perceive how smoothly things happen.
Whether information flows.
Whether teams seem aligned.
Whether decisions feel timely.
Every unclear handoff.
Every repeated question.
Every visible hesitation.
All of it becomes part of their experience.
Most organisations do not suffer from a lack of effort.
They suffer from friction that has become normal.
A handoff that always needs rework.
A cross-functional meeting where each team defends its own priorities.
A decision that keeps moving upward because nobody is fully sure who can hold it.
This is where silo thinking and top-down habits become visible.
Silo thinking breaks the pathway into pieces.
Top-down reflexes pull decisions away from the people closest to the work.
The result is predictable.
More coordination effort.
Less real coordination.
More escalation.
Less ownership.
More delay for teams, and more uncertainty for patients.
These issues are rarely solved through discussion alone.
People often understand the problem.
They just do not always see clearly how their own habits help sustain it.
That is where simulations can help.
Not as entertainment.
Not as a side exercise.
As a practical way to surface what daily work often hides.
Used well, they allow teams to work on very concrete situations:
What makes this powerful is not the format.
It is the visibility it creates.
In a realistic scenario, patterns become easier to see.
Where information gets lost.
Where teams optimise their part but weaken the whole.
Where roles are unclear.
Where decisions drift upward.
Where communication creates friction instead of clarity.
And because the situation is shared, it becomes easier to talk about what is really happening.
Not in theory.
Not through blame.
But through something people have just experienced together.
This is where many teams start to shift.
In healthcare settings, this kind of work has been used to strengthen communication, improve collaboration, and build a more shared language across teams. In one NHS Trust, the impact was visible beyond perception alone. Stress-related absence dropped significantly, which is a strong signal that better ways of working do not only improve coordination. They also change the day-to-day experience of teams.
It also helps turn reflection into action.
Instead of stopping at “we should communicate better,” teams begin to define:
Real progress often starts there. Not when people are told to collaborate better, but when they can finally see what gets in the way.
Patients do not see your organisation chart.
But they feel its effects.
In the smoothness of transitions.
In the coherence between professionals.
In the sense that things are moving forward.
Improving patient experience does not always require adding more.
Sometimes, it starts by changing how what already exists connects.
If these situations show up in your organisation, the next step is not a large programme.
It is to take one pathway, one team, and make these moments visible and workable in practice.
That is where change becomes real.
.png)
Development isn't decided once a year. What a development conversation contains, why it so rarely happens, and what actually builds capability at work.
We train managers alone, then ask them to succeed as a team. What clinical simulation teaches management training, in every sector.
When development, recruitment and performance stop building the capabilities you need, your competency framework may be the cause. Three shifts, one test.
