The ‘Documentation Evangelist’ in Your Company (and How to Become One)

The Ghost in the Slack Channel

There is a specific kind of silence that kills companies. It isn't the silence of an empty office or a quiet focused team. It is the silence of a question asked in a public channel that nobody answers.

It hangs there. "Does anyone know why the billing service returns a 500 error on Tuesdays?"

Ten minutes pass. Then an hour. Then the person who asked the question sighs, closes their laptop, and goes to tap someone on the shoulder, breaking their flow and costing the company fifty dollars in lost productivity. This ghost is the accumulated debt of everything your team knows but hasn't written down.

It is a remarkably expensive ghost. The average employee spends 5.3 hours a week just waiting for information. They are sitting there, staring at a screen, unable to do their job because the knowledge they need is locked inside someone else's head. It is a tax on every project. It is the reason we miss deadlines. It is the reason we hate our jobs.

And into this void steps a figure who doesn't officially exist. They don't have a title. They don't have a budget. They are the Documentation Evangelist, and they are the only reason anything ever gets done.

The Resistance

The mistake we make is thinking that documentation is a job title. We hire a "technical writer," put them in a corner, and expect them to document a moving train. It never works. Hiring one person to be the "documentation person" is like hiring one person to be the "exercise person" for the entire office. They get fit; everyone else gets heart disease.

The true evangelist is a change agent. They are the person who realizes that spending 20% of the work week searching for internal information isn't just annoying; it is a market inefficiency that borders on negligence.

They don't do this because they love writing wikis. Nobody loves writing wikis. They do it because they hate repeating themselves. They do it because they have realized that the only way to scale a team is to scale the knowledge.

The Quiet Rebellion

This is not a role you get promoted into. It is a role you seize. It starts with a series of small, subversive acts.

You stop answering questions in private messages. When someone asks you how to set up the dev environment, you don't walk them through it. You write a guide, you put it in the repo, and you send them the link. You force the knowledge out of the oral tradition and into the artifact.

This is uncomfortable. It feels rude. But it is the only way to break the cycle. You are drawing a line in the sand. You are saying that knowledge is not a favor we trade; it is an asset we own.

You start to weaponize the pain. When a project goes off the rails because nobody knew the API had changed, you don't let the team shrug it off. You conduct a post-mortem. You calculate the cost. You show them the graph. Research suggests that successful organizational change rarely comes from top-down mandates; it comes from these kinds of grassroots movements. It comes from someone deciding to care when everyone else has decided to settle.

The Force Multiplier

The problem, of course, is that writing is hard. It is the vegetables of the software world. We know it is good for us, but we would rather ship code.

The smart evangelist doesn't try to force people to eat their vegetables. They try to make the vegetables taste like candy. They look for leverage. They look for tools that lower the friction of capturing knowledge until it is almost accidental.

This is where AI stops being a buzzword and starts being a teammate. We built Doc Holiday because we realized that the bottleneck wasn't a lack of desire; it was a lack of time. An AI can watch you work. It can listen to you explain the code. It can take that messy, rambling explanation and turn it into a structured guide.

It changes the economics of the problem. If documentation takes an hour, you won't do it. If it takes five minutes of reviewing a draft that an AI wrote for you, you might. The evangelist's job isn't to write the docs; it is to build the machine that writes the docs.

The Long Game

You will not get a bonus for this. At least, not immediately. The work of the Documentation Evangelist is a thankless grind of invisible labor. You are planting trees under whose shade you do not expect to sit.

But eventually, the culture shifts. Behavioral science tells us that if you make a behavior easy and you reward it, it sticks. You start to see it in the onboarding process. New hires aren't lost for three months; they are shipping code in week one. You see it in the slack channels, which are suddenly quieter, not because people aren't working, but because they are finding the answers themselves.

You have exorcised the ghost. You have built a team that doesn't just write code, but writes the history of the code. You have created a legacy of clarity. And that, more than any feature or product launch, is the thing that lasts.

‍