Resolve a cross-functional conflict blocking Logistics Platform

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’s Logistics Platform powers how delivery opportunities are created, matched, routed, tracked, and completed across food delivery, grocery, retail, and other local commerce use cases. A planned platform initiative meant to improve delivery reliability for Dashers and marketplace operations is currently blocked by a cross-functional conflict between teams such as Product, Engineering, Operations, Data Science, Support, Legal/Policy, and regional business stakeholders.

You are the PM responsible for getting the initiative unblocked and moving it toward launch. The conflict may involve competing priorities, unclear ownership, disagreements on risk tolerance, trade-offs between Dasher experience and marketplace efficiency, operational readiness concerns, or tension between short-term business metrics and long-term platform scalability.

Your task is to describe how you would diagnose the conflict, align stakeholders, create an execution path, and manage launch risk without assuming unlimited resources or authority. The focus is not on designing the Logistics Platform itself, but on demonstrating how you would lead execution in a complex marketplace environment where Dasher earnings, delivery reliability, merchant outcomes, customer experience, and unit economics all matter.

The experience should consider:

- The specific nature of the cross-functional conflict, including which teams are blocked, what decisions are unresolved, and why progress has stalled.

- The operating plan you would create, including decision owners, workstream owners, dependencies, milestones, and escalation paths.

- How you would align stakeholders around shared goals and trade-offs across Dasher experience, marketplace balance, reliability, merchant ROI, and cost efficiency.

- The sequencing of work required to unblock execution, validate assumptions, prepare operations, and reduce launch risk.

- Go/no-go criteria for moving forward, including product readiness, data confidence, operational preparedness, support readiness, and risk acceptance.

- Communication mechanisms for keeping executives, regional teams, engineering, operations, and support teams aligned.

- Rollback, mitigation, and contingency plans if the launch causes reliability issues, Dasher dissatisfaction, marketplace imbalance, or operational strain.

- How you would prevent similar cross-functional blockers from recurring in future Logistics Platform initiatives.

The goal is to show how you would lead a medium-complexity execution challenge at DoorDash: turning an ambiguous cross-functional conflict into a clear operating rhythm, accountable decisions, manageable risks, and a path toward delivering a reliable platform outcome for Dashers and the broader marketplace.