Reduce documentation debt
Find the structural problems behind outdated, duplicated, incomplete, or hard-to-maintain content.
Building documentation systems that scale.
Helping software teams modernize documentation through scalable content architecture, practical AI workflows, and documentation operations.
20+ years
6 current products
25 Git repositories
100+ reusable snippets
The outcome
Documentation that is easier to create, maintain, publish, and use.
Build reusable architecture
Create content systems that support multiple products, outputs, audiences, and release cycles.
Modernize the workflow
Connect documentation with Git, Azure DevOps, publishing tools, analytics, and practical AI assistance.
Selected work
Three documentation systems. Three different kinds of pressure.
Modernization is rarely a single tool change. It is the work of untangling people, process, content, architecture, and delivery without bringing the whole machine to a halt.
Trintech
AI workflow modernization after a 66% team reduction
Redesigned planning and production workflows so one writer could continue supporting six enterprise products.
Read the case studyNextAxiom
Documentation rescue through reusable architecture
Rebuilt an aging Help system around reusable, context-sensitive content and Git-based maintenance.
Read the case studyEquinix
Documentation operations at enterprise scale
Built repository, publishing, localization, and delivery infrastructure for roughly 20 products and 15 writers.
Read the case studyDocumentation Health Check
Some documentation projects do not need more writers. They need better systems.
A focused assessment can reveal the hidden maintenance costs inside information architecture, content reuse, publishing, search, ownership, release workflows, and analytics.
See what the assessment covers
Information architecture
MadCap Flare structure
Content reuse
Publishing workflows
Git and governance
AI opportunities
Search and analytics
Documentation debt
How I think
Practical notes on the machinery behind good documentation.
Documentation debt
The content is not always the real problem
Why stale documentation often points to deeper failures in ownership, architecture, and release process.
Read the note →Content reuse
Reuse should remove work, not hide complexity
A practical way to think about reusable content without creating a maze only the original architect understands.
Read the note →AI workflows
Use AI where judgment is not the bottleneck
How AI can accelerate research and first drafts while keeping accuracy and ownership firmly human.
Read the note →About
A writer by craft. A systems builder by instinct.
My career has gradually moved from creating individual documents to improving the systems behind them. I have modernized legacy Help environments, designed reusable content architecture, administered Git repositories, managed publishing and localization operations, customized responsive HTML5 systems, and introduced AI-assisted documentation workflows.
I am most energized by difficult documentation environments: too many projects, too much duplication, unclear ownership, brittle publishing, incomplete product coverage, or a team being asked to do more with less.
MadCap FlareDocumentation operationsInformation architectureGitHTML/CSSAI-assisted workflowsLocalizationGoogle Analytics
Start a conversation
Need to untangle a documentation system?
I work remotely with software teams that need documentation modernization, MadCap Flare expertise, scalable operations, or a clearer path through accumulated documentation debt.