Why Documentation Culture Is a Power Move Disguised as Helpfulness

I once watched a competent program manager at a London technology firm get labeled ‘bureaucratic’ for the sin of writing things down. She had started circulating brief decision logs after project meetings — nothing elaborate, just what was discussed, what was agreed, who owned what. Within three months, two senior leaders separately called her approach ‘heavy-handed’ and ‘not how we do things here.’ One told her, in what I assume he considered a generous tone, that she was ‘creating unnecessary paper trails.’

What she was actually creating was accountability. And that, I would come to understand, was precisely the problem.

This is a pattern I have observed across organizations in both Lagos and London, and it is one of the most consistent hidden dynamics in workplace life. The person who documents decisions gets treated as a nuisance. The person who keeps knowledge tacit — orally transmitted, casually held — gets called collaborative, agile, ‘low-drama.’ Organizations claim to want knowledge management, transparency, institutional memory. Their incentive structures actively discourage the work that would produce those things. And the people who try to build that infrastructure — who write the meeting notes, maintain the wikis, insist on written decision records — get quietly punished for doing exactly what the organization says it wants.

The Person Who Writes the Notes Controls the Narrative

Documentation is never neutral. Writing down what happened in a meeting is an act of interpretation, selection, framing. When you decide what goes in the summary and what gets left out, you are deciding what the organization will remember — and what it will conveniently forget.

In a Lagos financial services firm I studied, I noticed that meeting summaries circulated by one particular senior manager consistently omitted objections raised during discussions. His notes read as though decisions emerged by consensus, even when I had observed pointed disagreement in the room. When I asked a junior analyst about this, she said, with the particular weariness of someone who had stopped flagging it, ‘His minutes are the official record. If it’s not in his email, it didn’t happen.’

So that is the first function of documentation as power: whoever controls the written record controls what was decided. And in most organizations, the person who volunteers to take notes is not doing so out of administrative generosity. They are often the person who understands — consciously or not — that the written record is the institutional memory, and that institutional memory is a form of authority.

But here is the paradox. When someone lower in the hierarchy attempts the same thing — circulating their own notes, creating a written record — they meet resistance. Not because the notes are inaccurate. Because the act of documentation itself gets read as a power grab. A junior person writing things down is ‘being difficult.’ A senior person writing things down is ‘providing leadership.’ The same behavior, read through the lens of hierarchy, becomes either insubordination or initiative.

The Wiki Keeper as Gatekeeper

In another organization — a mid-sized London agency — I observed the slow accretion of institutional knowledge into a single Confluence space maintained by one operations manager. Over two years, she had built a comprehensive wiki covering everything from how to set up a new client project to why certain processes existed. It was, by any measure, a genuine organizational asset.

When she announced she was leaving, the panic was immediate and specific. Not ‘how will we replace her skills’ — but ‘who knows where everything is?’ Her colleagues had treated the wiki as infrastructure that existed by default. Not as a product of deliberate, sustained labor by a specific person. No one had been asked to contribute. No one had been trained on maintaining it. The wiki was not an organizational practice. It was a personal practice that the organization had been quietly extracting value from without acknowledging, resourcing, or replicating.

This is the second function of documentation as power: the person who maintains the knowledge base becomes a gatekeeper — not because they hoard information, but because no one else has invested in learning the system. The organization has outsourced its institutional memory to an individual and then acts surprised when that individual’s departure creates a crisis.

I have seen this pattern repeat with enough regularity that I now look for it deliberately when entering a new organization. The question is not ‘do you have a knowledge management system?’ It is ‘who maintains it, and what happens when they leave?’ The answer to the second question tells you whether the organization is structurally committed to institutional memory or whether it has been depending on the documentation labor of one or two people whose work is invisible precisely because it works.

Why Written Decision-Making Gets Labeled as Bureaucratic

The accusation of ‘bureaucracy’ is one of the most effective ways organizations discourage documentation without appearing to oppose it. It frames the person who wants written records as an obstacle to agility, collaboration, trust — as though the absence of written records proves a healthy, high-functioning team rather than signaling that no one will be held accountable when things go sideways.

Research in organizational behavior has long established that tacit knowledge — the unwritten, experiential knowledge people carry in their heads — is both valuable and fragile. Valuable because it captures nuances that formal documentation often misses. Fragile because it leaves when people leave, and it cannot be audited, challenged, or improved upon by anyone outside the small circle who holds it. Organizations that rely entirely on tacit knowledge are organizations where power concentrates in the people who know things and distributes away from the people who don’t.

