Plan the MVP rollout for Pickup in a constrained market 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.

DoorDash is evaluating how to roll out an MVP for Pickup in a constrained market, where customers are highly price-sensitive and delivery may be limited by affordability, courier supply, merchant density, or local operating constraints. Pickup allows customers to order ahead from restaurants or merchants and collect items themselves, reducing delivery fees while still using DoorDash for discovery, ordering, payment, and preparation timing.

The execution challenge is to define how DoorDash should launch this MVP in a way that is operationally feasible at global scale, while protecting customer trust, merchant readiness, marketplace balance, and unit economics. The plan should address how to start small, validate core assumptions, coordinate cross-functional teams, and decide whether to expand, pause, or adjust.

This is not a strategy question about whether Pickup should exist, and it is not asking for a full product design. Focus on the rollout plan: market selection, MVP scope, sequencing, dependencies, launch readiness, risk management, measurement, and communication across product, engineering, operations, merchant, support, marketing, and analytics teams.

The experience should consider:

- Which constrained market or market archetype should be selected first, and why it is suitable for an MVP

- The minimum viable customer and merchant experience needed for Pickup to function reliably

- Key owners across product, engineering, merchant operations, support, marketing, analytics, and local market teams

- Dependencies such as merchant onboarding, menu accuracy, prep-time estimates, payments, order status, cancellation flows, and customer support readiness

- Sequencing from internal testing to limited beta, market launch, and broader regional or global expansion

- Go/no-go criteria, including adoption, order completion, merchant reliability, customer satisfaction, refund rates, support contacts, and operational cost

- Launch risks such as poor merchant execution, inaccurate pickup times, customer confusion, cannibalization of delivery, marketplace imbalance, and competitive response

- Rollback or mitigation plans if the MVP creates customer trust issues, merchant burden, or negative unit economics

The goal is to present a practical MVP rollout plan that shows strong execution judgment: how to launch Pickup quickly but responsibly, how to coordinate teams under constraints, how to measure whether the launch is working, and how to scale only when the experience is reliable for customers, merchants, and the broader DoorDash marketplace.