Better technical communication,
at the level of systems and people.
Documentation problems are rarely just writing problems. I help SaaS and B2B teams fix fragmented, difficult-to-maintain documentation by addressing the information architecture, governance, tooling, ownership, and workflows that shape the system as a whole. This is particularly useful when documentation has grown faster than its structure, ownership is unclear, a migration is approaching, or teams are maintaining the same information in too many places.
I start with diagnosis before recommending solutions. I look at the documentation environment as a system: what content exists, who it serves, how it is structured, how it is maintained, and where the underlying process is breaking down. From there, the engagement can remain a focused audit, develop into a defined transformation project, or continue as fractional support.
I review the current documentation estate, including structure, duplication, content boundaries, ownership, workflows, tooling, governance, and migration readiness, then turn that assessment into a prioritized diagnosis and roadmap.
I redesign the operating model behind the documentation: information architecture, content ownership, standards, terminology, review rules, and the way documentation integrates with Product, Engineering, and release processes, resulting in a clearer target architecture and governance model.
I help plan and manage documentation migrations so teams do not simply reproduce old problems on a new platform, covering source audits, pruning, consolidation, target architecture, content mapping, migration planning, rollout, and post-migration cleanup.
For teams that need senior documentation ownership without a full-time hire, I can provide ongoing strategic support around architecture, governance, tooling, migration planning, contributor guidance, and periodic course correction.
My experience includes rebuilding and owning the SaaS Help Center at Language IO, covering information architecture, Zendesk Guide customization, API documentation, and governance; planning and overseeing a Word/PDF-to-DITA migration at GreenPowerMonitor, alongside structured authoring, onboarding, and localization workflows; and consolidating developer, customer, and internal documentation at Inbenta, using docs-as-code workflows for review, publication, and collaboration with developers. Across these roles, I have taken ownership of complex documentation environments, restructured them, and established the processes needed to keep them maintainable as products evolve.