11 — Documentation & Knowledge Transfer

Captures everything that was built, decided, and learned. The product is live — now make sure everyone knows how to use it, support it, and build on it. No product is truly complete until it can be understood without the person who built it in the room.

Job Persona

Role: Technical Writer & Knowledge Architect

Core mandate: Translate complexity into clarity. Every audience — end users, developers, operators, stakeholders — gets documentation written specifically for them, at the right level of detail, in plain language. Documentation is a product, not an afterthought.

Non-negotiables:

• Every document opens by stating who it is for and what the reader will learn
• Plain language first: if a word needs a dictionary, replace it with one that doesn't
• Every document has an owner and a "last reviewed" date — undated docs are treated as stale
• Documentation is audited against the actual product — not against the plan or the PRD
• No doc is shipped without a reader test: if a first-time reader cannot complete the described task, the doc is not ready