Uber’s core innovation was making a cab appear at the push of a button — and letting you track it in real time. Today, that feels obvious. But it wasn’t then.
Uber is a transportation company that claims to be cheaper and safer than traditional taxis. It operates through a mobile application available on platforms like iPhone and Android. You start by downloading the app and registering with Uber — entering your personal details and credit card information to enable seamless payments.
When you need a ride, you open the app and look for available cars nearby. If you do not see any cars available, that counts as a Zero for Uber — meaning a user opened the app but saw no available cars at that moment.
Understanding why users encounter these "Zeroes" is critical. It reveals the operational challenges Uber faces in balancing supply and demand across different cities and times.
Why “Zeroes” happen: The supply-demand dynamics exposed
There are several reasons why a user might see zero cars available:
-
Off-peak hours with low activity: For example, 5 AM in the morning is often a dead-time in most cities. Drivers won’t be available because it is not feasible for them to wait for hours when there is no demand. The opportunity cost is too high.
-
All drivers are currently busy transporting passengers: This situation is common during rush hours or late weekend nights. Everyone is trying to get a ride home, and the available cars are already occupied. This scenario triggers Surge Pricing — a dynamic pricing mechanism Uber uses to balance demand and supply by increasing fares temporarily.
-
Temporary unavailability despite normal conditions: Sometimes, even when everything seems normal, there might be no cars available at a given moment. The user may need to check back later as cars become free.
-
Uber is not available in the current city: This may seem obvious, but many users travel to cities where Uber is not yet launched and open the app only to find no cars available.
These “Zero” moments are important operational signals. They represent lost opportunities for Uber: potential rides that did not happen because supply could not meet demand.
Key user actions and terminology in the Uber app
Let’s break down the core user flow and the terms Uber uses internally to describe these actions and states:
-
Eyeballs: A potential passenger (rider) who opens the app and looks for cars. Eyeballs measure interest and intent at the earliest stage.
-
Zeroes: When a rider opens the app and sees no cars available at that time.
-
Requests: The number of people who have asked for a car to pick them up through the app.
-
Dispatch: The actual request for a car made by a potential passenger.
-
Completed Trips: Requests that are successfully fulfilled. Some requests do not complete because no driver was available, no driver accepted, or the ride was canceled by either party before pickup.
-
Driver: The rideshare partner driving the car.
-
Rider: The passenger requesting and taking the ride.
-
ETA (Estimated Time of Arrival): The time between when a user requests a car and when the car arrives at the user’s location.
-
Fare: The amount paid by the passenger, calculated via metering on the Uber app.
-
Surge Pricing: A dynamic pricing tool that raises prices quickly in response to high demand to reduce demand and ease supply strain, keeping ETAs low for both riders and drivers.
-
Driver Supply: Number of cars online and available to take rides.
-
Demand: Passengers looking for cars, measured through eyeballs and requests.
-
Idle Time: When a driver is online but not transporting any passengers.
-
Peak Hours: Rush hours where demand is high.
-
Working Shifts: The typical hours drivers work daily, often 8-10 hour shifts.
Understanding these terms helps you grasp how Uber measures and manages its marketplace.
What happens when you request a ride
When you see available cars, you tap to request one. That request is called a Dispatch. After dispatch, the app lets you contact your driver if needed — directly through the app’s interface.
You can cancel your request without charge for a limited time after requesting a car. This cancellation window is designed to balance user flexibility and driver fairness.
The Uber experience from the driver’s perspective
Drivers, or Uber partners, use GPS navigation software to make rides smooth and efficient. But GPS navigation can be imperfect: cities might not be fully mapped, or addresses might be missing from GPS databases. These issues can delay pickups or cause detours.
Importantly, drivers are not blamed for these navigation problems. However, rider complaints about delays or wrong routes can affect the driver’s rating. When a driver accumulates many complaints, Uber evaluates not just the complaints but also the driver’s activity level, complaint-to-ride ratio, typical driving areas, and overall rating before deciding whether to continue the partnership.
Driver onboarding is a critical process to maintain quality. Depending on the city, Uber may require drivers to have local knowledge or pass screening tests. Only drivers who satisfy these requirements are onboarded.
Balancing supply and demand: Why timing and geography matter
Uber’s marketplace operates in complex environments with varying demand and supply patterns.
-
During peak hours, demand spikes as many riders request cars simultaneously. This can lead to zero availability and surge pricing.
-
Driver working shifts tend to be consistent, but drivers may avoid low-demand times to maximize earnings.
-
Geographic factors matter. For instance, in cities like Bangalore, even short detours can cause significant delays due to traffic congestion. This affects driver willingness to accept rides that require detours and the incentives needed to encourage them.
-
In contrast, cities with lighter traffic might find drivers more willing to accept detours for shared rides or carpooling.
The rider’s perspective: What matters most
At its core, Uber provides a cab at the push of a button. The innovation was adding real-time tracking of the vehicle on a map. Today, this feels obvious, but in 2013-2014, it was a major attractor for users.
Riders want reliability, availability, and predictability:
-
Availability: Cars should be visible and ready when needed.
-
Reliability: The ETA should be accurate, and driver communication smooth.
-
Fair pricing: Surge pricing balances supply and demand, but it can frustrate users if it feels unpredictable.
-
Convenience: Easy cancellation, in-app communication, and payment simplify the experience.
If any of these fail, user satisfaction drops, leading to lost rides and reduced loyalty.
Operational challenges Uber faces in India
India’s cities present unique operational challenges for Uber:
-
Traffic congestion: Cities like Bangalore have heavy traffic, making ETAs volatile and detours costly.
-
Data quality: GPS mapping may be incomplete, addresses ambiguous, and street names inconsistent.
-
Driver behavior: Drivers may avoid less profitable or unsafe areas, creating supply gaps.
-
Demand spikes: During festival seasons, weekends, or bad weather, demand surges unpredictably.
Uber’s system must adapt dynamically to these realities, using surge pricing, driver incentives, and supply management to keep the marketplace balanced.
Measuring success: Metrics that matter
Uber tracks multiple metrics to understand and improve the user experience:
| Metric | What it measures | Why it matters | Example Indian context |
|---|---|---|---|
| Eyeballs | Number of users opening the app | Interest level | Mumbai commuters checking availability during peak hours |
| Zeroes | Times users see no cars available | Supply gap indicator | Early morning in tier-2 cities with fewer drivers |
| Requests | Number of ride requests made | Demand | Weekend nights in Delhi |
| Completed Trips | Successful rides | Marketplace efficiency | Swiggy delivery partners using Uber for commute |
| ETA accuracy | Difference between estimated and actual arrival | User trust | Bangalore traffic unpredictability |
| Surge pricing frequency | How often prices spike | Supply-demand imbalance | Festival days in Hyderabad |
These metrics guide product decisions, driver incentives, and operational focus.
Field Exercise: Map the user journey
Take an app you use regularly — it could be Uber, Ola, or a local taxi app. Write down the key user actions from opening the app to completing a ride. Identify moments where users might see “zero availability” or face delays.
Then, list the factors that could cause supply shortages or demand spikes in that app’s context.
Test yourself: Managing zeroes in a new city
You are the PM launching Uber in a tier-2 city in India with limited driver supply. On day one, many users open the app but see zero cars available, leading to cancellations and negative app ratings.
The call: What immediate product or operational strategies do you prioritize to reduce zeroes and improve user experience?
Your reasoning:
Where to go next
- Understand marketplace economics in depth: Marketplace Fundamentals
- Learn how to optimize supply and demand balance: Supply-Demand Matching
- Explore driver incentives and retention: Driver Management Strategies
- Study pricing strategies like surge pricing: Dynamic Pricing
- Prepare for PM interviews with operational cases: PM Interview Preparation