Build a metric tree for Dasher App after a major redesign

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.

DoorDash has recently launched a major redesign of the Dasher App, the mobile experience used by Dashers to receive offers, navigate to restaurants, manage pickups, complete deliveries, and track earnings. The redesign may have changed information architecture, task flows, visual hierarchy, in-app guidance, and how Dashers make real-time decisions during a delivery.

Your task is to build a metric tree that helps DoorDash understand whether the redesigned Dasher App is improving the delivery experience and marketplace outcomes, especially for restaurant orders. The metric framework should connect app-level user behavior to operational performance, Dasher earnings and satisfaction, merchant reliability, customer experience, and business health.

This is a metrics interview question. Focus on defining useful metrics, how they relate to each other, what denominators and cohorts matter, how the data would be instrumented, and how DoorDash should interpret changes after launch without confusing app impact with marketplace or seasonality effects.

The metric tree should consider:

- The core Dasher workflow from offer receipt through acceptance, travel to restaurant, pickup, drop-off, and post-delivery actions.

- Clear north-star, input, diagnostic, and guardrail metrics for the redesigned app experience.

- Denominators such as active Dashers, sessions, offers shown, offers accepted, deliveries completed, restaurant pickups, and delivery hours.

- Key cohorts including new vs. experienced Dashers, high-frequency vs. occasional Dashers, market type, restaurant category, device/platform, and delivery mode.

- Instrumentation needs for app events, funnel steps, latency, errors, navigation transitions, acceptance decisions, pickup status updates, and support contacts.

- Guardrails around delivery reliability, Dasher earnings, cancellation rates, merchant wait time, customer ETA accuracy, safety, and marketplace balance.

- How the metric tree would support diagnosis if topline outcomes move in different directions across markets or Dasher segments.

- How to distinguish redesign-driven behavior changes from external factors such as demand shifts, weather, restaurant readiness, incentives, or competitive activity.

The goal is to create a structured measurement framework that DoorDash product, design, operations, and marketplace teams could use to evaluate the redesigned Dasher App, identify where the experience is helping or hurting Dashers, and make informed post-launch decisions.