New York didn’t lack inventory. It had a Switch behind the circulation desk, a projector in the park, a database of court schedules. Real capabilities, fully funded, already live. By every internal metric, the “product” worked.
But capability isn’t access. A feature nobody can find isn’t a feature. It’s Shadow CX. It’s the tribal knowledge of the kid whose older cousin happens to know the library has games, the family already plugged into the parks calendar, the one group chat that tracks the runs. The system worked, but only for people who had already translated their need into the city’s internal structure.
Everyone else got the default municipal experience: here are 47 departments, each with its own portal, go figure out which one has what you want. Customers experience your systems, not your org chart. Teenagers experience the city, not the Parks/Libraries/DOT split that owns each piece.
”What should you do?” is the intent
Look at how Mamdani frames the open: young people are always told what not to do. But what should you do?
That’s the customer trying to do something. The intent is real, specific, and present: I’m bored, I have time, what’s available to me. The old architecture forced that kid to do the translation work: to know which agency runs what, know the program exists, know where it’s published, navigate five surfaces to assemble an answer the city could have assembled for them.
The gap isn’t a content problem. The content existed. It’s an architecture problem: the distance between what the customer is trying to do and what the system gives them at that moment. A single map collapses that distance. The right next step appears before the citizen has to reverse-engineer municipal structure.
Discoverability is the actual deliverable
This is the part most orgs miss, public or private. They keep building inventory: more programs, more docs, more features, and treat discovery as marketing’s problem or a footer link. But the routing layer is the product. It’s the thing that decides whether everything upstream of it converts into adoption or dies in a silo.
Mamdani’s map does four things that map cleanly to post-sales infrastructure:
| The map does | The system equivalent |
|---|---|
| Surfaces programs by what you want to do, not which agency owns them | Intent-based routing instead of org-chart navigation |
| Replaces “ask someone who knows” | Kills the Shadow CX dependency |
| One trusted surface for a dozen disconnected services | Unified self-service architecture |
| ”Free and affordable, made just for you” | Self-service as service, not its absence |
The lesson for anyone shipping software
You can fully fund a feature and still strand it. If adoption depends on a citizen or a customer already knowing the thing exists, you haven’t shipped a product. You’ve shipped potential, gated behind tribal knowledge.
The work that converts inventory into outcomes is invisible: the map, the routing, the signal that says given who you are and what you’re trying to do, here’s the thing. It rarely gets the press release. It’s the layer between the people and the org chart.
Mamdani put it in a tweet. It’s the same line I’d put on a diagnostic report:
The program isn’t the product. Access is the product. Everything else is just budget you haven’t connected to intent yet.
CX is infrastructure, civic or commercial. Engineer it accordingly.