I help engineering teams build documentation systems that developers can maintain and users can navigate. I’ve worked across SaaS, healthcare IT, scientific instrumentation, and enterprise software, taking on projects that other writers find difficult: complex API documentation, legacy systems that need restructuring from the ground up, and documentation that has to scale without growing the team.
The gap between what engineers build and what users understand isn’t a writing problem. It’s a thinking problem. My job has always been to close that gap: understand how something works, understand what users actually need to know, and connect the two in the simplest, most durable way possible.
I run Green Mountain Docs, LLC as an independent consultant. I bring a systems perspective to every engagement. I’m not just writing words; I’m thinking about how the documentation scales, how it stays current, and how it fits the tools your team already uses.
Those aren’t vanity metrics: they’re what let a small team maintain documentation that used to require twice the headcount.
I’ve led editorial teams, built documentation systems from scratch, managed content migrations, and mentored writers who have gone on to lead documentation organizations of their own. I’m an editor, a strategist, and sometimes a translator between the people who build things and the people who use them.
My approach has kept pace with the industry. I work with modern toolchains and use AI-augmented workflows where they genuinely help rather than just adding noise. I care about documentation that works: findable, accurate, and written for the person who actually needs it, not for the person who built it.
Industries: SaaS · Healthcare IT · Scientific Instrumentation · Enterprise Software
Tools: MadCap Flare · OpenAPI / Swagger · GitHub · Confluence · DITA · Docs-as-code workflows · Claude AI