I build systems that make knowledge helpful.

The Problem: Documentation was siloed in a legacy on-premises CCMS that couldn't integrate with modern delivery systems or AI-assisted tools, creating a growing bottleneck as the product portfolio expanded.

The System: Led end-to-end migration of 20,000+ DITA XML topics from the legacy DITAToo platform to SaaS Heretto — building an API-driven, single-source-of-truth content layer designed for structured delivery.

The Result: Content is now API-accessible to AI chatbots, voice bots, and support ticketing systems — transforming a static documentation library into a live input layer for AI-assisted customer support.

The Problem: A lack of high-fidelity data made it impossible to identify systemic bottlenecks, plan capacity accurately, or demonstrate the team's output to leadership.

The System: Architected a custom Jira-based project management ecosystem from the ground up to capture real-time team velocity, throughput, and capacity data across a globally distributed team.

The Result: Transformed a reactive operation into a data-driven one — establishing clear baselines for quarterly planning, enabling defensible resource requests, and making the team's work visible to stakeholders.

The Problem: Legacy publication cycles carried excessive cross-functional overhead and hard dependencies on other teams, taking 2–3 weeks to ship even minor content updates.

The System: Reengineered the end-to-end publication workflow to remove external dependencies and give the documentation team direct ownership of releases — a true continuous delivery model.

The Result: Reduced the publication cycle from 3 weeks to a single day. Content now ships at the speed of the product, not the speed of a cross-functional scheduling queue.

The Problem: Severe team attrition created dangerous single points of failure across critical documentation functions, placing upcoming product launch timelines and compliance requirements at risk.

The System: Implemented cross-training frameworks to maintain coverage during the gap, then executed a strategic hiring effort — two writers positioned specifically to eliminate the single-contributor dependencies that had made the team fragile.

The Result: Maintained 100% operational continuity with zero launch delays throughout the attrition period. Rebuilt team capacity to a stronger and more resilient foundation than before.