Diagnose a 20 percent drop in activation for Rides

Problem Statement Description

Product context: Uber is a mobility and delivery platform; its products include rides, Uber Eats, grocery and retail delivery, freight, driver and courier tools, and marketplace pricing.

Uber has observed a 20% drop in activation for Rides among riders. In this context, activation should be treated as the point where a rider successfully reaches the first meaningful usage milestone, such as completing a first ride after signup, reactivation, or app install, depending on how you choose to define the funnel.

You are the product manager investigating the issue. Your task is to structure a root-cause analysis that separates a real business problem from a measurement artifact, identifies where in the rider journey the decline is happening, and narrows the most likely drivers across product, marketplace, pricing, reliability, safety, acquisition quality, and local market conditions.

The analysis should reflect Uber’s marketplace dynamics: rider activation depends not only on app onboarding, payment setup, and intent to travel, but also on driver supply, ETA, price, promotions, city-level operations, trust, and competitive alternatives.

The experience should consider:

- How you define “activation,” including the numerator, denominator, time window, and whether the drop applies to new riders, returning riders, or a specific cohort.

- How you would validate the anomaly through instrumentation checks, event logging, funnel consistency, data freshness, experiment exposure, and changes in attribution.

- Which segments you would cut by first, such as geography, platform, app version, acquisition channel, rider type, trip intent, payment method, time of day, and signup cohort.

- Where in the rider journey the drop may occur: install, signup, phone verification, location permission, destination entry, fare estimate, ride request, driver match, pickup, trip completion, or post-trip payment.

- Marketplace-side hypotheses, including driver availability, ETAs, surge pricing, cancellation rates, pickup reliability, safety concerns, or local disruptions.

- Demand-side and competitive hypotheses, including promo changes, acquisition mix, seasonality, holidays, weather, public transit changes, competitor pricing, or brand trust.

- Evidence you would seek to prioritize hypotheses, quantify impact, and distinguish correlation from causation.

- Immediate mitigation options, longer-term prevention mechanisms, and how you would monitor recovery without prematurely declaring success.

Your goal is to present a clear RCA approach that moves from anomaly validation to segmentation, hypothesis generation, evidence gathering, impact sizing, mitigation, and prevention, while staying grounded in the rider activation funnel and Uber’s two-sided marketplace constraints.