**Source:** https://heykiku.com/glossary/document-agency-processes

# Document Agency Processes

The problem with documentation isn't that agencies don't know they need it. It's that documentation has been defined as a project: a dedicated block of time, a blank page, a writing task that competes with billable work. Framed that way, **it always loses**. Client work is urgent. Documentation is important but never now.

The agencies that actually build documentation habits don't treat it as a separate task. They **capture at the moment of creation** — while they're explaining something to a new hire, doing a process for the first time, solving a problem they don't want to solve again. A two-minute voice note after a client call contains more useful context than a structured document written three weeks later from memory.

The medium matters because it determines who participates. When documenting requires sitting down to write, only people who write well and have spare time contribute. When it requires speaking a thought aloud, **everyone contributes**. The best knowledge capture systems meet people where they work, not where documentation theory says they should work.

The failure mode isn't missing documentation — it's documentation that exists but **can't be found**. Files in folders nobody navigates. Notes in a tool only one person checks. Processes written by one person in a format only they can parse. Capturing knowledge is only half the practice. The other half is making it accessible at the moment someone needs it, without requiring them to already know it exists.

## Related terms

- [Standard Operating Procedures](https://heykiku.com/glossary/standard-operating-procedures)
- [Tribal Knowledge](https://heykiku.com/glossary/tribal-knowledge)
- [Agency Playbook](https://heykiku.com/glossary/agency-playbook)
- [Internal Documentation](https://heykiku.com/glossary/internal-documentation)