Lyft · Product sense · Mid · 45 to 60 minutes

Gated community pickups break down

Lyft is a ride hailing platform that matches riders with drivers for local transportation. Answer this product management case and get it graded line by line against a weighted rubric.

product sense
prioritization
systems thinking
metrics
experimentation

The situation

You are a PM working on Lyft's pickup experience with partners across mapping, routing, and the rider and driver apps. Regional operations teams keep flagging a recurring complaint in markets with many gated apartment complexes and communities: riders request a ride from home, drivers arrive at a locked entrance, and the pickup falls apart. Internal data shows these rides have more cancellations, longer waits, and more rider driver contact than typical pickups. In some markets, gated community pickups account for 25 to 30 percent of rides, so leadership is no longer sure this is a niche edge case. Your director asks you for a recommendation. Should Lyft make a focused investment here, and if so, what problem should it solve first and how? The hard part is that the issue may span multiple moments in the journey, from choosing a pickup spot to getting a driver through a gate. Any change could also backfire by adding rider friction before request, exposing sensitive gate details, or distracting drivers during navigation. Assume you have access to ride funnel, wait time, cancellation, route, and support contact data by market.

What to produce

Write a 1 to 2 page product strategy memo.

Your answer must

Define the target users and the specific pickup failures you would prioritize solving first, for both riders and drivers.
Size the opportunity and explain whether this segment deserves dedicated investment, using the context provided and a clear segmentation approach.
Lay out your diagnosis of the most likely root causes, including where in the pickup journey they occur and what evidence you would seek.
Propose a product approach for an MVP and a follow on phase, covering rider experience, driver experience, and any needed mapping or routing changes.
Specify success metrics, guardrails, and an experiment or rollout plan that would tell you whether the solution improved the end to end pickup experience.

Constraints

Must work within Lyft's existing rider and driver apps plus its current mapping and routing stack, no new hardware or on site staff.
Cannot assume complete gated community coverage or perfect entrance data on day one.
Any rider prompt before requesting a ride should add as little friction as possible.
Driver facing information must be safe to consume while navigating and must protect sensitive access details.

Format

Use sections with short headings such as Problem, Users, Diagnosis, Recommendation, Metrics, and Risks.

How Lyft actually played it

Gated community pickups can be 25 to 30 percent of rides in some markets, yet the app offered no guidance and caused cancellations and longer waits. Lyft Mapping found two root causes in the data, then built an end-to-end flow; about 95 percent of riders surveyed responded positively. A good case of sizing a problem and fixing the full journey.

Size the segment before deciding it is niche.
Diagnose root causes from data and examples.
Fix the end-to-end experience, not one screen.

Built from How We Built a Smarter Pickup Experience for Gated Communities by Lyft Engineering.