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

Too Good To Go

Why has the average number of meals saved per user on Too Good To Go declined from 3 to 2 per week since the latest app update?

Prepared by NextSprints

12 mins
Report an error
Data Analysis Problem Solving User Experience Food Tech Sustainability Mobile Apps Root Cause Analysis User Behavior Sustainability Food Tech App Metrics
Product Management Root Cause Analysis Question: Investigating Too Good To Go app update impact on meal saving metrics

Introduction

The decline in average meals saved per user on Too Good To Go from 3 to 2 per week since the latest app update is a critical issue that demands immediate attention. This decrease directly impacts our core mission of reducing food waste and affects user engagement, potentially leading to reduced retention and revenue. I'll approach this problem systematically, focusing on identifying the root cause, validating hypotheses, and developing both short-term fixes 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 the app update might be directly related. When exactly was the latest update released?

Why it matters: Establishes a clear timeline for the issue. Expected answer: Within the last 1-2 months. Impact on approach: Helps narrow down potential causes related to the update.

  • Considering user segments, I'm curious if this decline is uniform across all user types. Have you noticed any differences in the impact on frequent vs. occasional users?

Why it matters: Identifies if the issue affects all users equally or specific segments. Expected answer: The decline is more pronounced among frequent users. Impact on approach: May lead to focusing on features that heavy users rely on more.

  • Regarding the metric itself, has there been any change in how "meals saved" is calculated or tracked since the update?

Why it matters: Ensures we're comparing apples to apples in our data. Expected answer: No changes in the metric calculation. Impact on approach: If changed, we'd need to reassess our baseline data.

  • Thinking about user feedback, have you seen any significant changes in app store ratings or direct user complaints since the update?

Why it matters: Provides qualitative data to complement our quantitative metrics. Expected answer: Some increase in negative feedback related to specific features. Impact on approach: Would guide us to investigate those specific features more closely.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Mar 29, 2025