Product Design Prompt: Parking-Spot Finder Integrated with Google Maps
Design a parking-spot finder feature integrated into Google Maps.
Address:
-
Target users and pain points.
-
Core user journeys.
-
MVP feature set.
-
Go-to-market strategy.
-
Primary success metrics.
-
Business and revenue model.
-
Counter-metrics to monitor to avoid unintended consequences.
Constraints & Assumptions
-
Ground the design in real parking behavior and data availability.
-
Distinguish off-street parking, such as garages and lots, from on-street curb parking.
-
On-street availability is often probabilistic, not guaranteed.
-
Safety, legality, driver distraction, local regulations, and entrance routing matter.
-
The feature should fit naturally inside Google Maps rather than feel like a separate app.
Clarifying Questions to Ask
-
Which market should we launch in first: dense urban areas, airports, events, campuses, or suburban destinations?
-
Are we allowed to support reservations and payments, or only discovery and routing?
-
What parking data is available: garage feeds, city meter data, sensors, historical patterns, user reports, or partners?
-
Are we optimizing for time saved, certainty, lower price, revenue, or user trust?
-
How should we handle legal restrictions and curb rules?
Part 1 - Users, Pain Points, and Journeys
Define target users, pain points, and core user journeys.
What This Part Should Cover
-
Users such as commuters, event-goers, travelers, delivery drivers, EV drivers, and visitors.
-
Pain points around uncertainty, price, walking distance, legality, entrances, safety, and time pressure.
-
Pre-trip planning, en-route rerouting, arrival search, reservation, payment, and walking navigation.
-
Trade-off between close, cheap, and certain parking.
Part 2 - MVP and GTM
Define the MVP feature set and go-to-market strategy.
What This Part Should Cover
-
Parking difficulty badge, option comparison, garage reservation, pricing, walking time, entrance routing, and availability confidence.
-
Off-street parking as an MVP wedge before broader on-street prediction.
-
Partner, city, event, and airport launch strategy.
-
User education about probabilistic availability and legal rules.
Part 3 - Metrics, Business Model, and Counter-Metrics
Define success metrics, revenue model, and counter-metrics.
What This Part Should Cover
-
Metrics such as parking search success, time to park, reservation conversion, navigation completion, user trust, and repeat use.
-
Business models such as partner commissions, promoted lots, reservations, payments, EV charging, or enterprise/event partnerships.
-
Counter-metrics such as wrong availability, illegal parking, driver distraction, congestion, complaints, price inflation, and partner bias.
What a Strong Answer Covers
A strong answer recognizes that parking is a data-quality and trust problem. It proposes a focused MVP, handles uncertainty transparently, and balances user convenience, city rules, safety, partner incentives, and Google Maps' navigation experience.
Follow-up Questions
-
How would you estimate on-street parking availability without sensors?
-
What would you do if a user arrives and the spot is gone?
-
How would you prevent the product from increasing congestion?
-
How would you rank price versus distance versus certainty?
-
What market would you choose for launch and why?