Station-access alerts need faster context without letting a suggested severity become a decision.
Incident speed protects station availability, while engineer review protects the integrity of security decisions.
Who you’d be doing this for
“I had to explain why three stations were offline, and nobody could tell me if it was maintenance or something worse.”
Jiyeon Choi · Public Mobility Program Manager
Oversees a municipal bike-share program whose station availability and safety are affected by security incidents.
What is at stake
Suspicious station-access alerts are taking too long to classify because repair and field evidence sit apart. You have to weigh faster routing against the risk of an AI suggestion understating a real security incident.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster incident routing vs engineer-owned severity
- field repair context vs security signal integrity
- reusable automation vs narrow pilot safety
- station availability vs investigation rigor
Why Lyft
Bike and scooter stations combine connected hardware, field repair activity, and public-facing availability in the same operating surface.
Written with these in mind
Not your kind of problem? 66 more at Lyft, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.