knowledge-ops

Topics in the source

• knowledge-ops
• Purpose
• When to use
• Workflow
• Scripts
• Quick example
• References
• Assumptions

Company SOP + internal runbook authoring, 5W2H completeness validation, and KB hygiene reporting for Head-of-Ops / Knowledge-Manager / TPM-Internal personas. An ops organization three years in accumulates a sprawl: 600 Notion pages, 200 Confluence runbooks, three Obsidian vaults, a Drive/SOPs/ folder, and a Slack #ops-questions channel that exists because nobody can find the canonical doc. Predictable failure modes: 1. No owner — 40% of SOPs name "the team" instead of a person. When the doc rots, nobody is accountable. 2. No last-reviewed date — a years-old vendor-offboarding SOP still references a procurement tool that was sunset over a year ago. 3. Vague success signals — runbook step 4 says "verify the service is up". A new operator can't tell what that means. 4. No rollback path — incident-comms cascade runbook tells you how to send the alert. It doesn't tell you how to retract it when the alert was wrong. 5. Orphan pages — half the KB has no inbound links. Nobody finds them via navigation; they only exist because somebody knew the URL. 6. Glossary drift — "CSM" means Customer Success Manager in three docs and Customer Solutions Manager in five. New hires guess wrong for six mo

This is an excerpt. Refer to the complete source and its current requirements.