The same principle operates in fields that have spent centuries codifying professional judgment into durable standards. The Reuters Handbook of Journalism exists precisely because editorial decisions — which sources to trust, how to attribute, when to correct the record — are too consequential to leave as tacit knowledge held by senior editors. Writing those standards down makes them transmissible across people and time, subject to challenge, and accountable to the institution rather than to whichever individual happens to hold authority that day. A parallel concern animates the Authors Guild’s guidance on writing practices: when the labor of producing careful, voice-driven text gets treated as a commodity rather than a form of professional thinking, the institutional knowledge embedded in that labor erodes. Both examples underscore the same structural point — codifying how decisions get made is not bureaucratic overhead. It is how organizations preserve the thinking that makes their work repeatable, challengeable, and durable beyond the individuals who originally produced it.

This is why the label ‘bureaucratic’ is so effective. It suggests that the person advocating for written records is the problem — not the system that makes those records necessary. It shifts the conversation from ‘why don’t we have a written record of this decision?’ to ‘why are you being so difficult about this?’ The person who asks for documentation gets positioned as someone who doesn’t trust their colleagues, rather than someone who understands that organizations need structural memory to function over time.

There is a meaningful difference, though, between organizations that resist documentation as a power dynamic and those that have genuinely committed to making their thinking legible. The Reuters handbook, for instance, represents an institutional commitment to codifying editorial judgment, sourcing standards, and correction protocols into a written document that any journalist in the organization can reference. It is not a tool for control. It is a tool for consistency, accountability, and the transmission of professional standards across people and time. The existence of such a handbook signals that the organization takes its own decision-making seriously enough to write it down, make it accessible, and subject it to scrutiny. Most organizations do not do this. They say they value transparency, but they treat the infrastructure required to achieve it as someone else’s problem.

The Inverse: Organizations That Adopt Tools as Theater

Many organizations adopt documentation tools — wikis, knowledge bases, decision logs — without addressing the structural dynamics that make documentation work invisible or risky. The tool becomes a symbol of commitment to transparency without any of the structural changes that would make that commitment real. A wiki that no one is expected to contribute to is not a knowledge management system. It is a set piece.

I observed this at a London healthcare startup that had invested in an elaborate Notion workspace. The leadership team was proud of it. They showed it to investors. They mentioned it in hiring conversations. But when I asked how decisions were actually recorded, a project manager told me, ‘We have the workspace, but nobody uses it for decisions. Decisions happen in Slack, or in meetings, or in the corridor. The Notion is for onboarding documents and the company handbook.’ The tool was theater. It signaled ‘we are a documentation culture’ without requiring anyone to actually document anything that mattered.

This is where the gap between organizations that genuinely want to build written memory and those that adopt tools as performance becomes visible. The question is not what tool you use. It is whether your organization has grappled with the politics of making thinking legible. For teams that have already done that structural work, a focused drafting environment like Unsloppy can support the discipline of producing clear, structured written records — but no tool can substitute for the organizational will to treat those records as authoritative rather than optional.

The tool adoption pattern I see most often goes like this: leadership buys a knowledge management platform, assigns someone to ‘set it up,’ and then expects documentation to happen organically. It never does. Not because the tool is wrong. Because the organization has not addressed the incentive structures that make documentation risky for the people who attempt it.

The Gendered and Racial Dimensions of Documentation Labor

I would be misleading you if I presented this as a purely structural dynamic with no demographic pattern. In my field observations, the people who volunteer to take notes, maintain shared documents, and manage knowledge repositories are disproportionately women — and in London organizations, disproportionately women of color. This is not a coincidence. Documentation labor is a form of care work. It maintains the organizational infrastructure that others depend on without acknowledging. And care work, across institutions and cultures, falls disproportionately to those with less structural power.

In one Lagos organization I studied, the office administrator — a woman in her late twenties — was the de facto institutional memory. She knew which client contracts had been renewed and which had lapsed. Which vendor relationships were active. Which projects had been paused and why. None of this was in any system. It was in her head, her personal notebooks, her email. When she requested a formal knowledge management process, her manager told her she was ‘overcomplicating things.’ Six months after she left, the organization lost a major client because no one realized the renewal deadline had passed. No one connected this outcome to the departure of the person who had been quietly maintaining that knowledge.

