Cut onboarding tickets by 60% and tripled adoption across 100+ teams
Scaled Autodesk’s internal developer portal documentation system
Principal Content Designer | 2021–Present

Context & Challenge
The Problem: Autodesk launched Beacon to unify service registration, documentation, and infrastructure modeling across 100+ engineering teams. Early adoption lagged due to inconsistent standards, fragmented contributor practices, and a lack of onboarding resources, creating friction and stalled efficiency.
My Role
Leadership: As Senior/Principal Content Designer, I led UX content strategy for Beacon, partnering with engineering leads, developer advocates, and platform PMs to create unified workflows, scalable documentation models, and cross-team contributor education.
Approach
- Standardized YAML workflows → unified 100+ teams
 - Built onboarding manuals → 60% fewer support tickets
 - Embedded docs in CI/CD → automated compliance
 - Presented to leadership → secured adoption
 
Impact
- 📉 60% fewer
tickets - 📈 3× catalog adoption
 - 👩💻 200+ engineers enabled
 
Deliverables
Tools
MkDocs (TechDocs) YAML Markdown Confluence Backstage
Leadership Contribution
Scaling documentation systems isn’t just about clarity. It’s about governance, enablement, and alignment—shifting content from support work to strategic impact.

