Finding the city’s natural joints
Christopher Alexander argued that good form comes from decomposing a problem along its own structure, not along your culture’s inherited categories. Run his 1964 method on Uber and the failures that haunted it for a decade fall out exactly where the org chart cuts through the problem’s real subsystems.
Five moves, from misfit to form
Alexander’s program is a pipeline. Each stage consumes what the previous one produced, and the form itself is the residue of the final composition, not a sketch you started with.
- 01 Resist
- 02 Enumerate
- 03 Map
- 04 Decompose
- 05 Compose
Resist
Drop inherited categories
"Rider app," "pricing," "maps" are the org chart’s vocabulary, the modern equivalent of "acoustics" and "circulation." Start there and you guarantee you solve the wrong structure.
Enumerate
List the misfits
Not goals. Failures. The driver cancels on a low fare. The pin sits 200m from a viable curb. Surge reads as gouging at the worst moment. Hundreds of them, each specific.
Map
Graph the interactions
Which misfits constrain each other? Cancellations couple tightly with hidden destinations and earnings legibility, and barely at all with airport chaos.
Decompose
Find the natural clusters
Cut the graph where it is sparse. The dense clusters that fall out are the problem’s real subsystems, and they will not match your component library or your teams.
Compose
Diagram, then assemble
Solve each cluster with a minimal formal gesture, a diagram, then compose the diagrams along the decomposition tree. The interface is the residue.
Where the org chart cuts the wrong way
Uber’s misfits, clustered by how they actually interact. Each colored region is one of the problem’s natural subsystems. The team boundaries run straight across them, and misfit accumulates wherever a team line slices through a subsystem.
The rendezvous cluster crosses three team boundaries, which is why airport pickups stayed broken for years: the natural subsystem had no owner, because the self-conscious decomposition split it three ways. Alexander’s claim, vindicated. Misfit gathers exactly where the program’s structure diverges from the problem’s.
One formal gesture per cluster
A diagram, in Alexander’s sense, is the minimal move that resolves a cluster’s internal tensions. Uber converged on most of these eventually, years late, because each one cut across the teams that owned its pieces.
Pickup as a negotiated point
Not a GPS coordinate. A point chosen from a finite set of physically viable locations, confirmed by both parties.
What Uber built designated pickup zones, PIN-matching at airports
Both sides see the deal upfront
Fare, destination and earnings are legible before either party commits. Surprise is the misfit; predictability dissolves it.
What Uber built upfront pricing, upfront destinations, resisted for years
Honest uncertainty
The system shows what it knows and admits what it doesn’t: ranges instead of false-precision ETAs, stale state marked as stale.
Still partially unresolved the confident-but-wrong ETA persists
Failure has a path
Every broken match (a cancellation, a dispute, a lost item) gets a designed route back to resolution, inside the flow, not outside it.
What Uber built in-app lost-item calls, cancellation reason flows
Corrected by generations, or re-derived at speed
Form corrected by generations
The raised hand at the curb, the medallion, the airport queue. Nobody designed them. Decades of street-level failure and small correction produced well-fitted forms, the way the Mousgoum hut fit its climate. Fit without a designer.
Form re-derived at speed
Uber tore up the corrected form and had to re-derive fit deliberately, in years rather than generations. Its most persistent failures map onto the places where its team-based decomposition missed the problem’s natural joints.