The Bandwidth Problem

Communication channels have limited bandwidth. Reality has high dimensionality. Transmission requires compression. Compression loses information. This single fact explains enormous amounts of miscommunication, coordination failure, and organizational dysfunction.

Everything important is too complex to communicate fully. You compress it into words, gestures, documents. The receiver decompresses. What they reconstruct isn't what you had.

The Bottleneck

Consider the bandwidth limits:

• Speech: ~150 words/minute, ~10 bits/second of semantic content
• Text: Reading ~250 words/minute
• Video: ~millions of bits/second, but semantic extraction is slow
• Experience: Living through something = very high bandwidth

Now consider what you're trying to transmit: years of experience, complex models, nuanced situations. The channel is far narrower than the content.

Every communication is lossy compression.

What Gets Lost

Context

You know the full context. You can only transmit a slice. The receiver fills gaps with their own context—which differs from yours.

Nuance

"It's complicated" compresses to "yes" or "no." Gradations flatten. Conditionals drop. The receiver gets a simplified version.

Tacit Knowledge

Much of what you know is tacit—you can't articulate it. Skills, intuitions, patterns. These can't fit through the language bottleneck.

Emotional Tone

Text drops tone. Email wars escalate because neutral text reads as hostile. The affective layer compresses badly.

Organizational Implications

Hierarchies

Information flows up hierarchy through compression. Each layer summarizes for the next. By the time it reaches top leadership, crucial detail is lost. Leaders make decisions on summaries of summaries.

Meetings

Ten people in a room means ten different models. Alignment requires transmitting models across bandwidth-limited channels. No wonder meetings feel unproductive.

Documentation

Writing things down is useful but limited. Documents compress knowledge. Readers decompress differently. "But the spec says..." disputes arise from decompression divergence.

Handoffs

When someone leaves a project, their knowledge must compress into handoff documents. Critical tacit knowledge often can't fit. Institutional memory leaks through bandwidth bottlenecks.

Mitigation Strategies

Increase Bandwidth

Face-to-face beats video beats phone beats text beats email. Higher bandwidth channels transmit more. Use the highest bandwidth available for important communications.

Shared Context

When sender and receiver share context, less needs transmitting. Build shared context deliberately. Team rituals, shared experiences, common frameworks.

Iterate

Single transmission rarely succeeds. Back-and-forth allows error correction. "What did you understand?" catches compression errors.

Show, Don't Tell

Demonstrations bypass language bottleneck. Code reviews beat documentation. Working prototypes beat specs. High-bandwidth experience beats low-bandwidth description.

Redundancy

Say important things multiple ways. Repeat key points. Redundancy corrects errors but costs bandwidth. Tradeoff.

Personal Implications

You're always compressing. Others are always decompressing with different contexts.

• Assume miscommunication. The default is lossy transmission. Verify understanding.
• Match channel to content. Complex emotional topics need high bandwidth (in person). Simple factual updates work low bandwidth (text).
• Build shared context. Investment in shared understanding pays returns in future communication.
• Expect frustration. The bottleneck is real. Perfect transmission is impossible. Lower expectations accordingly.

— Decoded by DECODER