Reimagining technical documentation as a core product experience

Challenge

Establishing UXR framework within a publishing system. And empower Technical Writers to launch documentation with a user-first mindset.

Context

Technical Documentation are help documentation written by Technical writers to introduce users to new products, fix issues and overall understand the product ecosystem.

Leadership & Scope:

• Established the UX program from the ground up to have standing ux studies for streamlined feedback. 

• Developed actionable heuristics for technical authors. Heuristics are now adopted by the organization with technical backing.

• Embedded UX KPIs into organizational planning.

• Translated user centered metrics into actionable insights for the Technical Writing Team.

• Discovered untapped topics like localization within Technical Documentation to increase user engagement. 

Impact

1. Directed the overhaul of the documentation's Information Architecture (IA) through large-scale research that led to tangible navigation and labeling improvements, resulting in a 30% reduction in developer time-to-find for Google Cloud docs (validated via usability benchmarking).

2. To solve the issue of experiencing Cloud docs as a product in conjunction with core products Spearheaded the  Cloud Architecture Center launch. This created a high-value strategic asset for sales enablement and significantly improved enterprise time-to-solution by organizing complex solutions around user goals, not product silos

3. Establishing the UX Program & Expertise: I became the official Point of Contact (POC) for Google Cloud Documentation UX with consulting in multiple projects with the help of office hours. 

4. Discovered the importance of localization during the process because of the text heavy nature of the product. Provided compelling evidence that enabled teams to reinvest their budgets on high value languages.

Difficulty

1. Usability Problems: Documentation was managed as a mere operational requirement rather than a strategic asset. This resulted in a fragmented legacy of uncoordinated guidelines, inconsistent labeling, and siloed pages. The lack of a unified design language made the documentation feel like a collection of separate products, ultimately causing significant user confusion in the user journey.

2. Organizational Metric Blind Spot: The team relied on a single, one-dimensional metric (e.g., page views) to measure effectiveness. This lack of a coherent performance narrative made it impossible to accurately assess impact and advocate for necessary resource investment.

3. The UX Feedback Vacuum: The documentation space lacked a foundational user-centric structure to help prioritize decisions of the content pages.

Methodology

My mandate was to fundamentally shift the organization's view of documentation from a collection of static pages to a critical service component of the developer experience. I established myself as the Principal UX domain expert and created the structural framework for success.

1. Establishing the UX Program & Expertise: I became the official Point of Contact (POC) for Google Cloud Documentation UX. I created and deployed a set of Documentation Heuristics —a foundational guide for technical authors to self-assess and improve the usability of their writing.

2. Driving Organizational Alignment: Successfully influenced the entire Technical Writing organization to prioritize user experience. I integrated UX goals directly into quarterly organizational planning by defining and making visible OKRs (Objectives and Key Results), CUJs (Critical User Journeys), Personas, and Success Metrics for documentation.

3. Foundational Research & Validation:

   • Unified Measurement Strategy: Authored and led a cross-functional team to define and implement multiple metrics to measure the effectiveness and performance of a document, moving beyond simple page views.

   • Systemic Usability Testing: Aligned with multiple Product UXRs to validate the new heuristics and the usability of core documents, introducing localization as a key variable in studies to target global market needs.

   • Continuous Engagement: Conducted aggressive bi-weekly office hours, along with comprehensive quarterly and yearly benchmarking studies, and created a canonical library of moderated and unmoderated test protocols to drive continuous

Impact & Outcomes

The research resulted in a concrete shift in investment, organizational structure, and information delivery, solidifying documentation as a strategic asset.

• Directed the overhaul of the documentation's Information Architecture (IA) through large-scale research that led to tangible navigation and labeling improvements, resulting in a 30% reduction in developer time-to-find for Google Cloud docs (validated via usability benchmarking).

• To solve the issue of experiencing Cloud docs as a product in conjunction with core products Spearheaded the  Cloud Architecture Center launch. This created a high-value strategic asset for sales enablement and significantly improved enterprise time-to-solution by organizing complex solutions around user goals, not product silos

• Discovered the importance of localization during the process because of the text heavy nature of the product. Provided compelling evidence that enabled teams to reinvest their budgets on high value languages.

• Embedding a UX Culture: Provided compelling evidence that enabled teams to reinvest their budgets with confidence, dedicating resources to prioritized UX topics that were proven to drive user success.

  • UX became a center with opening of multiple headcounts based on this research and standing office hours

  • Built a democratized UXR feedback system for tech writers with heuristics and continuous research cadence