The Shallow Document Problem
AI didn't break organizational communication. It just made it more visible.
I’ve spent years writing documents I knew most people would never read. Strategy docs, architecture white papers, product requirements, communication plans. I wrote them carefully. I formatted them properly. I put them in the right folder in Confluence and sent the right people a link.
And mostly, nothing happened. The org kept moving. Decisions got made. Projects shipped or didn’t. The documents sat there, timestamped evidence that the work of thinking had occurred.
When people ask whether AI is degrading organizational communication, I want to answer honestly: it’s accelerating a degradation that was already well underway. The more interesting question is why we didn’t notice sooner.
We were already not reading
Before AI entered the picture, document volume was already outpacing attention. The average knowledge worker was drowning in Confluence pages, Notion docs, Notion databases inside Confluence pages, Google Docs shared with edit access, Slack messages linking to all of the above. The backlog of “things I should read” was functionally infinite before anyone had access to a language model.
Here’s what that meant in practice. Most PRDs, white papers, and communication plans weren’t serving as transfer-of-understanding. They were serving as proof-of-work. The approval signature was the goal. The content was incidental.
Think about the last time a stakeholder pushed back on a specific sentence in a document you wrote. Not the summary. Not the conclusion. A sentence, mid-section, where the reasoning was soft. If that’s happened to you more than twice in a career, you’re ahead of most people. Usually what happens is: the doc gets circulated, a few people skim it, the right people click approve, and the work begins.
AI accelerated the production of these performance artifacts. The audience’s rational response, summarize it via AI before the meeting, is not a new failure. It’s a logical adaptation to content that was never genuinely information-dense. The AI-to-AI loop that people find so alarming, AI generates the doc, AI summarizes it for the recipient, is just the visible endpoint of a trajectory we were already on.
AI didn’t create the shallow document problem. It created conditions where pretending the problem doesn’t exist became impossible.
The slider intuition is wrong
The obvious response is calibration. Require more human effort in the writing. Better documents lead to better reading. Slide the dial back toward human-generated and we recover something we’ve lost.
This is wrong on two counts.
First, we already know human effort alone didn’t produce reading. The evidence is the decades of carefully written, professionally formatted, largely unread documents that preceded AI. If effort were the variable, those docs would have landed differently.
Second, the slider frames AI as the thing that changed. It isn’t. Accountability is the variable. The slider just adjusts the cost of producing cover.
Comprehension was always optional. Nobody got fired for approving a strategy document they skimmed. Nobody got called out for signing off on a PRD they didn’t fully understand. The document gave everyone cover, the author for having communicated, the approver for having reviewed, the organization for having a record. AI-generated documents provide the same cover at a fraction of the cost. That’s not a degradation. That’s an efficiency gain applied to the wrong problem.
Sliding the dial back toward human authorship doesn’t remove the optionality of comprehension. It just makes the performance more expensive to stage.
The document was never the unit of understanding
Ask yourself when understanding actually transferred in the organizations you’ve worked in.
Almost never in the reading of a document. It was the conversation after the document, the meeting where someone had to defend a position out loud, the design review where a tradeoff became unavoidable, the postmortem where a bad decision got traced back to a doc nobody had really engaged with.
The document was almost always downstream of the understanding, not the cause of it. The real cognitive work happened in the room, or on the call, or in the hallway. The document recorded a version of the conclusions that had already been reached.
What writing did was force the author to think. You can’t write a section on tradeoffs without resolving what the tradeoffs actually are. You can’t write a section on risks without deciding which ones are real. The artifact wasn’t valuable. The cognitive work of producing the artifact was valuable. That’s a crucial distinction.
AI removes that forcing function from the author. Summarization removes it from the reader. Both sides opt out of the cognitive work simultaneously. What’s left is the artifact, which was always the least important part.
Documents were doing two different jobs. We conflated them.
Documents weren’t a single thing. They were doing two genuinely different jobs, and we used the same artifact for both.
Job 1: Transfer understanding in the moment. Align the team on a decision. Get approval to proceed. Coordinate action across groups. This is the PRD, the architecture doc, the communication plan. The consumer is present-tense. The purpose is now.
Job 2: Preserve institutional memory across time. Capture decisions so the organization doesn’t have to rediscover them when someone leaves. This is the runbook, the architecture decision record, the post-mortem. The consumer is future-tense. The purpose is later.
These are genuinely different problems. Job 1 requires comprehension now, from specific people who need to act. Job 2 requires retrievability later, from people who don’t yet exist in the organization.
We used the same artifact for both and called it documentation. Then we complained that our documentation didn’t work. A PRD optimized for stakeholder approval is nearly useless as institutional memory. An architecture decision record optimized for future retrievability is nearly useless for driving present-tense alignment. They’re different documents serving different consumers on different timescales.
The shallow document failed at Job 1 because the conversation was always doing that work. But Job 2 is a legitimate problem, and it’s worth taking seriously on its own terms.
Design for verification, not for documents
If the document isn’t the unit of understanding, stop designing documents and start designing the moments where comprehension gets verified.
This isn’t a call for more meetings. It’s a call for smarter forcing functions. Three that work:
Decision forcing. Treat the AI draft as a starting position, not a deliverable. Before it becomes the record of alignment, run the room through explicit disagreement prompts. What’s the strongest argument against this? What did we decide not to do, and why? What would have to be true for us to be wrong? The document is kindling. The conversation is the fire.
Oral defense of tradeoffs. Anyone who signed off on a document can be asked, at any subsequent meeting, to explain the key tradeoffs and what was decided against. This doesn’t have to happen every time. It has to be possible every time. That possibility changes how people engage with what they’re approving.
Human authorship of the “what we didn’t do” section. This is the part AI reliably omits and the part that encodes real organizational thinking. What options were considered and rejected? What constraints ruled things out? What did we explicitly choose not to build? Require this section to be written by a human who was in the room. Protect it from AI generation. It’s where the real decision lives.
The point isn’t more process. Verification needs consequences. A norm without a consequence is decoration. If nobody ever gets asked to explain what they approved, the approval is still just cover. What changes is that misunderstanding now has a cost worth paying to prevent.
The memory problem is real. But we were solving it wrong.
Here’s the strongest objection to everything I’ve argued so far: if people leave the organization, their knowledge leaves with them. Documents are how you prevent that. Reduce the documents, lose the institutional memory.
It’s a real concern. But let’s look at the actual track record.
How often did the document actually prevent knowledge loss when someone left? In my experience: rarely. What happened was that the document existed in Confluence, nobody had looked at it in fourteen months, the person who wrote it was gone, and the context that made it meaningful was gone with them. The organization had a record. It didn’t have the knowledge.
A PRD buried in Confluence eighteen months after it was written, with no record of what changed after the doc was finalized, with no indication of which decisions held and which got reversed, is not institutional memory. It’s institutional archaeology. The knowledge was there in theory and gone in practice.
Here’s what AI changes about Job 2, in a way it doesn’t change Job 1. Retrieval and synthesis across a structured knowledge base is something AI does genuinely well. The human reader who was supposed to find and read that PRD almost never did. An AI assistant querying a well-structured decision log on behalf of a new engineer asking “why did we choose Postgres over DynamoDB for this service?” will surface the answer faster and more reliably than any wiki navigation ever did.
That changes what good institutional memory looks like. Stop writing it for a human reader who won’t show up. Write it for AI retrieval. The design properties are completely different.
Structured for retrieval, not reading. Decisions, context, tradeoffs, outcomes. Short, atomic, linked. Not prose paragraphs that require sequential reading to yield their meaning.
Decision-centric, not document-centric. The unit is a decision and its reasoning, not a document and its sections. The question a future employee asks isn’t “can I find the architecture doc from 2023?” It’s “why did we build it this way?” Those are different retrieval targets.
Queryable by AI, not navigable by human. The interface assumption flips entirely. You’re not building a wiki a human browses. You’re building a knowledge base an AI queries on behalf of a human asking a question in natural language. That means structure and tagging matter more than narrative flow. It means a 200-word decision record with clear metadata is more valuable than a 2,000-word white paper.
Living, not archival. Decisions get updated when they change. The system distinguishes between what we decided, what we decided later, and what we eventually reversed. Confluence graveyards fail here not just because they’re hard to find, but because nothing ever gets updated. Every doc reflects the thinking at the time of writing and nobody knows what changed.
I’ve built a version of this for my own work, a system I call Mindstore. The point isn’t the specific stack. It’s that the design assumptions are completely different from anything we’ve called documentation before. When I want to know why I made a past technical decision, I ask a question in natural language and get a synthesized answer grounded in the actual decision records. That’s a different tool than Confluence. It’s serving a different consumer.
A big caveat: this only works if the inputs are disciplined. Garbage in, hallucinated retrieval out. The cognitive work doesn’t disappear. It shifts from writing documents to capturing decisions at the moment they’re made. That’s still a human job. It connects directly back to the verification moments from the previous section. Decision forcing and oral defense aren’t just accountability tools. They’re also the mechanism by which real decisions get captured in a form worth preserving. The two halves aren’t separate solutions. They’re the same solution applied to different timescales.
Less documentation, not better documentation
If we get this right, the output isn’t more carefully written docs. It’s fewer docs.
The ones that remain will be shorter and harder to write. They’ll carry actual decisions, including what was decided against. They’ll be structured for the consumer they’re actually serving, whether that’s a human who needs to act now or an AI assistant helping a future employee reconstruct why the system works the way it does.
AI handles everything that was always performance. Human attention goes to the things where misunderstanding has a cost. Job 1 gets replaced by verification moments with consequences. Job 2 gets replaced by structured decision capture optimized for retrieval, not reading.
This will threaten people whose job looks like “producing documents.” That’s not a side effect. It’s the point. The shallow document problem persisted for decades because it served everyone’s interests except the organization’s. It gave authors credit for communicating. It gave approvers cover for reviewing. It gave the org a paper trail. AI just made the hollowness of that exchange too obvious to ignore.
The uncomfortable question
If accountability was always the missing variable, why didn’t we fix it before AI made it obvious?
The shallow document gave everyone cover, including leadership. A VP who approved a strategy doc without reading it can point to the approval. A team that shipped a feature nobody wanted can point to the PRD. The document was the alibi, not the evidence.
Fixing verification means removing the alibi. It means the person who approved the document has to be able to explain it. It means leadership doesn’t get cover from a doc they skimmed. That’s why this problem persisted. The people with the power to fix it were the people most protected by its existence.
AI accidentally gave us the tools to fix Job 2 correctly, if we design for the right consumer. What it can’t give us is the will to fix Job 1. That requires deciding that misunderstanding has a cost worth paying to prevent, and that the people responsible for decisions are actually responsible for understanding them.
That’s the conversation we should be having.