Diagnose a 20 percent drop in activation for Drive at global scale

Problem Statement Description

Product context: DoorDash is a local commerce and delivery platform; its products include restaurant delivery, DashPass, grocery and retail delivery, merchant tools, and dasher tools.

You are the PM responsible for DoorDash Drive activation across global markets. Drive enables merchants and partners to offer DoorDash-powered delivery from their own ordering channels, so activation depends on a multi-sided workflow involving consumer checkout, merchant configuration, API/order creation, delivery quoting, Dasher availability, and successful first fulfillment.

The team has observed a 20% drop in activation at global scale. The decline appears large enough to affect business health, merchant ROI, delivery reliability, and marketplace balance, but the root cause is unknown. You need to structure an RCA that can separate a real product or marketplace issue from measurement noise, instrumentation changes, seasonality, partner mix shifts, or localized operational problems.

Frame the investigation as if you are working with product, engineering, data science, operations, merchant success, and regional teams. Focus on how you would define the anomaly, narrow the search space, validate hypotheses with evidence, identify immediate containment steps, and prevent recurrence.

Your RCA should consider:

- The exact activation metric definition, including numerator, denominator, eligibility criteria, activation window, and whether activation means first quote, first order creation, first completed delivery, or repeat successful usage.

- Instrumentation checks, including event schema changes, API logging gaps, attribution issues, partner-side tracking changes, delayed data pipelines, and global reporting consistency.

- Segmentation by geography, merchant or partner type, vertical, platform, integration method, consumer checkout funnel step, delivery distance, time of day, and new versus existing partner cohorts.

- Funnel decomposition across Drive quote generation, checkout conversion, payment, order creation, dispatch, Dasher acceptance, pickup, delivery completion, cancellations, and refunds.

- Marketplace and operational hypotheses, such as Dasher supply constraints, delivery time estimates, pricing or fees, service availability, merchant prep time, reliability incidents, and support/contact rates.

- External and commercial factors, including partner promotions, competitor activity, macro seasonality, merchant traffic changes, regulatory constraints, or changes in consumer demand by market.

- Evidence standards for prioritizing hypotheses, deciding whether to mitigate immediately, communicating severity, and setting up monitoring or prevention mechanisms.

The goal is to demonstrate a rigorous, product-oriented RCA approach that can quickly isolate where activation is breaking, distinguish correlation from causation, coordinate cross-functional action, and protect the Drive experience for consumers, merchants, Dashers, and DoorDash’s marketplace.