How can DiDi balance driver availability with surge pricing to maximize both user satisfaction and driver earnings?

Introduction

Balancing driver availability with surge pricing is a critical trade-off for DiDi to maximize both user satisfaction and driver earnings. This scenario involves managing the supply of drivers, demand from riders, and the pricing mechanism that connects them. I'll analyze this trade-off by examining the product ecosystem, identifying key metrics, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming this is a ongoing challenge rather than a specific incident. Could you confirm if this is a systemic issue or if there's a particular event or market driving this question?

Why it matters: Helps frame the scope and urgency of the solution Expected answer: Ongoing challenge across markets Impact on approach: Would focus on long-term, scalable solutions rather than quick fixes

• Business Context: Based on DiDi's business model, I'm thinking revenue is primarily driven by take rates on rides. How does surge pricing currently impact our overall revenue and profitability?

Why it matters: Helps understand the financial implications of adjusting the surge pricing model Expected answer: Surge pricing increases short-term revenue but may impact long-term user retention Impact on approach: Would need to balance short-term gains with long-term sustainability

• User Impact: I'm assuming we have different user segments with varying price sensitivities. Can you share insights on how surge pricing affects behavior across these segments?

Why it matters: Helps tailor solutions to different user needs and behaviors Expected answer: Price-sensitive users avoid surge times, while less sensitive users are willing to pay for convenience Impact on approach: Would consider segmented pricing strategies or incentives

• Technical: Considering the real-time nature of ride-hailing, I'm curious about our current capabilities for dynamic pricing. How granular can we adjust surge pricing in terms of time and location?

Why it matters: Determines the feasibility of more sophisticated pricing models Expected answer: Capable of adjusting prices at neighborhood level every few minutes Impact on approach: Would explore more nuanced, data-driven surge pricing algorithms

• Resource: Given the potential impact on core business metrics, I'm thinking this might require significant engineering resources. What's our current capacity for implementing changes to the surge pricing system?

Why it matters: Helps determine the scope and timeline of potential solutions Expected answer: Limited engineering resources available in the next quarter Impact on approach: Would prioritize high-impact, low-resource solutions initially