Andrew FlynnGovernment · Finance · Civic Institutions
Area of work

Effective Government

Government earns trust by being capable, not by promising to be.

What this means in practice

The operating principles.

Capacity, not intention

Judge an organization by whether its money, workforce, systems, assets, and decision-making are aligned well enough that it can actually deliver.

Transparency people can use

A 300 page budget PDF is not disclosure. Usable means a resident can find what something costs and what it will cost in five years.

Share what is merely duplicated

Local control over judgment. Shared delivery for dispatch, procurement, training, and back office administration.

Process before software

Technology is the easy part. Redesigning the service, then sustaining it after the consultant leaves, is the work.

Public trust is not a mood. It is a verdict people reach after watching whether institutions do what they said they would do.

That verdict is being rendered constantly, in small transactions. A permit that takes four months instead of four weeks. A road that gets patched three times before it gets rebuilt. A budget that balances on paper by deferring an obligation into a year nobody at the table will still be responsible for. None of these are scandals. All of them teach people something about whether their government is serious.

I have 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. What separates strong public organizations from weak ones is almost never the quality of their intentions. It is capacity: whether the money, the structure, and the operations are aligned well enough that the organization can actually deliver.

Transparency that is usable, not just available

Publishing a 300-page budget PDF is not transparency. Transparency is when a resident, a reporter, or a board member can find out what something costs, what it is expected to cost in five years, and what tradeoff was accepted to fund it. That requires deliberate design of what gets disclosed and how, not just compliance with the minimum.

The same applies inside the organization. Boards and councils cannot govern well on information they receive the night before a vote. Decision quality is downstream of information quality.

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 productive question is narrower and more useful: 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 are usually in the second category.

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 only the easy part. The harder work is process: deciding what a service is actually supposed to accomplish, removing the steps that exist only because they always have, and building the capacity to sustain the new way of working after the consultant leaves. Governments that skip that step buy software and keep their old problems.

Where effectiveness actually fails

The capacity test

A service failure is almost never one thing. It is usually one of five systems out of alignment with the others.

InformationHow it failsThe decision is made on a report nobody had time to read.What a resident experiencesAn answer that changes depending on who you ask.What better looks likeBoards and residents can see what something costs, what it will cost, and what was traded away.
ProcessHow it failsSteps survive because they have always been there.What a resident experiencesFour months for a permit that takes four weeks of actual work.What better looks likeThe service is redesigned around what it is meant to accomplish, then staffed to sustain it.
WorkforceHow it failsA vacancy held open long enough to become a structure.What a resident experiencesSlower response, less continuity, and a new face every time.What better looks likeCritical roles filled, training funded, and succession treated as infrastructure.
TechnologyHow it failsSoftware bought to solve a process problem.What a resident experiencesA portal that produces the same delay in a nicer typeface.What better looks likeTools chosen after the process is fixed, and maintained after the consultant leaves.
StructureHow it failsAuthority and responsibility sit in different places.What a resident experiencesNobody can say yes, and nobody has to say no.What better looks likeThe person accountable for the outcome can actually direct the resources that produce it.
Government effectiveness depends on five systems working together: information, process, workforce, technology, and structure. Each has a characteristic failure mode, each produces something a resident can feel, and each has a version of what improvement looks like. Effectiveness is systemic, not rhetorical.
The newsletter

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.