All posts

There's a gold rush happening in enterprise AI right now. Every documentation tool is bolting on "AI-powered search" and calling it innovation. Notion has AI. Confluence has AI. Every wiki startup has AI.

Here's the thing: if the knowledge isn't in the system, it doesn't matter how smart your search is.

The documentation gap nobody talks about

Companies are sitting on a weird paradox. They have more tools than ever to organize information, and less of their critical knowledge is actually documented.

The stat is well-worn but still staggering: 70% of institutional knowledge is undocumented. That number hasn't moved despite two decades of wiki tools, knowledge bases, and documentation initiatives.

Why? Because the bottleneck was never the tool. It was the act of writing.

The real workflow looks like this

Here's what actually happens at most companies:

  1. Senior person does important process for years
  2. They get promoted, leave, or go on extended leave
  3. Someone asks: "Wait, how did Sarah handle the quarterly reconciliation?"
  4. Everyone scrambles to find a doc that doesn't exist
  5. The team spends weeks reconstructing the process through trial and error
  6. Someone says: "We should really document everything"
  7. A documentation initiative starts with great energy
  8. It dies within 6 weeks because everyone's too busy doing actual work
  9. Go to step 1

Sound familiar?

Where AI actually helps (and where it doesn't)

AI search on existing docs? Marginal improvement. If your Confluence is garbage, AI search just finds garbage faster.

AI that generates documentation from code or data? Useful for technical docs. Useless for operational knowledge, which is the stuff that actually matters when people leave.

AI that writes docs from prompts? Still requires someone to sit down and write a prompt that captures all the nuance. We're back to the "writing is the bottleneck" problem.

AI that conducts knowledge interviews? Now we're onto something.

The insight is simple: people can explain things verbally 5-10x faster than they can write them. And an AI interviewer can:

  • Ask the follow-up questions a junior person would ask but feel dumb asking
  • Identify gaps and ambiguities in the explanation
  • Catch edge cases by probing specific scenarios
  • Structure the rambling explanation into something organized
  • Do all of this in 15 minutes instead of 3 hours

This doesn't replace writing entirely. It replaces the hardest part: getting the knowledge out of someone's head and into a usable format.

The knowledge capture hierarchy

Not all knowledge needs the same treatment. Here's a rough hierarchy:

Tier 1: Critical processes with single-person dependency. If one person is the only one who knows how to do something important, that's an emergency. Capture this first, even if the output isn't perfect.

Tier 2: Complex processes with many edge cases. These are the ones that take months to learn. New hires struggle with them. They generate the most questions in Slack. Document the decision trees and exceptions.

Tier 3: Standard processes that multiple people know. These are important but less urgent. Multiple people can train new hires. Still worth documenting, but lower priority.

Tier 4: Processes that are well-documented already. Just keep them updated. Focus your energy elsewhere.

Most companies spend all their documentation effort on Tier 3 and 4, while Tier 1 and 2 go uncaptured. That's backwards.

What good looks like

A company with healthy knowledge management can answer "yes" to these questions:

  • If any single person left tomorrow, could someone else do their critical work within a week?
  • When a new hire has a question, is there a reliable place to find the answer (that isn't "ask Dave")?
  • When a process changes, do the docs get updated within a week?
  • Can someone find what they need in under 2 minutes?

If you answered "no" to even one of these, you have a knowledge problem. Not a documentation problem. Not a tool problem. A knowledge capture problem.

And that's a different thing to solve.


Understudy captures tribal knowledge through AI-guided conversations. Your experts talk through what they know, and Understudy produces structured playbooks your team can actually use. No blank pages. No writing required.


Related Resources

See how Understudy compares:

Get early access to Understudy

Turn your team's tribal knowledge into structured playbooks. Join the waitlist — we're onboarding teams now.