All Articles
A weekly newsletter on high-stakes communication — drawn from 27 years in operating theatres, military medicine, and hospital leadership. One story. One pattern. One thing you'll use.
Each piece below began as a newsletter issue — and earned a permanent home here.
The Phrase That Bought Us Three Minutes
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
T is for Trap Errors — the sixth letter in the SCRIPTED framework for communication under pressure
The surgery had gone well.
Two and a half hours of concentrated effort. The team was calm, coordinated, quiet in the way that good teams get quiet when everything is working. The patient had started breathing on her own — a good sign. We were close.
The surgeon announced his last three stitches. Three minutes to closure.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
From experience I knew the numbers. Cut the anaesthetic vapour — Sevoflurane — now, and she wakes in five minutes. The timing would be perfect. Patient conscious, comfortable, ready for recovery.
So I announced it out loud.
"Cutting off the Sevoflurane. She will be awake in five minutes."
Everyone heard it. The surgeon heard it.
Two minutes passed.
Then he said it.
"I think I need to resuture. The closure needs to be better."
My stomach dropped.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
She was not awake yet — but she was close. Light breathing. Heart rate climbing. Blood pressure rising. I could feel her coming back. Another minute and she would have moved.
I turned the Sevoflurane dial up immediately. The vapour returned. She settled. The surgeon resutured. The patient felt nothing, knew nothing, woke up in recovery asking for water.
But here is what stayed with me long after that case closed.
If I had cut the vapour silently — without announcing it — the surgeon would not have known her timeline. He would have made his decision to resuture without that information. By the time he asked for more time, it might have been too late.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
One sentence changed the outcome.
Not a protocol. Not a checklist. Not years of experience.
Just a deliberate announcement before a time-critical action.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
What is an error-trap?
An error-trap is a phrase deliberately designed to catch mistakes before they happen.
Not after the drug is given. Not after the email goes out. Not after the decision is announced. Before.
The best communicators build error-traps into their language as a matter of habit — not because they are uncertain, but because they understand something important about high-stakes situations.
Under pressure, individuals miss things. Systems catch them.
An error-trap turns your individual action into a system. You announce what you are about to do. You state the consequence or timeline. You create a window for someone else to raise a flag. Three seconds of deliberate pause — and suddenly you have four eyes on the decision instead of two.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The pattern — three elements
Every effective error-trap has the same structure:
One — state the action clearly. Not "I am going to do something now" but the specific action. Drug name. Decision. Communication. Whatever is about to happen that cannot easily be undone.
Two — state the consequence or timeline. "She will be awake in five minutes." That one phrase told the surgeon everything he needed to recalculate his own timeline. Without it he was making decisions in an information vacuum.
Three — invite concerns explicitly. "Any concerns?" is the most powerful three-word phrase in high-stakes communication. It does not just signal openness — it actively creates a moment where speaking up is expected, not exceptional.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Together the pattern sounds like this:
"I am giving succinylcholine — that is the muscle relaxant — to facilitate intubation. Any concerns?"
"I am cutting the Sevoflurane. She will be awake in five minutes."
"I am about to send this announcement to the entire hospital staff. It goes out in three minutes. Anyone see a problem?"
Same structure. Same three seconds. Different context, same principle.
The workplace parallel
Error-trapping is not a clinical technique. It is a communication technique that happens to save lives in clinical settings.
In any environment where decisions carry consequences — a hospital ward, a boardroom, a project team — the same pattern applies.
Before a major financial decision: "I am approving this expenditure. Once released it cannot be recalled. Does anyone see something I am missing?"
Before a critical communication: "I am about to send this to the entire organisation. This is what it says. Any concerns with the timing or the message?"
Before executing a significant change: "We are about to implement this. Here is what changes from this moment. Last call for concerns."
The phrase "any concerns?" is the error-trap. It signals that you are open to input. It creates the space for someone to raise a flag who might otherwise have stayed silent — out of deference, out of uncertainty, out of the assumption that you already knew what they knew.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Most communication failures are not failures of knowledge. They are failures of the window — nobody created the moment where the right person could speak.
Error-trapping creates that moment deliberately.
The cultural challenge
There is one condition that determines whether error-trapping works.
The team has to feel safe enough to use the window you create.
If speaking up is seen as questioning authority — if raising a concern is perceived as incompetence or insubordination — people will stay silent even when you invite them to speak. The announcement creates the opening. The culture determines whether anyone walks through it.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This is why T cannot stand alone in the SCRIPTED framework.
T works because of C — Confirmation — which establishes that individual voices matter and silence is never assumed to mean agreement.
T works because of I — Inquire — which normalises the act of asking before acting, regardless of hierarchy.
The framework is interconnected. Each letter reinforces the others. Error-trapping language is a habit. But a habit practised in a culture that punishes honesty is just noise.
Build the language. Build the culture alongside it.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The one thing to do this week
Before your next high-stakes action — clinical or organisational — announce it out loud.
State what you are doing. State the consequence or timeline. Then pause for three seconds.
Notice what happens in those three seconds.
Someone may say nothing. That is fine — you have still created the record, the shared understanding, the moment of alignment.
Someone may say something. And that something may be exactly what you needed to hear.
The surgeon used that window.
Three seconds of silence.
And the patient felt nothing.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
T is the sixth letter in the SCRIPTED framework for communication under pressure. Each week I reveal one letter — one strategy, one clinical story, one pattern you can use. Subscribe to Communication Under Pressure at
https://lastvoiceyouhear.com
If you have not yet found your biggest communication gap — take the SCRIPTED Communication Audit. Eight scenarios, two minutes, your full profile unlocks on screen instantly.