Lessons from aviation. Closed loop communication
In the world of aviation, certain mistakes are final. Flight manuals use a specific, clinical phrase for operating procedures that, if ignored, lead to "injury or death." Because flight controls, engine power, and hydraulic systems are so critical, pilots don't leave communication to chance.
They use a concept called Dual Concurrence—a closed-loop communication script where two crew members must explicitly agree before a critical system is touched. This isn't just a safety check; it’s a communication fail-safe that reduces the likelihood of fatal errors to near zero.
"You Have the Controls"
Imagine a noisy helicopter cockpit. The engine is roaring, and helmets with visors block your ability to see a teammate’s facial expressions. To pass the flight controls, we use a specific three-step loop:
Pilot 1: "You have the controls."
Pilot 2: (Ensures they have a physical grip) "I have the controls."
Pilot 1: (Confirms the transfer is complete) "You have the controls."
In a side-by-side setup, I’ll even hold my hands up visually to show I’ve let go. We don't assume the message was heard; we prove it.
Why Digital Teams are "Noisy"
You might not be flying a helicopter, but modern virtual teams operate in their own kind of "noise." Zoom windows are small, non-verbal cues are lost, and Slack notifications provide zero feedback on whether a message was actually understood.
Without a closed loop, we fall into the trap of declarative communication—we "announce" things and hope they land. To fix this, we can borrow the flight crew’s discipline.
The 4-Step Closed Loop
To ensure a message isn't just sent, but received, follow this framework:
1. Transmission: The sender communicates the message clearly.
2. The Echo: The receiver repeats the core details back in their own words.
3. The Seal: The sender confirms the interpretation is correct (or clarifies if it isn't).
4. Completion: The loop is closed only when both parties are in total alignment.
Put it Into Practice: The Alice and John Example
It can feel slightly formal at first, but in a high-stakes project, it’s a lifesaver. Here is how a Project Manager (Alice) might use it with a team member (John):
Alice: “John, I need the final report, the presentation slides, and the executive summary by Friday at 5 PM. Can you confirm you’re clear on those three items?”
John: “Got it. You need the full package—report, slides, and summary—ready for review by end-of-day Friday. Is that right?”
Alice: “Exactly. All three components by 5 PM. Thanks for the catch.”
John: “Understood. I’ll have them to you by then.”
In this exchange, John didn't just say "Okay." He echoed the requirements, allowing Alice to "seal" the loop. This eliminates the Monday morning surprise of: "Oh, I thought you just wanted the slides."
The Bottom Line
Closed-loop communication is the antidote to the fragmented, "thumbs-up emoji" culture of modern work. It moves us from the uncertainty of "I think I told them" to the confidence of "I know they understand."
Give this script a try in your next meeting. It might feel redundant for a moment, but it’s the only way to ensure your project stays on course.
