Everyone wants great internal docs to kill the endless Slack noise and status meetings. But internal documentation falls into the NMP category (Not My Problem).
Everyone uses internal documentation, but who owns it? I live in the docs world, and I've only known of a handful of people who owned internal docs full-time as part of their role.
Engineering leaders focus on improving hard metrics: performance, reliability, productivity. Who can blame them? If they show results, they get rewarded. If they don't, they get the axe. That's why they surround themselves with Datadog dashboards like they're aboard the Avengers' Helicarrier.
The immediate impact of documentation is notoriously difficult to measure, so it doesn't get prioritized.
Great engineers know documentation is important, but they only have time to solve documentation locally for their area. No global ownership of documentation means a terrible global experience.
Engineers don't have the time to work on an NMP project.
The average tenure in Silicon Valley is 2.1 years.
- The first 3–6 months you're ramping up, learning the people and systems
- The next 6–12 months you're working on your first projects
- The next 12–24 months you're fully ramped and hitting a nice rhythm (and probably taking more recruiter calls)
Now things have changed. Everyone sees that their expensive coding agents are choking on bad documentation. Token spend is going up, rate limits are getting hit, budgets are getting tightened, velocity is decreasing.
To repeat: everyone uses internal documentation, but no one owns it. Is the answer to deliver a top-down mandate to everyone?
A mandate is tough to sustain when people aren't staying in roles long enough to care. The answer is to start measuring documentation like everything else. Show the current state, address the issues, feel the immediate benefits, and gain the long-term compounding effects.
No more vibe checks on documentation. If the documentation impact on your team and coding agents is easily visible, accountability will follow.
I get why 2.1 years means there's no time for NMP projects. But typically founders, CEOs, and mission-driven employees think on long-term time horizons.
If you're not writing things down, you're basically saying you don't care about your velocity or think your company will be around for a long time.