Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

Epic Systems

After Epic moved to quarterly releases, customer adoption of new features fell from 40% to 25%. What is the root cause?

Prepared by NextSprints

13 mins
Report an error
Root Cause Analysis B2B Metrics Systems Thinking Healthcare Enterprise Software Health IT Root-Cause-Analysis Epic-Systems Enterprise-Software Release-Management
Product Management Product Root Cause Analysis Question: Epic customer feature adoption after quarterly releases

Introduction

Epic has moved its software releases from roughly every 18 months to every three months, according to presenters at its 2026 user group meeting, with each quarterly release now carrying about as many enhancements as an old 18-month release. Epic also tracks how much of its recommended functionality customers turn on through its "Gold Stars" programme, and reported 35,000 Gold Star features turned on last year. The prompt: after the switch to quarterly releases, the share of new features that customers turn on within six months of release fell from 40% to 25%. What is the root cause? This is hard because the "users" are health system IT and clinical teams, and adoption depends on their capacity, governance and trust, not just on the software.

Framework overview

I'll clarify the metric, rule out external factors, understand the adoption journey, break down the metric, gather data, form and test hypotheses, and close with a resolution plan.

Step 1

Clarifying Questions (3 minutes)

  • How is adoption measured?

  • Hypothetical answer: The share of new optional features (not automatically on) that a customer enables within six months of having the release installed.
  • Impact: The denominator grew a lot with faster releases.
  • Has the number of features per year changed?

  • Hypothetical answer: Yes; annual feature volume roughly doubled.
  • Are all customer types affected equally?

  • Hypothetical answer: Unknown.
  • Is the drop in "features turned on" or in "share of features turned on"?

  • Hypothetical answer: Absolute features turned on per customer rose slightly; the share fell.
  • Impact: Customers are adopting more, but not keeping pace with supply.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Oct 31, 2026