Getting a reliable ride in a city is slow, expensive, and unpredictable. Taxis are hard to hail, dispatch is unreliable, payment is awkward, and there is no transparency on price, ETA, or driver quality.
Every job is expressed at four depths, from a minimal basic version to a comprehensive one. Each dot is a feature — the median climbs with depth (a comprehensive feature is 7.2× harder on average than its basic version), but so is the overlap.
7 customers × 4 adoption stages = 56 cohorts. Each cell is a cohort, sized by its requirement load and grouped by customer segment (coloured by marketplace side). Hover for details.
56 cohorts → 961 requirement links → 400 of 920 features. Each band is a customer segment, each ribbon is a requirement link, and width shows how many features a segment demands from each problem domain. Hover for details.
Show the planned route drawn on a map with the car's current position pinned. Solves basic reassurance that a path exists for most simple trips.
M1Rider Safety Team
Show driver and car details
Before pickup, display the driver's name, photo, car make, model, color, and plate so the rider can match them to the arriving car.
M1Trip Sharing & Dependents Team
Send trip link
Rider taps share to send a web link showing live car position and ETA; recipient views in any browser, no app needed. Solves basic peace-of-mind for most rides.
Payments & Pricing Group
M1Fares & Pricing Team
Distance-based estimate
Rider enters pickup and destination and sees a single fare estimated from straight-line distance and a flat per-mile rate. Solves most simple, uncongested trips.
M1Cashless Payment Team
Manual card entry
Rider types card number, expiry, and CVV into a form, stored for future trips. Covers most riders with a standard credit or debit card.
M1Receipts & Disputes Team
In-app receipt card
Shows an itemized receipt card in the app right after the trip ends, with fare lines, route, and total. Covers immediate confirmation needs.
Pickups Group
M1Ride Request Team
Auto-pin from GPS
App drops a pin at your phone's GPS location; you confirm it with one tap. Solves most open-street pickups where GPS is accurate.
M1Getting Matched Team
Broadcast to closest driver
Sends the request to the single nearest idle driver by straight-line distance; first to accept gets the trip. Solves most low-density cases.
M1Pickup Meeting Team
Auto GPS meeting point
Sets the meeting point automatically to the rider's GPS position and shows it to the driver. Solves clear-location cases.
Driver & Marketplace
Marketplace Engine Group
M1Dispatch & Matching Team
Straight-line nearest match
Picks the free driver with the shortest as-the-crow-flies distance to the rider. Solves most pickups in dense, well-supplied areas with simple, fast dispatch.
M1Dynamic Pricing Team
Surge price notice
Show the elevated fare and a plain surge label on the confirm screen before the rider commits, so no one is surprised at trip end.
M1Liquidity & Growth Team
Recruit drivers manually
Team signs up drivers one by one through a web form and reviews documents by hand, building a first roster before launch. Covers the initial handful of drivers.
M1Ride Reliability Team
Match nearest online driver
Sends the request to the closest available driver and shows honest availability. Solves most quiet-hour requests where a few drivers are still online nearby.
Driver Experience Group
M1Driver Onboarding Team
Basic account signup
Prospective driver enters name, email, phone, and password to create an account. Solves the entry step for motivated applicants who complete details later.
M1Driver Earnings Team
Tap to go online
One button flips a driver online and starts sending nearby ride requests, no shift or schedule required. Solves the core on-demand start for most casual drivers.
Identity, Accounts & Trust
Trust & Safety Group
M1Identity Verification Team
Sign up with phone and email
Rider registers a name, phone number, and email, confirmed by a one-time code. Solves most basic accountability where a reachable, named person requests rides.
M1Ratings & Reputation Team
Single tap score
Show a simple thumbs up/down or star screen at trip end to capture whether the ride was good. Solves the basic yes/no quality signal.
M1Incidents & Enforcement Team
Select trip and issue type
User opens trip history, picks the specific trip, and chooses an issue type to start a report tied to that exact ride record.
Accounts & Onboarding Group
M1Rider Accounts Team
Manual phone entry with SMS code
Rider types their mobile number, receives a one-time code by SMS, and enters it to create the account. Solves signup for most standard cases.
M1Driver Applications Team
Email signup form
Prospective driver creates an account with email, phone, and password, then answers a basic web form to start the application.
Uber-style Rideshare
Problem
Getting a reliable ride in a city is slow, expensive, and unpredictable. Taxis are hard to hail, dispatch is unreliable, payment is awkward, and there is no transparency on price, ETA, or driver quality.
Solution
2-sided marketplaceA smartphone app that lets riders summon a nearby driver on demand, with upfront pricing, live tracking, cashless payment, and two-way ratings.
How it works
6 stepsPrinciples
12 beliefsProblem domains
6 domainsUse cases and Jobs
6 domains → 36 use cases → 230 jobs. Each cell is a use case, sized by its job count and coloured by domain. Hover for details.
Features
920 featuresEvery job is expressed at four depths, from a minimal basic version to a comprehensive one. Each dot is a feature — the median climbs with depth (a comprehensive feature is 7.2× harder on average than its basic version), but so is the overlap.
Customer segments
2-sided marketplace7 customersCustomer cohorts
7 customers × 4 adoption stages = 56 cohorts. Each cell is a cohort, sized by its requirement load and grouped by customer segment (coloured by marketplace side). Hover for details.
Customer requirements
56 cohorts → 961 requirement links → 400 of 920 features. Each band is a customer segment, each ribbon is a requirement link, and width shows how many features a segment demands from each problem domain. Hover for details.
Customer terrain
Requirement load for every cohort — customers × adoption stages. Green is easy ground, red is steep.
Customer sequencing
The first moves on each side of the marketplace — the lightest cohorts, in rollout order. Colour = requirement load (green is easy ground).
Team composition
147 roles · 28 squads · 10 groupsAll 147 roles open — hiring not startedThe whole org in one block — divisions → groups → squads left to right, band height = FTE headcount. Hover for details.
Product roadmap
685 deliverables · 54 milestonesThe next milestones from each squad
Positioning
5 momentsMarket opportunity
Opportunity over time — overlaid TAM / SAM / SOM bands per positioning moment.