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

Gojek Tech

What caused the sudden 30% increase in failed transactions for Gojek Tech's GoFood delivery service during peak lunch hours yesterday?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis Technical Understanding Food Delivery Fintech E-commerce Food Delivery Root Cause Analysis System Performance Crisis Management Transaction Processing
Product Management Root Cause Analysis Question: Investigating sudden increase in failed food delivery transactions

Introduction

The sudden 30% increase in failed transactions for Gojek Tech's GoFood delivery service during peak lunch hours yesterday is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term fixes and long-term strategic implications.

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 this could be a capacity issue. Can you confirm if there were any unusual spikes in order volume during the affected period?

Why it matters: Helps determine if the system was overwhelmed by unexpected demand. Expected answer: Yes, there was a 40% increase in order volume. Impact on approach: If confirmed, we'd focus on scaling infrastructure and load balancing.

  • Given the specificity of "failed transactions," I'm wondering about our error logging. Have we seen any particular error codes or patterns in the failure data?

Why it matters: Pinpoints specific technical issues causing the failures. Expected answer: There's been a spike in timeout errors. Impact on approach: If true, we'd investigate network issues or database performance.

  • Considering it's a lunch hour problem, I'm curious about restaurant partner performance. Have we noticed any changes in restaurant response times or cancellation rates?

Why it matters: Identifies potential issues on the supply side. Expected answer: No significant changes observed in restaurant metrics. Impact on approach: If confirmed, we'd shift focus to our internal systems rather than partner issues.

  • With recent product updates in mind, were any new features or changes deployed to the GoFood service in the past week?

Why it matters: Helps isolate if a recent change is causing the issue. Expected answer: A new payment gateway was integrated two days ago. Impact on approach: If true, we'd prioritize investigating the new integration and its impact on transaction processing.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025