I proved this pattern in production at Zeta. During my sabbatical I built the checkers that automate it - a documentation health check that runs weekly against this site's own content, plus traceability, governance and release-notes checkers. See the checkers running →
Documentation Systems Leader
Currently consulting independently · 15+ years leading documentation functions in enterprise SaaS, fintech, and networking software
Building documentation systems that make complex products usable at scale
I've led documentation teams and built the AI-assisted editorial workflow they ran on, turning fragmented content efforts into a governed, measurable function that scaled with the product.
My focus is the operating model, the editorial standards, and the AI-assisted workflows that let a documentation team grow without growing headcount 1:1.
What I do
Documentation systems
I set the standards, governance models, and content architecture that let documentation teams operate at enterprise scale.
Developer experience
I own how developers experience documentation - structured API references, workflows, and content built into the engineering process.
Documentation at scale
I build the operating model that keeps documentation aligned with releases - structured workflows, governance, and AI-assisted systems.
Sabbatical project
During my career break, I built the checkers and designed the operating models I'd bring into a Senior Documentation Manager role on day one - reasoning forward from what I've already proven in production. Each card states what is built and what is still a model.
Documentation Health Operating Cycle
A weekly cadence - flag, triage, assign, re-check - that runs a team against documentation health data instead of a quarterly manual audit.
Checker built and running weekly against this site's own content; the team operating cycle is designed, not yet run with a team
Read the model →End-to-End AI-Assisted Publication Pipeline
Spec in, AI-assisted draft out, mandatory human review gate before anything publishes - and the link into ongoing health monitoring.
Built; one AI-drafted page merged through the PR gate on this site. Not yet run as a team workflow
Read the model →AI Governance & Review Operating Model
What AI owns, what the team owns, and what I own as manager - the accountability model that keeps AI-assisted documentation auditable as a team scales.
Compliance checker built; operating model designed, not yet run with a team
Read the model →Impact highlights
Reduced support dependency
Led the knowledge system redesign that improved discoverability and cut support tickets by 25%.
Read the case study →Standardized API documentation at scale
Set the API documentation standards and templates the team adopted, owning 300+ endpoints at a sustained 15-20 endpoint review cadence per sprint.
Read the case study →Scaled documentation workflows
Led the team's shift to AI-assisted editorial review, cutting documentation cycle time by 30-40% while keeping human sign-off on every release.
Read the case study →How I think about systems
Documentation, developer workflows, and operational knowledge often exist as disconnected layers. I design systems that connect them and make them scalable.
When documentation is designed as a system, it becomes infrastructure for product understanding, developer productivity, and customer self-service.
Featured case study
Zeta • Lead Information Developer
Building the knowledge base management system at Zeta
Product knowledge and process documentation were scattered across teams, making it difficult for employees to find reliable information or know what was current.
I owned and built a centralized knowledge base management system end-to-end - not just a set of articles, but the architecture, governance, and contributor model behind them.
I focused on:
- Designing the information architecture and taxonomy that made content discoverable across teams
- Building governance and contributor workflows so other writers could add knowledge without breaking structure
- Authoring 80+ troubleshooting guides and revamping 40+ for end-user self-service
- Establishing standards for knowledge organization that outlasted any single contributor
The system reduced support ticket volume by 25% and became the standing model the team operated against, not a one-time project.
Explore the case study →Why me
15+ years leading documentation functions
Across enterprise SaaS, fintech, and networking software, building and running teams, not just producing content.
Documentation as a governed function
Establishes the operating model, AI workflows, and metrics that let a documentation team scale without scaling headcount 1:1.
Cross-functional influence
Partners with Product and Engineering leadership to embed documentation into the delivery lifecycle, not bolt it on after.
Let’s connect
Open to roles in documentation leadership, developer experience, and product-aligned content strategy.