The Public Experiences Your Systems, Not Your Intentions

People who design processes tend to focus on what happens inside the organization, but the public experiences what happens outside it.

A delayed response feels like indifference. An unclear process is exclusion. Repeated requests for the same information feel like incompetence. Conflicting instructions feel like nobody is in charge.

Most system failures don’t look like system failures to the people affected by them. They look personal.

Someone assumes they are being ignored. Someone concludes the organization doesn't care. Someone gives up and walks away.

Most government failures are system failures, not policy failures. The policy may be reasonable. The law may be sound. The funding may exist. The staff may be competent and committed. But if the systems connecting those pieces don't work, the outcome still fails.

A benefit can exist on paper while the application remains confusing, documentation requirements are unclear, status updates don’t exist, caseworkers are unreachable, and the process takes six months.

A public records law can guarantee access while requests sit in shared inboxes, responsibilities remain unclear, records are stored inconsistently, and communication happens only after someone follows up.

Permitting rules can be clear while approvals stall because nobody owns handoffs, information gets re-entered multiple times, reviews happen sequentially, and applicants can’t see status.

In each case, the policy remains intact. The experience still fails.

Government succeeds or fails in those tiny moments: the handoffs, workflows, approvals, communication channels, exception handling, and documentation. That is where residents actually experience government.

When a system fails, organizations often look for a person to blame. Sometimes the problem is not a person. Sometimes the system is producing exactly the results it was designed to produce. And the absence of ownership is itself a system design choice.

After years working in and alongside public service, I’ve become increasingly convinced that many organizations diagnose the wrong problem. They think they have a people problem, a training problem, or a technology problem, when the deeper issue is often a system that makes good outcomes harder than they need to be.

That’s why process improvement is so much more than efficiency. The experience created by a system shapes how people view the organization behind it.