Effective Government
Government earns trust the slow way, by doing what it said it would do.

The operating principles.
Capacity, not intention
Judge an organization by whether its money, people, systems and decision-making line up well enough that it can actually deliver.
Transparency people can use
A resident should be able to find what something costs and what it will cost in five years.
Share what is merely duplicated
Keep local judgment local and share the things every town does the same way, like dispatch, procurement, training and back-office work.
Process before software
Fix the process first, then pick the software.
People make up their minds about their government in small transactions, like a permit that takes four months instead of four weeks, a road that gets patched three times before anyone rebuilds it, or a budget that balances on paper by pushing an obligation into a future year. None of these would make the news, but people notice, and they draw conclusions about whether their government is serious.
I’ve spent my career on the inside of that problem, first in technology and enterprise architecture, then in public finance, and now as an elected official. When an organization keeps falling short, the cause is usually that its money, structure and operations don’t line up well enough to deliver what it promised.
Transparency people can actually use
Posting a 300-page budget PDF technically counts as disclosure, but almost nobody can use it. Real transparency means a resident, a reporter or a board member can find out what something costs, what it’s expected to cost in five years, and what tradeoff was made to pay for it. That takes deliberate decisions about what gets disclosed and how, which is more work than meeting the legal minimum.
The same goes inside the organization. Boards and councils can’t make good decisions on a packet they received the night before the vote.
Regional collaboration where it actually pays
Southwestern Pennsylvania runs roughly 130 municipalities, most of them separately negotiating the same contracts, separately procuring the same equipment, and separately trying to staff the same services from a shrinking volunteer base. Local control is real and worth protecting. But local control over a trash contract is not what anyone means when they defend it.
The better question is which functions genuinely benefit from local judgment and which are simply being duplicated 130 times because nobody built the shared alternative. Dispatch, procurement, training and back-office administration usually fall in the second group.
Modern service delivery
Most local governments are running processes designed for a paper world, staffed by fewer people than they had a decade ago, against expectations set by every other service in a resident’s life. That gap will not close through effort alone.
Technology is part of the answer, but it’s the easy part. The harder work is fixing the process, which means deciding what a service is actually supposed to accomplish, removing the steps that exist only because they always have, and building the capacity to keep the new way of working going after the consultant leaves. Governments that skip that step buy software and keep their old problems.
Where effectiveness actually fails
The capacity testA service failure is almost never one thing. It is usually one of five systems out of alignment with the others.
Where I have developed the argument in writing.
Occasional notes, when there is something worth sending.
New essays and the occasional working note on public finance, local government, and civic institutions. No campaign mail. No forwarding of your address to anyone.