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 orders are matched, assigned, routed, and completed across food delivery, grocery, and other local commerce use cases. A cross-functional conflict is blocking progress on an important platform initiative affecting Dashers, and you are the PM responsible for getting the work unstuck and moving toward launch.

The conflict may involve teams such as engineering, data science, operations, support, legal/policy, finance, or marketplace teams disagreeing on priorities, timelines, ownership, risk tolerance, or success criteria. The issue is not simply interpersonal; it has implications for delivery reliability, Dasher experience and earnings, merchant outcomes, customer satisfaction, and marketplace unit economics.

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. Focus on the operating approach you would use as the PM to turn disagreement into a clear decision and execution plan.

The experience should consider:

- The specific nature of the conflict, including which teams are involved and what each side may be optimizing for

- The impact of the blockage on Dashers, merchants, customers, and marketplace health

- How you would gather facts, clarify trade-offs, and separate data-backed concerns from opinions

- Decision ownership, escalation paths, and how you would drive alignment without over-escalating too early

- A practical sequencing plan with owners, dependencies, milestones, and go/no-go criteria

- How launch risks would be monitored, including reliability, Dasher earnings, operational burden, and customer promise accuracy

- Communication plans for executives, partner teams, operations, and frontline support teams

- Rollback or mitigation options if the chosen path creates marketplace disruption

The goal is to demonstrate how you would lead execution in a high-stakes, cross-functional DoorDash environment: balancing speed with reliability, resolving ambiguity, protecting the Dasher and customer experience, and creating a clear path from conflict to accountable delivery.