Ask someone what a city does, and they'll usually describe the visible parts: the buildings, the streets, the dining, the parks. The harder question is what enables all of it. Water has to come out of the tap. Waste has to leave the building. Buses have to show up. Benefits have to reach the people eligible for them. Kids have to get to school on time. Permits have to clear. None of it happens by itself.
That's the working layer I mean when I talk about urban systems: the systems a city has to operate, day in and day out, for it to function at all. Some are literal: water, waste, food, energy. Some are logistical: transport, housing, health, emergency response. Some are social: education, workforce, economic mobility. The list isn't ordered or exhaustive. It's the territory.
What makes these systems distinctive is that they're part-organic and part-designed. They grew up over decades in response to whoever was living there, and they're also governed by codes, contracts, and agencies with formal authority. Agencies, private operators, standards bodies, community organizations, and vendors all have to land in the same room on the same problem, often with different authority, different incentives, and different time horizons. What makes the work hard is the coordination, not any single piece of it.
The clearest illustration comes from a specific moment. In 2018, the NYC Taxi and Limousine Commission capped the number of for-hire vehicles on the road for the first time. Uber and Lyft had grown unchecked for most of a decade, and the consequences had arrived all at once: congestion, emissions, wage collapse, a medallion market in freefall, a wave of driver suicides.
The real work was underneath. Rules had to become logic a system could enforce. New data had to be collected, and new analysis stood up, so the agency could tell whether any of it was working. Operations had to be redesigned. Teams had to be restructured. Every change had to be walked through with the industry while it was still being built. All of it had to happen at once, without breaking the service millions of New Yorkers depended on every day.
That's the layer this Journal is about. Not the policy debates above it or the infrastructure underneath it, but the operational layer in between.
If that's the layer you work in too, you're in the right place.