Many organizational problems aren't people problems. They're systems problems. The challenge is that "systems problem" isn't a diagnosis. So where do you start? When I'm trying to understand why a process isn't working, I don't start with solutions. I start with questions. Who owns the process? Can anyone see where work is sitting? Where does work change hands? Is the process documented? How do people report problems, and what happens after they do? None of those questions

We love the myth of spontaneous collaboration. A brilliant idea > A quick meeting > Everyone jumps in > Magic happens. Except that's usually not what happens. Good outcomes rarely happen by accident. They happen because someone thought about the process. Collaboration without preparation is interruption. It might be important interruption. But it IS interruption. And spontaneous collaboration is really just unplanned work. Now someone has to: Context switch > Stop current wor

A 60-minute meeting recording is not a meeting summary. A transcript is not a procedure. A Teams recording is not a training resource. And "it's in the recording somewhere" is not a documentation strategy. Many of us have probably found ourselves digging through old recordings (or *ahem* 36,910 screenshots) trying to answer what should have been a simple question. The information technically existed. Somewhere. In a recording. Maybe in a transcript. Possibly in a Teams chat.

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

“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

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

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