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

Wish

Why has Wish's customer support satisfaction score declined from 4.2 to 3.5 in the past quarter?

Prepared by NextSprints

15 mins
Report an error
Data Analysis Problem-Solving Strategic Thinking E-commerce Customer Service Retail User Experience E-Commerce Data Analysis Root Cause Analysis Customer Support
Product Management Root Cause Analysis Question: Investigating decline in Wish's customer support satisfaction score

Introduction

The decline in Wish's customer support satisfaction score from 4.2 to 3.5 in the past quarter is a significant issue that requires immediate attention. This 16.7% drop in satisfaction could have far-reaching consequences for customer retention, brand reputation, and overall business performance. To address this problem, I'll employ a systematic approach to identify the root cause, validate hypotheses, and develop both short-term and long-term 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 there might have been recent changes to the customer support system. Have there been any significant updates to support tools or processes in the last quarter?

Why it matters: Recent changes could directly impact support quality. Expected answer: Yes, a new ticketing system was implemented. Impact on approach: If confirmed, we'd focus on system transition issues.

  • Considering the scale of the drop, I'm wondering about staffing changes. Has there been any significant turnover or expansion in the customer support team recently?

Why it matters: Staff changes could affect support quality and consistency. Expected answer: There's been a 20% increase in new hires. Impact on approach: If true, we'd investigate training and onboarding processes.

  • Given the global nature of Wish's business, I'm curious about regional variations. Is this decline consistent across all geographic regions, or are some areas more affected than others?

Why it matters: Helps identify if the issue is global or localized. Expected answer: The decline is more pronounced in certain regions. Impact on approach: We'd focus on region-specific factors if confirmed.

  • Thinking about potential external factors, has there been any significant change in the volume or nature of customer inquiries during this period?

Why it matters: Changes in customer behavior could strain the support system. Expected answer: There's been a 30% increase in inquiries related to shipping delays. Impact on approach: We'd investigate the cause of these inquiries and how they're handled.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025