Resolve a cross-functional conflict blocking Uber One at global scale

Problem Statement Description

Product context: Uber is a mobility and delivery platform; its products include rides, Uber Eats, grocery and retail delivery, freight, driver and courier tools, and marketplace pricing.

Uber One is preparing for broader global expansion across mobility and delivery, but the launch is blocked by a cross-functional conflict. The membership team wants a consistent global value proposition for consumers, while regional operations, driver/earner teams, finance, legal, and marketplace teams are raising concerns about driver experience, supply reliability, local regulation, and unit economics.

As the PM responsible for execution, you are expected to navigate the disagreement and create a path to unblock the program without ignoring marketplace health. The conflict may involve questions such as whether Uber One benefits increase demand unevenly, whether drivers are compensated fairly for member-linked trips or orders, whether regional markets can support the promised reliability, and whether global consistency should override local operating constraints.

Your task is not to design Uber One from scratch, but to explain how you would diagnose the conflict, align stakeholders, make trade-offs explicit, and drive an operating plan that can scale across countries while protecting riders, eaters, drivers, merchants, and Uber’s business outcomes.

The experience should consider:

- The core stakeholders involved, including membership product, driver/earner experience, marketplace, regional operations, finance, legal, support, and executive leadership.

- The specific decision or disagreement blocking progress and how you would clarify ownership, escalation paths, and decision rights.

- The operating plan for resolving the conflict, including sequencing, workstreams, owners, dependencies, and timelines.

- The evidence needed to make a decision, such as driver earnings impact, supply availability, fulfillment reliability, member retention, cost per benefit, and regional readiness.

- Go/no-go criteria for global rollout versus phased launches, local exceptions, pilots, or market-specific configurations.

- Risks around driver trust, marketplace liquidity, regulatory exposure, customer promise, support burden, and margin deterioration.

- Communication and change-management needs across global and local teams, including how to keep teams aligned after a decision is made.

- Rollback, mitigation, and monitoring plans if the chosen execution path creates marketplace imbalance or harms driver sentiment.

The goal is to demonstrate how you would lead a complex, high-stakes execution problem at Uber’s scale: turning an ambiguous cross-functional disagreement into a structured decision, a credible launch plan, and a measurable operating cadence that balances growth, reliability, local realities, and marketplace health.