Week 26 Day 3: The Gap Between What You Said and What They Heard

Communication is not what you say. It is what the other person understands. You can be perfectly clear in your own mind and still create confusion in someone else's because they are interpreting your words through their context, not yours. The leader who says 'I was clear' after a handoff failure is confusing intention with impact. Clarity is not measured by what you meant -- it is measured by what they built.

Here is an exercise that demonstrates the gap. At your next team meeting, describe a project deliverable in two minutes. Be as clear as you can. Then ask each person in the room to write down what they understood the deliverable to be. Collect the answers. I have done this exercise with a dozen teams, and the result is always the same: the descriptions vary significantly, even when the team is experienced and the deliverable is straightforward. The variation reveals three types of gaps. Vocabulary gaps: the same word means different things to different people. When you say 'scalable,' the infrastructure engineer hears 'handles 10x traffic.' The product manager hears 'works for more customers.' The designer hears 'adapts to different screen sizes.' The word is shared, but the meaning is not. Assumption gaps: information you consider obvious is not obvious to everyone. You say 'build the reporting dashboard.' You assume it includes filtering, export functionality, and mobile responsiveness because those are standard. The developer assumes it means a read-only view with predefined reports because that is what the last dashboard was. Neither of you states the assumptions because both of you think they are obvious. Priority gaps: what you emphasize is not what they remember. Research shows that people retain about 10% of what they hear in a meeting. If you mentioned the deadline once and the feature requirements five times, they will remember the features but not the deadline. The gap is not about intelligence or attention. It is about the fundamental nature of human communication: every message is filtered through the receiver's context. Clean handoffs do not eliminate the gap -- they acknowledge it and create mechanisms to close it.

The communication gap is formalized in Shannon and Weaver's (1949) mathematical theory of communication as 'noise' -- any factor that causes the received message to differ from the sent message. In organizational contexts, Axley (1984) extended this framework beyond physical noise to include 'semantic noise' (differences in word meaning), 'contextual noise' (differences in background assumptions), and 'relational noise' (differences in trust and interpretation based on relationship dynamics). The vocabulary gap is documented in research on 'boundary objects' (Star and Griesemer, 1989) -- artifacts or terms that are shared across communities of practice but interpreted differently by each community. In cross-functional teams, key terms like 'done,' 'quality,' and 'scalable' function as boundary objects that feel shared but are not, creating systematic misalignment. Research by Donnellon, Gray, and Bougon (1986) on 'equivocal language in organizations' found that teams routinely use shared vocabulary to mask fundamental disagreement, creating what they call 'equifinal meaning' -- the illusion of agreement where none exists. The 10% retention statistic cited in level_2 is supported by Ebbinghaus's (1885) forgetting curve research, updated by Murre and Dros (2015), showing that retention of verbal information drops to approximately 20% within 24 hours without reinforcement. The implication for handoffs is that verbal-only communication is structurally insufficient for complex task transfer.