Healthcare Help systems Research

Providence Healthcare / ValueLens Help

Providence Healthcare · 2022–2025 · Senior UX Designer

Built a Help ecosystem from scratch for a financial analytics platform used across one of the largest healthcare systems in the country, turning a tool that users found frustrating and opaque into one they felt confident navigating independently.

ValueLens Help System

ValueLens is a financial reporting platform used by healthcare finance professionals across Providence Health. As the platform grew, so did the support burden. Users couldn't find answers on their own, onboarding new cohorts required heavy involvement from product and dev teams, and analysts were spending time being confused instead of doing their jobs.

I was brought in to research, design, test, and launch a complete Help ecosystem. The result was a suite of interconnected tools: a searchable Help Center, a context-aware sidebar, inline tooltips, first-time user onboarding modals, a Financial Definitions Library, and a headless CMS. Together they gave users everything they needed to help themselves.

  • NPS scores moved from broadly dissatisfied to satisfied post-launch
  • Faster onboarding across user cohorts of thousands at a time
  • Fewer basic support questions routed to product and dev teams
  • Non-dev content teams gained the ability to publish Help articles instantly, no code deployments required
↑ NPS Dissatisfied to satisfied in user perception of support
1,000s Users onboarded per cohort, faster than before
0 devs Required to publish or update Help content
Dozens Dev hours saved monthly via headless CMS adoption

Users needed help, but the system couldn't help them. Interviews revealed several critical issues:

The result: slow onboarding, repeated support tickets, and frustration among high-value financial analysts.

I led the end-to-end UX effort, from user interviews and contextual inquiry through information architecture, wireframes, prototypes, usability testing, and systems design. I also led CMS research and implementation guidance, and drove iterative improvements based on ongoing user feedback.

I started with deep discovery sessions with ValueLens power users, financial analysts, and reporting experts to uncover what "help" looks like in tools they enjoy, where they get stuck in ValueLens, their mental models for financial definitions, and what they expect during onboarding. Those insights shaped a holistic, interconnected help system built across six components.

ValueLens Help Center

Help Center

Designed a structured, searchable Help Center available from all pages, containing how-to guides, report workflows, troubleshooting steps, feature walkthroughs, terminology, and video content. Built on a CMS that scales easily as the product grows and is simple for content managers to update and tag to specific areas of the platform.

ValueLens On-Report Help Sidebar

On-Report Help Sidebar

Designed a persistent, context-aware sidebar that follows users across all reports. It gave users the ability to toggle overlayed Help Points, access deep articles specific to their current view, and submit tickets and feedback directly to the product team, without leaving the report.

ValueLens Help Points tooltips

Help Points (Tooltips)

Created an inline micro-explanation tooltip feature called Help Points, embedded directly in the interface. These explained calculations, filters, metrics, and terminology specific to the ValueLens platform, designed for quick scanning and reducing onboarding time by removing guesswork at the moment of confusion.

ValueLens First Time User Experience

First Time User Experience (FTUE)

Built a series of onboarding modals triggered on a user's first load of each report. They included welcome information, a video, links to interactive page tours, and help content specific to the loaded report, easing new users into a data-rich tool without requiring a live training session.

ValueLens Financial Definitions Library

Financial Definitions Library

Integrated a library of finance and clinical terminology used in ValueLens directly into the tool, pulled from trusted internal data sources. Replaced static PDF lists that users complained about or simply didn't know existed, making critical definitions findable in context, exactly when needed.

Headless CMS for ValueLens Help content

Rapid Content Creation via Headless CMS

To empower non-technical content creators, I evaluated CMS options and led the adoption of a headless CMS approved for internal use at Providence. This enabled real-time content editing without dev involvement, faster article creation, instant addition of video and audio, and version control. It removed a major bottleneck and saved the dev team dozens of hours per month.

  • NPS scores improved significantly post-launch, moving the product from broadly dissatisfied to satisfied
  • Faster onboarding across cohorts of thousands, with users reporting quicker time-to-confidence
  • Fewer basic support questions routed to product and dev teams
  • Content teams now publish and update Help articles instantly, no code deployments required

The ValueLens Help system became more than documentation. It became a teaching tool, a structured knowledge base, and an onboarding engine that transformed the platform from powerful-but-confusing into something users felt genuinely confident navigating. The architecture was built to scale long after my engagement ended.

Lessons Learned

  • Help is a product, not an afterthought. Treating it as a first-class design problem, with the same research, iteration, and systems thinking as the core product, produced results a bolted-on FAQ never could.
  • Users don't struggle because they aren't smart enough. They struggle because the product wasn't designed to teach itself.
  • Empowering content teams with the right tools multiplied the impact of the design work beyond the initial launch.

How about we have a chat?

Open to new opportunities — drop me a line.

Email me