Knowledge Doesn't Survive the Trip (And Neither Does Spock)
Even if you haven’t watched the shows/movies, you probably know how Star Trek’s transporter works: Scotty beams you up, you step off the pad, you’re off to the holodeck for some R&R. It probably feels like magic✱ to people still commuting for work. Unless you’re one of the people who believe the original person is destroyed in the process — that what steps off the pad isn’t the person who stepped on. It’s a copy, built from the “same” pattern, carrying the “same” memories, convinced it’s the “same” person.
Knowledge communication works the same way. Bit of a conceptual roundabout from Star Trek to get here, but stick with me.
Knowledge is subjective, embedded in a specific mind’s fuzzy network of experiences, mental models, worldviews, and contextual relationships. You can’t just teleport it as-is.
Philosopher Michael Polanyi spent decades studying how scientists actually think, and concluded that all knowledge has a tacit dimension — “we know more than we can tell.” You know how to ride a bike, but try writing instructions that actually teach someone. Later, knowledge management scholars Nonaka and Takeuchi built an influential model proposing that tacit knowledge could be converted into "explicit knowledge" and transferred between people. It became the foundation of corporate knowledge management. But the conversion doesn’t hold up. What survives externalization is just information. The rich context that made it knowledge in the first place gets left behind on the transporter pad.
To communicate the electrical patterns bouncing around your grey matter, you have to put your thought on that transporter pad, beam it across the void of space between your mind and theirs, and hope the receiver can reverse-engineer it perfectly.
Spoiler alert: it can’t.
Every step of the encode > transmit > decode pipeline introduces its own loss.
Your knowledge of anything is tangled up in everything else you know. Your failures, your pattern recognition, years of accumulated context. Compressing all of that into language or diagrams or demonstrations means leaving pieces behind. All knowledge exceeds its own articulation.
And that’s just the first step. All we’ve tried to do is encode knowledge (or meat sacks) as information, and we’re already destined to fail, at least a little bit.
Luckily, we’ve gotten pretty good at moving bits from A to B2. Symbolic language, the printing press, telecommunications, the internet, and Star Trek’s transporter help us do it. The road has potholes, but we manage.
We have a big problem, though. The receiving transporter is running completely different software. What if it doesn’t rebuild every single atom in the exact right configuration? Likewise, the person receiving communication builds their own knowledge using their own mental models, their own experiences, their own cognitive machinery.
These problems compound. Encoding strips away context you couldn’t articulate. Decoding rebuilds with different machinery entirely.
So what actually helps? The instinct may be better encoding. More precise language, more thorough documentation, longer onboarding decks. But encoding optimization has diminishing returns when you’re polishing the input to a system you don’t control.
The highest-leverage move is learning the receiver’s system. A sender who understands the receiver’s existing models can encode for those models. Choose analogies that map to what they already know. Sequence ideas that build on existing scaffolding. Anticipate where the reconstruction will drift and preemptively correct for it. The best teachers figured this out. They study the student before they teach the subject.
Most advice on communicating knowledge optimizes the wrong end. Speak clearly. Write concisely. Organize your thoughts. All encoding refinements. The skill that actually changes whether knowledge survives the trip is modeling the machine on the other end. The better you practice the discipline of understanding your audience, their own mental models and past experience, the better you can encode your message for them.