Carl Piva used a smart light pole to describe a common city mistake in the 2018 Constructrr conversation. A team starts with a piece of technology, then searches for a use case that might justify it. He preferred starting with a public need people already understood.
That preference connected his city-platform principles, his caution about raw data, and his final recommendation for a city's first step.
Purpose came before platform architecture
Carl Piva said a city platform needed a purpose tied to quality of life, residents, the environment, and digital access. He also acknowledged how easily the citizen can become distant from daily agency work.
His response was to put the citizen at the center of the design decision. That did not mean every public choice became a direct vote. Carl kept a role for elected officials while describing places where residents should be able to understand and influence a decision.
Data needed interpretation and a culture willing to use it
Carl argued that more data did not guarantee better political decisions. Too much information could become noise, and the same data could be used selectively.
The platform could make evidence available. In his account, public leaders still needed to interpret it and create a political climate in which evidence had value. That human decision remained outside the platform.
Open interfaces supported work across city boundaries
When the conversation turned to open standards and APIs, Carl Piva described shared building blocks that could help services and data connect across municipalities. He used regional federation as an example of cities avoiding a separate closed system for every local service.
In 2018, Carl expected shared interfaces to make cross-city work more efficient. For city leaders, the practical decision was narrower: agree on the limited interface needed to connect different systems without making them identical.
Carl's first move was a benefit residents could see
At the end of the interview, Carl Piva put it plainly: “I would not start with something that's too complex.”
He recommended a simple, visible service that a mayor could explain and residents could recognize before moving into something more complex.
For a city applying that advice, select one resident service with a clear current problem. Describe the public benefit in ordinary language, identify the evidence officials will review, and define only the interfaces needed for that service to connect with existing systems. Let resident understanding of the result inform whether a more complex step follows.
The city platform remains secondary to that resident-centered sequence. The first commitment is to a public benefit people can see and discuss.
