Skip to content

Documentation Standards

🧷 If it isn't written down, it doesn't scale past one person's memory.

What Gets Documented

Artifact Where it lives Owner
Project README Project repo Delivery owner
Architecture / ADRs Project repo, /docs Tech lead on project
Client-facing scope & proposals Sales templates Sales/delivery owner
Internal SOPs & standards This knowledge base Whoever owns the process
Onboarding material Team Onboarding Ops

Writing Style

Follow the same voice as client-facing content (see Brand & Marketing): clear, structured, no hype — problem → approach → tradeoffs → outcome. Internal docs should be skimmable: headers, tables, and checklists over long prose paragraphs.