RETHINK — Fixing Documentation as a Product Capability Across 200+ Products

______________________________________________________________________________________

Case Study Snapshot:

Across AspenTech's 200+ products, documentation wasn't just a content problem—it was a workflow problem. Users operating in complex technical environments couldn't reliably find the right answer at the right moment: content was fragmented, too long, outdated, and mismatched to user terminology. The result was a costly default behavior—"ask a senior engineer"—which drove long training cycles, slower workflows, errors, and heavy support load. I identified this gap while running new user sessions and partnered with the global documentation team to treat docs like a UX system: research-led, structured, and measurable.

The initiative delivered a documentation experience built around context and speed: contextual help panels embedded in workflows, inline tooltips at decision points, smart search with deep links back into the UI, troubleshooting playbooks, and task-based content designed for execution rather than reading. We also introduced LLM augmentation for faster retrieval and feedback loops for continuous improvement. Results were significant at portfolio scale: 40% reduction in support tickets, faster time-to-resolution, 10–30% NPS improvement, and smoother onboarding—transforming documentation from an afterthought into a true product capability.

______________________________________________________________________________________

Context:

Across AspenTech’s **200+ products**, documentation wasn’t just a content problem—it was a workflow problem. Users were operating in complex, technical environments where “getting unstuck” is part of daily work. Yet help content was fragmented across in-product help, web docs, PDFs, knowledge bases, and training modules—with no cohesive experience.

I identified the gap while running sessions with new users: onboarding pain and low adoption were being amplified by weak documentation discoverability. With an executive sponsor, this became a formal initiative: **RETHINK**.

Problem:

Users couldn’t reliably find the right answer at the right moment:

• Information wasn’t contextual to the workflow

• Content was too long, outdated, and mismatched to user terminology

• Search was poor and inconsistent

• There was little external discoverability (almost nothing on Google/YouTube)

So when users got stuck, the default path was: **ask a senior engineer**. That created real business cost: long training cycles, slower workflows, errors, renewal risk—and heavy support load.

Approach: I partnered with the global documentation team and treated docs like a UX system—research-led, structured, and measurable.

Research:

• Interviewed "17 novice + expert users"

• Ran "contextual inquiry" (“show me how you find help”)

• Conducted "usability testing" of the existing doc experience

• Analyzed "support tickets" to identify recurring failure patterns

  
  

Synthesis and artifacts:

• Journey map identifying where users fail and why

• Taxonomy and terminology alignment (how users search vs how content is labeled)

• Content model and a new information architecture

• Requirements for search + **LLM augmentation** to speed retrieval and improve relevance

We piloted, refined, and shipped a doc experience built around *context* and *speed*:

• "Contextual help panel" embedded in workflow

• "Inline tooltips" and “View Agent”-style explanations at decision points

• "Smart search" across in-app + web docs with deep links back into the UI

• "Troubleshooting guides" and decision-tree playbooks (“if this, then that”)

• "Convergence playbooks" for complex engineering scenarios

• "Related articles by screen/context" to reduce hunting

• A command-palette style entry point for fast access

• Feedback loops (“was this helpful?”) to drive continuous improvement

We also restructured content away from long manuals into "task-based docs" designed for execution, not reading:

Outcomes

• "40% reduction" in support tickets

• "Faster time-to-resolution" and less “ask a senior engineer” dependency

• "10–30% improvement in NPS"

• Smoother onboarding and higher confidence in complex workflows

Why it mattered:

RETHINK turned documentation from an afterthought into a "product capability": contextual, searchable, and embedded where decisions happen. The result was measurable operational impact—fewer tickets, faster self-serve resolution, and stronger customer sentiment—at portfolio scale.