People experience journeys, not departments
A resident does not experience a city as an organization chart. They experience a trip to work, a permit application, waste collection, a flooded road, a public clinic, a broken streetlight, or a complaint that needs a response.
Those journeys often cross multiple agencies, contractors, systems, and physical locations. From the resident's perspective, however, it is still one experience.
That makes a city an interesting service-system problem: responsibility is distributed, but the outcome is experienced as a whole.
Citizens experience outcomes. Organizations experience boundaries.Working principle
Handoffs create invisible waiting
Many service failures happen between responsible parties rather than inside one party. A report is received but routed incorrectly. A field team arrives without the right information. A repair depends on another utility. A citizen is told to contact a different office without a clear handover.
Each organization may be following its own procedure while the overall journey remains broken.
Thought experiment
Imagine every public-service journey with four visible fields: current status, accountable owner, next action, and dependency. How many frustrating handoffs would become easier to see?
Shared visibility changes coordination
A useful service system makes status, ownership, dependency, and next action visible. The same principle can apply to city services.
The goal is not one giant control center for everything. It is enough shared visibility that separate actors can coordinate around the same outcome.
Complaints are operational data
A complaint is more than dissatisfaction. Repeated complaints can reveal recurring failure points, confusing communication, weak infrastructure, unclear ownership, or a policy that works differently in practice than intended.
Treating those signals as structured feedback can turn service interactions into learning for the wider system.
Closing thought
A city will always be more complex than a single service operation. But the service-system lens is still useful because it changes the question.
Instead of asking only which department owns a task, we can also ask what journey the resident is trying to complete, where that journey breaks, and what coordination is required to make the whole system work.