Portrait of Asbjorn Bjaanes
Asbjorn Bjaanes

Articles ·

Why We Don’t Understand Each Other -The Hidden Limits of Chunk Size in Team Communication

Most miscommunication isn’t about what was said, it’s about what was deleted.

Our brains can only hold 5±2 chunks of information at a time. That’s it. Exceed that, and our mind kicks into what NLP calls a transderivational search, an unconscious pattern scan, trying to make sense of what’s coming in based on past experience.

But here’s the catch:

When we can’t find a match, we don’t clarify, we delete.

It’s cognitive load management.

What’s a Chunk?

A chunk is a unit of meaning. A concept. A mental packet.

  • “Customer success” is a chunk.
  • “Optimize DNS resolution time” is a chunk.
  • “Trust” is a big, abstract chunk — open to wide interpretation.

When we communicate, we pass around these chunks. The listener processes them through their own domain knowledge, working memory capacity, and attention. Which leads us to…

Different Domains, Lower Chunk Tolerance

Here’s where it gets trickier:

When people from different domains communicate (e.g. product and compliance, engineering and product), their tolerance for chunk sizes drops as they are unfamiliar.

Why?

Because the mental reference maps are different. What feels like a simple chunk in one domain (“zero trust architecture”) is a total unknown in another. So instead of asking, the listener deletes. And what’s left is confusion, silence, or polite disengagement.

The more cognitive effort it takes to “decode” a message, the more likely it’s discarded.

Chunking Up, Down, and Sideways

To reduce deletion, we must manage abstraction with intent. This is where NLP’s chunking model becomes a practical tool:

Chunking Direction Eg. Chunk Up (Abstract) Connect ideas to purpose “Improve security, Build user trust, Protect brand equity” Chunk Down (Detail) Ground ideas in action “User trust, Fast login, Shorter auth cycle, Optimize token refresh” Chunk Sideways (Parallel) Explore related contexts “Trust in our app vs trust in fintech vs trust in healthcare platforms”

Skilled communicators navigate all three, depending on the audience’s domain and bandwidth.

What You Can Do

Here are five ways to reduce deletion and improve cross-domain communication:

  1. Respect chunk limits: Avoid dumping more than 3–5 ideas at once. Break it into digestible passes.
  2. Name / Label the chunk level: Signal whether you’re abstract (“vision”) or concrete (“bug report”).
  3. Bridge domains with “laddering”: Start where they are, then chunk up or down as needed.
  4. Use chunking to resolve conflict: Misalignment often isn’t disagreement, it’s abstraction mismatch.
  5. Surface what was deleted: Ask “What did you take from that?” to find where communication dropped off.

Common Scenario

Product Manager: “We want to strengthen trust in the platform.”

Developer (overloaded): What does that even mean? [Deletes it]

PM could chunk down: “Trust means no errors, fast loading, and transparency.”

Developer now has hooks. No deletion required. Execution can begin.

Final Thought

Most people listen not to understand, but to recognize.

When information doesn’t match their map, and they don’t have the bandwidth to resolve it, it gets deleted. Not because it’s unimportant. But because it’s not chunkable at their current resolution.

To lead across domains, you must:

  • Speak in chunks the other person can hold
  • Navigate abstraction intentionally
  • Become a manager of meaning, not just a messenger of ideas

What’s your take?

  • Where do you notice chunk overload in your organization?
  • Have you seen abstraction mismatches drive misalignment?
  • What do you do to chunk shift effectively between audiences?

Written by Asbjorn Bjaanes. Also published on Substack.

Reach out