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

Kurly

What factors are contributing to the sudden 30% decrease in Kurly's Beauty+ subscription sign-ups since the latest app update?

Prepared by NextSprints

15 mins
Report an error
Data Analysis Problem Solving User Experience Beauty E-commerce Subscription Services User Retention Root Cause Analysis Subscription Models Beauty Tech App Updates
Product Management Root Cause Analysis Question: Investigating sudden decrease in beauty subscription sign-ups after app update

Introduction

The sudden 30% decrease in Kurly's Beauty+ subscription sign-ups since the latest app update is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term and long-term implications for the product and business.

I'll approach this problem by first clarifying key details, ruling out external factors, and then diving deep into the product, user journey, and metrics. From there, I'll form data-driven hypotheses, conduct root cause analysis, and propose validation methods and solutions.

Framework overview

This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.

Step 1

Clarifying Questions (3 minutes)

  • Looking at the timing, I'm thinking the app update might be directly related. Can you confirm when exactly the update was released and when the decrease was first noticed?

Why it matters: Establishes a clear timeline for the issue. Expected answer: The update was released on [date] and the decrease was noticed within [timeframe]. Impact on approach: Helps narrow down potential causes related to the update.

  • Considering user segments, I'm curious if this decrease is uniform across all user groups. Have you noticed any differences in the impact on new vs. existing users, or across different demographics?

Why it matters: Identifies if the issue is widespread or specific to certain user groups. Expected answer: The decrease is [uniform/varies] across user segments, with [specific group] being most affected. Impact on approach: Guides the focus of our investigation and potential solutions.

  • Given the subscription nature of the product, I'm wondering about the conversion funnel. Has there been a change in the number of users starting the sign-up process, or is the drop occurring at a specific step?

Why it matters: Pinpoints where in the user journey the problem is occurring. Expected answer: We've seen a [increase/decrease/no change] in users starting the process, with the main drop occurring at [specific step]. Impact on approach: Helps focus the analysis on specific parts of the user journey.

  • Considering potential technical issues, have there been any reports of app crashes, slow loading times, or other performance issues since the update?

Why it matters: Rules out or confirms technical problems as a contributing factor. Expected answer: We've [seen/not seen] an increase in [specific technical issues] since the update. Impact on approach: Determines whether to prioritize technical investigations or focus on other areas.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Mar 29, 2025