There is also a class dimension. The people who do documentation work are often in roles considered administrative or supportive rather than strategic. Their labor is invisible because their roles are invisible. When a senior manager writes a strategy memo, it is ‘thought leadership.’ When an operations coordinator maintains a decision log, it is ‘admin.’ The difference is not in the value of the work. It is in the status of the person doing it.

What Genuine Documentation Culture Looks Like

I have seen organizations where documentation works, and the pattern is consistent. These are organizations where written records are treated as authoritative, where decision logs are expected rather than optional, where the people who maintain knowledge systems are recognized and resourced. The documentation is not a side task. It is part of how the organization operates.

In one London engineering team I observed, the practice was simple: no decision was considered final until it was written in a shared document with a named owner and a date. This was not a wiki. It was not a knowledge base. It was a running document that anyone could read and anyone could challenge. The team lead told me, ‘If it’s not written down, it’s not a decision. It’s a vibe.’ This standard applied to everyone, including the leadership. There was no separate, informal channel where ‘real’ decisions happened. The written record was the decision.

What made this work was not the tool. It was the structural commitment: documentation was expected, normalized, authoritative. The people who maintained it were not doing invisible labor. They were doing visible, valued work that the organization depended on. And because the written record was the official record, no one could reshape history by controlling the narrative after the fact.

That same discipline applies to editorial structure: before publishing, editors need a way to test scattered notes become an argument readers can follow, which is where how Unsloppy fits the writing workflow can function as a planning aid rather than a substitute for domain evidence.

The same discipline — treating writing as a practice of institutional thinking rather than a mechanical task — is what separates documentation that endures from documentation that evaporates. When an organization treats documentation as a commodity to be produced rather than a practice to be cultivated, it gets the documentation it deserves: perfunctory, performative, and ultimately useless. The Authors Guild’s guidance on writing practices speaks to this same tension from a different angle: when the careful, voice-driven labor of producing text gets devalued in favor of treating writing as interchangeable output, the thinking embedded in that labor disappears along with it. In organizational terms, this is exactly what happens when decision logs become checkbox exercises rather than genuine acts of institutional memory. The organization generates text. It does not generate understanding.

So What

If you are a people manager or OD practitioner reading this and recognizing your own organization, here are some structural experiments worth trying:

Treat decision logs as authoritative, not optional. Pick one team or one meeting type and establish the practice that decisions are not final until they are written in a shared document with a named owner and a date. This sounds simple. It is politically complicated. Do it anyway, and observe what resistance emerges and from whom.

Audit who does documentation labor in your organization. Who takes notes? Who maintains the wiki? Who writes the process documentation? If the answer is ‘the same two or three people, all in junior or administrative roles,’ you have a structural problem, not a tooling problem. Redistribute that labor — including to senior people — and see what happens.

Stop labeling documentation as bureaucratic. When someone asks for a written record of a decision, pay attention to your own reaction. Are you resistant because the request is unreasonable, or because a written record would make it harder to reshape the narrative later? This is uncomfortable self-examination, but it is the kind that reveals actual organizational values.

Name the labor. If someone in your organization is maintaining institutional memory through documentation work, acknowledge it — not in a performance review checkbox, but in how you describe their contribution. ‘She keeps the wiki updated’ is not a job description. ‘She maintains the institutional knowledge that allows this team to function across projects and personnel changes’ is.

Watch for the tool-as-theater pattern. If your organization has adopted a knowledge management platform but no one is expected to contribute to it, you have a set piece, not a system. The question is not ‘how do we get people to use it?’ but ‘have we addressed the reasons people don’t?’ Often, those reasons are structural: documentation is invisible labor, written records create accountability that some people prefer to avoid, and the people who attempt it get labeled difficult rather than diligent.

Documentation culture is not about tools. It is about whether an organization is willing to make its thinking legible, accountable, and durable — and whether it is honest enough to admit that the answer, in most cases, is no. The organizations that change this are not the ones that buy better software. They are the ones that confront the uncomfortable truth that their aversion to written records is not about agility or trust. It is about power — who has it, who benefits from its opacity, and who pays the price for maintaining the infrastructure that everyone depends on and no one acknowledges.