Knowledge & documentation
Runbooks, ADRs, onboarding tracks — written, current, useful.
Knowledge & documentation is runbooks, adrs, onboarding tracks — written, current, useful.
Why this work matters
The fastest way to lose institutional knowledge is to not write it down. The second fastest is to write it down and let it rot. Most docs are out of date within a quarter; we fix the process, not just the docs.
The work, in detail.
- Operational runbooks per service
- Architecture decision records
- Onboarding tracks (engineering, ops, support)
- Internal AI search over docs
- Decision logs
- Customer-facing API docs
- →Runbook per critical service
- →Architecture decision repository
- →Onboarding tracks
- →Internal AI search over docs
Real documentation, not 'someday' artifacts. Runbooks that work at 3 AM, onboarding tracks that get a new hire shipping in week 2.
The approach.
Docs in the repo
Markdown next to code. Updated in the same PR as the change. Stale docs fail review.
Searchable + AI-assisted
Internal AI search over docs + Slack history. New hires get answers in 30 seconds instead of 30 minutes.
Onboarding as code
First-week, first-month, first-quarter checklists per role. Measurable onboarding speed; new hires shipping in week 2 instead of month 2.
More from Software Management
The cost of waiting
is your competitor.
Every 90 days you delay is 90 days of authority compounding for someone else. Get the audit. See the math. Then decide.