Eats, Shoots & Leaves: The Art of Effective Communication in Distributed Teams
Words Matter—But They’re Only 7% of Communication
A panda walks into a café. He orders a sandwich, eats it, then draws a gun and fires two shots in the air.
"Why?" asks the confused waiter, as the panda makes towards the exit. The panda produces a badly punctuated wildlife manual and tosses it over his shoulder. "I'm a panda," he says, at the door. "Look it up."
The waiter turns to the relevant entry and, sure enough, finds an explanation: "Panda. Large black-and-white bear-like mammal, native to China. Eats, shoots and leaves."
This famous example from Eats, Shoots & Leaves is a perfect reminder that how we communicate is just as important as what we communicate. A misplaced comma changed the entire meaning of the sentence. Now, consider what happens in distributed, remote-first tech teams, where words alone make up only 7% of communication.
The 55/38/7 Rule
Albert Mehrabian’s 55/38/7 Rule states that:
• 55% of communication is nonverbal (body language, expressions, gestures).
• 38% is tone of voice (how we say things).
• Only 7% is words (the actual content of our message).
This explains why so many misunderstandings happen over text-based communication—email, Slack, Jira tickets, and even code reviews. Without tone and body language, our message can be misinterpreted.
The Challenges of Communication in Distributed Teams
Now, let’s apply this concept to a remote, multicultural, and diverse engineering team:
• Time Zones: Asynchronous work means messages are often read hours later, without real-time clarification.
• Cultural Differences: Directness in one culture may be perceived as rudeness in another.
• Tone Loss in Text: “Can we talk?” in Slack can feel ominous if there’s no additional context.
• Cameras Off on Calls: Without facial expressions, a simple comment can be misinterpreted.
• Feedback in Writing: “Looks good.”—Is that genuine approval or passive dismissal?
If 93% of communication is lost or distorted when body language and tone are missing, we need to rethink how we interact in remote work environments.
Lessons from High-Stakes Communication: Aviation & Emergency Response
Industries where miscommunication can be fatal—such as aviation, military, and emergency response—use a technique called “readback-hearback.”
Example:
Air traffic controllers don’t just give instructions and hope pilots understood them. Instead, pilots must repeat back the instructions to confirm accuracy.
ATC: “Climb to flight level 320.”
Pilot: “Roger, climbing to flight level 320.”
This eliminates ambiguity.
Tech teams can adopt this by:
• Encouraging clarification—“Just to confirm, you’re asking me to X, right?”
• Summarizing key takeaways from meetings in writing.
• Using structured formats for handovers, like “Next Steps: X, Y, Z. Does this look correct?”
Bridging the Communication Gap in Remote Teams
So, how do we counteract the missing 93% in distributed teams? Here are some strategies:
1️⃣ Use Multiple Channels to Support Different Learners
Not everyone processes information the same way.
• For visual learners: Diagrams, flowcharts, screenshots.
• For auditory learners: Voice messages, recorded explanations.
• For text-based learners: Summaries, bullet points, transcripts.
Example: Instead of sending a long Slack message with a complex idea, record a quick Loom video explaining it with visuals.
2️⃣ Encourage Active Clarification
Misinterpretations arise when people assume they understand.
• Instead of “Got it,” say “Just to clarify, we’re prioritizing X over Y, correct?”
• Instead of assuming feedback is negative, ask: “Do you mean X or Y?”
3️⃣ Overcommunicate, Especially in Writing
What feels like “over-explaining” is often just ensuring clarity in remote work.
• Provide context—“Here’s why we’re doing this.”
• Use explicit language—“By EOD, I mean 5 PM GMT, not local time.”
• Confirm understanding—“Does this approach make sense to you?”
4️⃣ Video Calls: Cameras On (When Possible)
If 55% of communication is nonverbal, cameras help recover that lost context. But be mindful—not everyone is comfortable on video all the time. Instead, encourage a mix:
• Cameras on for 1:1s and retrospectives (when emotions matter).
• Optional cameras for daily standups (focus on efficiency).
• Asynchronous video updates (for those who prefer recording over live calls).
5️⃣ Build a Culture of Psychological Safety
People hesitate to ask for clarification if they fear looking incompetent.
• Normalize asking, “Can you rephrase that?”
• Encourage feedback like, “What I heard was X. Is that correct?”
• Leaders should model transparent communication.
Final Thoughts: A Communication Checklist for Distributed Teams
Before you send that next Slack message, email, or pull request comment, ask yourself:
✅ Could this be misinterpreted? Add an emoji or extra context.
✅ Should I use a different format? Maybe a quick video explains it better.
✅ Am I assuming understanding? Ask for confirmation.
✅ Have I accounted for different communication styles? Not everyone learns the same way.
✅ Would a quick check-in avoid confusion later? A 5-minute chat can save hours of back-and-forth.
Communication isn’t just about what we say—but how, when, and through which medium we say it.
In a world of distributed teams, across time zones, cultures, and languages, effective communication isn’t just a skill—it’s a responsibility.
What strategies have worked for your team?