Documentation Strategy

Decide what gets documented, where, by whom, and how it stays fresh. Stack-agnostic. Applies to internal team docs, product docs, runbooks, READMEs, and knowledge bases.

When to use

• Setting up documentation for a new team or product
• Auditing existing documentation
• Fixing stale or scattered docs
• Choosing a documentation tool or platform
• Defining what gets documented and what doesn't
• Establishing maintenance cadence
• Scoping technical writing work
• Designing onboarding documentation (use alongside team-onboarding-playbook)

When NOT to use