How Haro’s Smart Bike Scheduling Boosts Asset Utilization – Key Takeaways from the HiPM Summit

Event Overview

On October 23‑24, the HiPM Product Innovation Summit gathered 55 senior product leaders from leading companies in Shenzhen. Among them, Haro Mobility’s senior product expert, Xi Hao, delivered a talk titled “Smart Scheduling Practice for Shared Bikes,” focusing on experience, feedback, human‑machine collaboration, feature‑driven design, and group‑interest alignment.

Challenges in Bike Distribution

Shared bikes and e‑bikes serve 1‑3 km trips, making user experience critical. However, heavy asset investment and operational costs lead to a “divergent” vehicle distribution in reality, caused by idle bikes and random parking. Operators must convert “unusable” bikes through maintenance and dispatch to restore availability.

Xi emphasized that two‑wheel mobility is a single‑sided market with high operating, depreciation, and loss costs, requiring lean operational methods that match limited supply with riding demand.

Evolution of Dispatch Modes

Haro’s dispatch system has progressed through three stages:

Manual Dispatch : Front‑line operators relied solely on experience for street‑level dispatch.

Task‑Based Dispatch : City managers assigned tasks centrally using station data.

Intelligent Dispatch : The “Haro Brain” system predicts supply‑demand using station attributes, historical ride data, weather, and real‑time driver locations, generating optimal routing tasks for dispatch personnel.

Strategic Product Thinking

Using the dispatch endpoint recommendation strategy as an example, Xi outlined a three‑step product strategy process:

Problem Analysis : Identify root causes, especially “bad cases” from feature or model releases, treating them as critical inputs for iteration.

Solution Design : Produce a complete strategy document that answers what the problem is, how to solve it, the expected impact, and evaluation metrics—not merely a PRD.

Review & Evaluation : Assess whether the problem is solved, if new issues arise, and weigh cost‑benefit to decide on further iteration, with pre‑designed review plans to avoid missing data after launch.

Visual Illustrations

The presentation concluded with a reminder that every “bad case” deserves respect and systematic analysis to continuously improve the product and operational efficiency.