Lyft's ML-powered ride mode recommendation and ranking system
As Lyft's product portfolio grew, riders in major markets faced 8–10 mode options at once, making it hard to discover the right ride type and risking accidental wrong-mode bookings. New mode launches suffered from cold-start bias due to limited training data, limiting their early visibility.
Earlier preselection heuristics were flawed: selecting the last-taken mode introduced exploration bias, and selecting the most-frequently-used mode was unstable for infrequent users. Static ranking by price or ETA did not account for user preferences.
ML propensity models now serve about 90% of use cases and have proven to drive more desirable outcomes than the static system, with model-based preselection proven to be more accurate and effective.
Frequently asked questions
What did this team achieve with this AI workflow?
ML propensity models now serve about 90% of use cases and have proven to drive more desirable outcomes than the static system, with model-based preselection proven to be more accurate and effective.
What tools did this team use?
LightGBM.
What results were reported?
ML model coverage of use cases: about 90%; Outcomes vs static system: more desirable outcomes compared to a static system; Model-based preselection accuracy: more accurate and effective (source-reported, not independently verified).
What failed first in this deployment?
Earlier preselection heuristics were flawed: selecting the last-taken mode introduced exploration bias, and selecting the most-frequently-used mode was unstable for infrequent users.
How is this ecommerce ops AI workflow structured?
Rider opens app or sets destination → ML model predicts mode propensity → Post-processor adjusts cold-start rankings → Ranked mode list displayed → Highest-propensity mode preselected → Post-request cross-sell shown.