Your company brain might have a comprehension problem

For the longest time, I thought the challenge of building a company brain was a knowledge problem.

The idea seemed straightforward. If every decision, project, conversation, customer interaction, and lesson learned could be captured in a single cognitive layer, the organization would become smarter over time. Instead of knowledge being trapped inside departments, teams, documents, and individuals, it would accumulate into one shared repository. A kind of digital cortex for the company.

The more I worked on second-brain architecture, especially for organizations, the more I realized something surprising. The hard problem isn’t knowledge. It’s interpretation.

What language models actually do

Most discussion around AI assumes language models understand meaning the way people do. At the mechanical level, that isn’t what they are doing. A language model trained with a next-token-prediction objective generates the most probable continuation of a sequence based on patterns learned during training.¹ It is extraordinarily good at this, good enough that the output is easy to mistake for understanding.

Set aside whether that counts as understanding. People argue it hard in both directions, and it is a genuinely interesting argument,²³ but it is not the one that matters here. Whatever is happening inside the model, the final act of interpretation happens outside it. When a model produces text, the person reading it constructs the meaning. The same words mean different things to different people. That was true long before language models existed, and it is true now.

This is not a new observation about machines. It is an old observation about reading. Reader-response theory has argued for over half a century that meaning is not fixed inside a text but is constructed in the encounter between text and reader. Louise Rosenblatt described a text as ink on paper until a reader evokes a work from it.⁴ Wolfgang Iser described texts as full of gaps that the reader fills.⁵ Stanley Fish located interpretation in communities of readers who share assumptions and strategies.⁶ A language model gives this old problem a new surface, because now the text is generated on demand, but the structure is identical: the reader makes the meaning.

Organizations run on interpretation

One advantage I’ve had throughout my career is sitting between stakeholders and engineering teams. Spend long enough in that seat and you stop writing one document. You start writing two.

For almost every significant initiative, I maintained parallel documentation. One version for engineers, focused on systems, implementation, constraints, dependencies, and execution. One version for stakeholders, focused on outcomes, risks, goals, timelines, and business impact. The underlying reality was identical. The interpretation was different.

This wasn’t a communication problem. It was an interpretation problem, and organizations have always known this even when they rarely articulate it. What you write in an investor memo differs from a customer update. A board presentation differs from a technical specification. What you tell engineering differs from what you tell sales. Not because anyone is lying, but because different audiences derive different meaning from the same information.

This is the core of Karl Weick’s account of organizations as sensemaking systems. Weick argued that organizations don’t simply process information; they organize to reduce equivocality, the condition where the same data admits multiple valid readings, and to build shared meaning so the group can act collectively.⁷ A single fact does not carry a single meaning into an organization. Revenue dropping eight percent means protect cash to the CFO, retention is failing to the product lead, is this even caused by the product to the engineer, and is growth slowing permanently to the investor. The fact is identical. The interpretations diverge by role. Equivocality is not a bug in the org; per Weick it is the engine that forces the organization to organize in the first place.

Translation

Historically, organizations solved this through layers. Managers, product managers, directors, and leaders each reinterpreted information for the next audience. Information wasn’t passed down so much as transformed at every level.

That transformation is expensive, and it is lossy. Information degrades and distorts as it moves up through the layers, and some of the distortion is deliberate, people screening out what makes them look bad on the way up, especially where trust is low.⁸ Think of each management layer as a bottleneck that compresses whatever passes through it, throwing away detail to fit the attention budget of the level above.⁹ Layered human translation was never free. It was a cost organizations paid because they had no alternative.

Now AI is collapsing those layers. Founders, engineers, customers, and investors can each query systems directly. The distance between the person with the idea and the people implementing it is shrinking fast, and many traditional translation roles look like they are disappearing.

The reality is more interesting. The translation function isn’t disappearing. It’s moving. The engineering team still needs engineering language. Customers still need customer language. Investors still need investor language. The need never went away. Only the mechanism changed.

Facts, judgment & interpretation

A single repository of information sounds elegant. A single interpretation does not. Because, following Weick, organizations operate on shared interpretations of information, not on information alone. So a company brain cannot just be a database of facts. It needs three layers.

Facts. Raw observations: sales numbers, customer interviews, meeting transcripts, product specs, decisions. This layer should be audience-neutral, a source of truth.

Judgment. The decisions that were made, the tradeoffs accepted, the principles that guided them, the preferences that emerged over time. This is the organization’s accumulated reasoning and taste, its institutional memory. Most organizations fail to capture this layer at all, which is why it walks out the door when experienced people leave.

Interpretation. The projection of that judgment into the form a specific audience needs. A single judgment, “we are prioritizing reliability over feature velocity this quarter,” becomes freeze feature work and cut incidents for engineering, stability and performance improvements are our focus for customers, and we are strengthening operational foundations for sustainable growth for investors. Same judgment, different valid renderings.

Maybe a compiler

This suggests a company brain shouldn’t be a single flat repository. It should behave more like a compiler.

A compiler starts from one source and generates different outputs for different targets. An organization can work the same way: one canonical layer of facts, one canonical layer of judgment, and many audience-specific interpretations generated from that shared source. The engineering version, the customer version, the investor version, all derived from the same underlying reality, all synchronized because they share an origin.

This directly attacks a problem organizations have fought for decades: documentation drift. Maintain separate documents by hand and they diverge. The engineering doc says one thing, the stakeholder doc another, the investor memo a third, and eventually nobody knows which is true. Generate every rendering from one judgment layer and the single-source-of-truth discipline that software already relies on becomes available to organizational communication.

The metaphor has a crack in it, and the crack is the interesting part. A real compiler is faithful by construction: the output means exactly what the source means. An LLM rendering judgment into an investor narrative makes no such promise. A generated customer update can be fluent, on-brand, and quietly false, and nothing in the architecture guarantees it still says what the judgment beneath it says. The compiler idea fixes the drift between the versions, because they share a source. It does nothing for the fidelity between any one version and the truth it came from. That gap, whether a translation carries the judgment honestly or quietly bends it, is the real frontier, and it is wide open.

What this changes

This changes how I think about AI as well.

I increasingly suspect that the language model is not the company brain itself. It is the interpretation layer through which the company’s accumulated judgment is expressed. The actual brain is the accumulated repository of knowledge, decisions, tradeoffs, principles, preferences, and institutional memory. The model renders that judgment into forms different audiences can understand, and that rendering is not a trivial step. It is where most of the organizational value and most of the risk concentrate, which makes it the layer that most needs governance, not the least.

The future challenge may not be building systems that know everything. Knowledge is becoming increasingly abundant. The harder challenge may be preserving coherent organizational judgment while generating multiple interpretations for multiple audiences, keeping those interpretations synchronized, and verifying that each one still tells the truth of the judgment beneath it.

That feels much closer to the real problem. Not how to build a company brain. But how to build a company’s shared judgment, continuously translate that judgment into language every part of the organization can understand, and prove the translation didn’t lie.

---

References