In a recent conversation, I caught myself explaining why I often snap photos of the whiteboard when I’m talking with stakeholders. I think in images. When communicating verbally, I’m searching for words to describe what I see in my mind.

However, I sometimes notice that people in the room aren’t following.

I learned that even the simplest drawing can go a long way toward getting everyone on the same page. And I struggle to think clearly if I’m only presented with words—I often need to pause the conversation and request that we draw something on the whiteboard so I can visualize it.

That realization led me to a bigger truth: written words, or even perfectly transcribed conversations, aren’t always enough. The words don’t always accurately represent people’s thoughts and feelings. 

When we reduce communication to text, we strip away tone, gestures, timing, and—most importantly—shared context. A stakeholder might say:

“Our customers order products…”
But what they see in their mind could be:

  • A busy storefront, customers lined up and paying at the counter
  • A call center with people taking phone orders
  • A web page form with a glowing “Place Order” button

Meanwhile, the developers listening may visualize something entirely different:

  • Database tables with rows and foreign keys
  • API endpoints and request payloads
  • Or even snippets of code spinning in their mental IDE

Sometimes the stakeholder doesn’t even see people at all—they see charts, revenue numbers, or trends.

And sometimes the developer doesn’t see tables or people—they see functions, loops, and conditionals.

Note: This is a great clip of an interview with Dr. Temple Grandin, author of Visual Thinking’s book.


No wonder we talk past each other.

That’s why voice, drawings, and shared experiences matter. They add the missing context that words alone can’t carry. A quick sketch on a whiteboard, a story told with emotion, or even revisiting an old conversation together can bridge the gap between what’s said and what’s understood.

Data is useful. Words are necessary. But neither alone tells the full story. It’s in the mix of voices, drawings, and context that true understanding emerges.

2 responses to “The Hidden Gap Between What’s Said and What’s Understood”

  1. […] Some of us “think in pictures,” some in words, many in blends, and some (as Temple Grandin has taught so well) think in particular visual categories. The point isn’t to pick a single mode; it’s to externalize how you think and let AI meet you there. That’s how we keep the spirit of agile’s “conversation” alive while increasing the fidelity of the artifacts those conversations produce. Think of the hidden gap between what’s said and what’s understood. […]

  2. […] the next move with greater context and more confident assurance? Recent Posts You Might Enjoy 👉 The Hidden Gap Between What’s Said and What’s Understood — How mismatched mental models derail teams (and how to close the gap). 👉 From Mimicry to […]

Leave a Reply

Trending

Discover more from Claudio Lassala's Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading