Semi-retired. Still consulting, still taking on projects.
Those aren't vanity metrics. They're what let a small team maintain documentation that used to require twice the headcount.
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.
After forty years in technical writing, I've stepped back from full-time work. I still run Green Mountain Docs, LLC. I consult with documentation teams, and I take on projects with a defined scope: documentation systems, editing, audits, style guides, AI-assisted workflows, and coaching writers.
I keep a short client list and work remotely, up to 25 hours a week. On every engagement I look past the words to the system: how the documentation scales, how it stays current, and how it fits the tools your team already uses.
I've led editorial teams, built documentation systems from scratch, managed content migrations, and mentored writers who now lead documentation organizations of their own. 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.