I accidentally made my best friend move to Columbus, OH. Not directly. She had narrowed her list to Philadelphia, Denver, and Portland. She had good reasons for all three, but I wasn’t convinced she was evaluating the places themselves. I thought she was weighing the idea of these places too heavily. I don’t mind being wrong. I mind making big decisions for reasons that weren’t fully examined. So I built a spreadsheet. Because of course. I researched ~50 cities that seemed to

Yesterday, I wrote about one of the fastest ways to predict implementation problems: ask who was missing from the planning. New Jersey's 2024 OPRA changes are a great example. Commercial vs. Private Requests Intent: Provide agencies with more time and revenue from requests serving a commercial purpose rather than the public interest. Challenge: Agencies now have multiple timelines governing records requests. In well-staffed agencies, that may be manageable. For lone Records O

Most exclusion doesn’t announce itself. It appears as: Forms that assume everyone has the same background knowledge. Office hours that require someone to miss work. Websites that only function on a desktop computer. Public notices written in language that large portions of the community can’t understand. Meetings held in locations that residents can’t access. Hiring processes that reward people who already know the unwritten rules. These are often treated as inconveniences, b

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.

People experience government through systems long before they experience it through politics or policy. Most residents never interact with an organizational chart, strategic plan, budget document, or legislative agenda. They interact with a form, a website, a permit application, a records request, a utility bill, a phone tree, an inspection process, a missed notification, or a confusing instruction. For most residents, the system is the government. When I was a Village Clerk,

A benefit, service, or public right may exist legally, but if the process is confusing, inaccessible, or difficult to complete, the practical result is limited access. There are a million examples; nobody gushes about how much they love the DMV or the utility company. Forms, portals, instructions, deadlines, and follow-up processes are not neutral. They shape who can actually use a service. A good test is simple: can someone unfamiliar with your agency complete the process wi

Ballston Spa’s FOI debate gets at a problem I see often: agencies talk about records access as though the main issue is requester behavior, when the real issue is usually process. Volume is unpredictable. Capacity is limited. Training is uneven. When agencies are not set up to efficiently handle routine requests, legal review, delays, and frustration multiply. All of that is real. But FOI is still a right. It can’t be treated as abuse simply because compliance is inconvenient

Many organizations think trust is built through messaging. It’s not. It’s built through operations. As more organizations experiment with AI in core workflows, the same question keeps coming up: can people trust the system? That question is not answered through branding. It is answered through performance. Do calls get returned? Are deadlines met? Are decisions explained? Are processes fair? Can people access what they need without unnecessary friction? When systems fail, peo