Airport guidance changes faster than incident evidence can be connected.
Drivers need current queue guidance while engineers need a verified cause before changing production systems.
Who you’d be doing this for
“I drove over for a short wait, then sat there nearly an hour with no rides.”
Femke Weber · Rideshare Driver
Drives airport trips and uses airport wait-time guidance to decide where to work.
What is at stake
Airport wait-time guidance is staying stale after airport communication changes, sending drivers into queues that no longer match the app. You must decide what the system can rank automatically and what engineers must verify before acting.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster diagnosis vs verified cause
- airport responsiveness vs production reliability
- AI-ranked evidence vs engineer judgment
- driver guidance continuity vs cautious releases
Why Lyft
Airport guidance in the driver app shapes whether drivers spend earning time entering a queue.
Written with these in mind
Not your kind of problem? 70 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.