If you were the Senior PM at Uber, how would you define the metrics and north star of your team before leaving for a 2-month break?

Introduction

Defining success metrics for Uber's product team before a two-month break is crucial for maintaining focus and driving progress. To address this product success metrics challenge effectively, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Uber is a ride-hailing platform connecting riders with drivers through a mobile app. Key stakeholders include riders, drivers, Uber's business team, and regulatory bodies.

User flow:

1. Rider opens app, enters destination
2. App matches rider with nearby driver
3. Driver picks up rider and completes trip
4. Payment processed automatically

Uber's strategy focuses on expanding market share, improving efficiency, and diversifying into new services like food delivery and freight.

Competitors include Lyft, traditional taxis, and regional ride-hailing apps. Uber differentiates through its global presence and brand recognition.

Product Lifecycle Stage: Mature growth phase, with established market presence but still expanding into new markets and services.

Software-specific context:

• Platform: Mobile-first, with web interface for certain functions
• Integration points: Payment systems, mapping services, driver/rider communication
• Deployment model: Continuous deployment with regional variations