“This meeting should’ve been an email.” But what about the meetings that needed an email? I can’t count the number of times I’ve participated in a meeting where the meeting happens and… that’s it. That’s the deliverable. No agenda. No recap. No action items. No record that the meeting happened other than a calendar block and, maybe, a recording no one will ever watch, or a transcript someone might dig through later, trying to find what could’ve been documented from the outset

One of the most common operational issues I see isn't complexity. It's unclear ownership. A task gets shared across teams. Responsibility gets assumed, questions get redirected, and deadlines slip. Everyone is involved. No one is accountable. I’ve seen this in policy implementation, internal workflows, and public-facing work. A request comes in, touches three departments, and no one is clearly responsible for seeing it through to completion. Clear ownership doesn't mean doing

Access isn't just a policy value. It's also an operational outcome. People experience access through practical details: Can they find information? Can they get an appointment? Can they understand the process? Can they complete forms? Can they reach a person? Can they get help without starting over? Mission-driven organizations often talk about access in broad terms, but access usually breaks down in specific places. A practical starting point is to map the user journey from t

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

When organizations feel pressure, one of the first instincts is to add people. Sometimes that is exactly right. But frequently the problem only looks like staffing. If workflows are unclear, ownership is fuzzy, tools are outdated, and priorities shift daily, adding headcount will only increase confusion. I’ve seen teams grow without improving outcomes because the underlying process never changed. A practical step before hiring is to map the work: where it starts, where it slo

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.

Modernization is not enough. Redesign is the next step. For years, improvement has often meant layering new technology onto existing systems. That approach can deliver incremental gains, but it is starting to hit its limits. What’s emerging now is something different: a shift toward rethinking how work actually happens. Not just new tools, but: how decisions are made how workflows are structured how teams are organized how data is shared how learning is built into operations

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

Mission-driven organizations are often asked to solve complex problems while operating with thin staffing, aging systems, and constant funding pressure. Passion is essential, but it isn't enough. Strong nonprofits need infrastructure, too: sound governance, realistic staffing models, clear ownership, healthy finances, and practical systems that support the mission. Too often, administrative capacity is treated as overhead instead of impact-enabling infrastructure. The organiz

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

Many executives believe their organizations would struggle to pass an AI governance audit. To those of us who have worked in Information Governance, that is not at all surprising. A lot of organizations are moving quickly on AI adoption while moving slowly on oversight. New tools are being introduced before core questions are answered: Who owns decisions? How are risks reviewed? What data is being used? How are outputs checked? How are records retained? Who is accountable whe

Partnerships don't succeed just because people agree on the goal. Agreement is the easy part. The harder work is building the structure that lets people keep moving together when priorities, capacity, visibility, funding, or timelines start to diverge. Early in my career, I worked for a coalition that struggled when alignment was assumed instead of built. Everyone supported the mission, or so it seemed, but no one had clearly defined expectations, decision rules, communicatio

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

Policy only matters if it can survive implementation. A policy can be legally sound, mission-aligned, and politically popular, but still fail if the operational path is unclear. Who owns the work? How will staff be trained? What systems need to change? Where will people get stuck? How will success be measured? Those questions are not administrative afterthoughts. They are often the difference between a piece of paper and a policy that changes outcomes. A good implementation p

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