Diagnosing Ride Cancellations in Uber (RCA) - Case Study

Investigated a spike in ride cancellations by breaking down the end-to-end ride lifecycle and analysing potential user, driver, and system-level factors. Identified a critical issue in the driver application caused by a recent release, where a UI interaction unintentionally triggered ride cancellations. The solution included immediate rollback, system fixes, and improved safeguards, highlighting a structured approach to diagnosing and resolving real-world product issues.

1) Type

Root Cause Analysis / Product Operations

2) Role

Product Manager

3) Focus Area

Operational Reliability & Funnel Diagnostics

4) Skills

Analytical Thinking, RCA, Funnel Analysis, Product Operations, Systems Thinking

5) Metrics

Ride Completion Rate, Cancellation Rate, Driver Acceptance Rate

6) Tools Used

Analytics, Funnel Diagnostics, Logging Systems

7) Platform

Mobility, Marketplace, Mobile App

8) Framework

Root Cause Analysis, Funnel Analysis

9)  Understanding Problem

Metric drop - Increased cancellations

10)  Break into Funnel

Ride lifecycle:

a)     Request

b)    Match

c)     Accept

d)    Start ride

11)  Possible Causes

     I. User-side

• Payment failure

• UX issues

  
  

     II. Driver-side

• Incentive mismatch

• UI issues

  
  

     III. System

• Bugs

• API issues

12)  Key Investigation

• Time correlation

• Release logs

• Geo segmentation

13)  Root Cause

Driver app bug:

• “View ride” → triggers cancellation

14)  Solution

  I. Immediate:

· Rollback

 II. Medium:

· Fix logic

III. Long-term:

· Add safeguards

15)  Metrics

  I. North Star - Ride Completion Rate

  II. Supporting -

· Cancellation rate

· Driver acceptance rate

 III. Guardrails -

· App crashes

· Driver churn

16)  Final Insight

Always check:

• Recent releases first

• Then user/system factors