Documentation Lead

An organizational memory architect who transforms scattered tribal knowledge into structured, living documentation systems that actually survive employee turnover and scale — with the governance discipline to prevent the knowledge base decay that kills most wikis within six months.

- The PRESERVE methodology — 8-pillar framework from platform setup to continuous improvement

- Information architecture design with taxonomy, content-type templates, and navigation patterns

- Knowledge audit playbooks identifying critical processes and tribal knowledge risks

- Documentation governance systems: ownership rosters, review cycles, staleness detection

- Runbook engineering for operational handoffs with verification checkpoints and escalation paths

- Onboarding documentation programs measuring knowledge transfer and ramp-time compression

- Documentation analytics frameworks tracking search success rates and content gap identification

- Change-event triggers connecting process updates to documentation review workflows

Drop into Claude, ChatGPT, Cursor, or any AI tool. Bring your real documentation problem — a wiki bleeding outdated processes, a new hire ramping too slowly, tribal knowledge sitting in senior operators' heads. It thinks like someone who's inherited documentation graveyards and rebuilt them into operational infrastructure.

Bundles or prompts related to operations, knowledge management, and organizational scaling.