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

Organizations often invest in new tools to fix existing problems. Sometimes the tools help. Sometimes they expose what’s already broken. When workflows are unclear, ownership is inconsistent, or standards vary across teams, new technology tends to amplify those issues instead of solving them. I’ve seen this happen with records systems, intake processes, and internal tracking tools. The system works as designed, but the underlying process was never clearly defined. Better outc

I’ve worked in government, nonprofit, and private-sector environments, and I’ve noticed something consistent. Most organizations have the same core problems. Unclear ownership. Weak process. Poor communication. Misaligned incentives. Too much urgency and not enough planning. The language changes by sector, but the underlying issues are usually the same. A policy initiative stalls in government. A nonprofit program struggles to grow. A private-sector project misses deadlines.

There’s a difference between a transition question and ongoing reliance. A quick follow-up a week or two after someone leaves is normal. It happens. But when an organization is still calling months later, something else is going on. That’s not about helpfulness or professionalism. It’s about missing infrastructure. If knowledge lives in one person’s head instead of in systems, documentation, and clear handoffs, the work doesn’t transfer. It follows the person out the door. At

Most discussions about records and information governance focus on federal or private-sector frameworks. Those are complex, but relatively structured. Local government is where things get messy. FOIA does not apply to municipal records. For that, you need state law, and those laws vary widely. Just the acronyms can be confusing: FOIL, OPRA, APRA, FOAA, CPRA, GRAMA, IPRA, PIA, Sunshine Law, Open Records... even the baseline is hard to track. Then come the state-by-state nuance

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

Documentation is accountability. The fullest full stop. Every single one of us has been there: "I thought someone else was handling that." "I don't remember agreeing to that." "Nobody told me." "That's not what we decided." "We've always done it this way." “Does anyone remember…?” “I think maybe Mike was supposed to…” Without documentation, we're relying on memory, interpretation, assumptions, and whoever happens to be the most confident person in the room. We need a shared r