Nothing Is Broken. But Everything Depends on Someone.

The same line. Different organizations.

There's a set of lines I keep hearing, not from one organization, but from many.

• "The buck stops with me."

• "It lands firmly on my shoulders."

• "I don't think people realize how much I'm holding."

• "We haven't created a system where someone else can step in."

They're usually said in passing. Not as complaints, more like facts. Part of the job.

But when you hear them across different organizations, something shifts. They stop sounding like role descriptions and start sounding like something else. Not an individual experience, but a shared condition.

This doesn't describe a role. It describes a system.

The person isn't filling a gap in the system. The person is the infrastructure.

Last week, I wrote about how decisions don't start from a complete picture. They start from whatever can be brought forward in the moment, what's visible, what can be found, what someone remembers. The system never holds the full picture, so the starting point is always reconstructed.

What it looks like when the infrastructure leaves

I spoke with someone who has served as an interim executive director across more than a dozen nonprofits. His job is to walk in after someone has left and figure out how to keep things running.

What he described wasn't chaos. It was something quieter. Grant applications that existed but couldn't be found. Donor relationships that were real but undocumented. Board decisions that had been made but never recorded anywhere the next person could locate. The work existed. The context didn't.

Every organization he entered had to be reconstructed from the beginning. Not because it had failed. Because institutional knowledge had left with a person, and the systems were never built to hold it in the first place.

This is what the failure mode of people-as-infrastructure actually looks like. Not a sudden collapse. A quiet reconstruction, every time, from whatever fragments remain.

The system isn't holding the work. A person is. And when that person is gone, you find out exactly how much they were holding.

The stability is real. It's just not coming from the system.

From the outside, everything looks like it's working. Deadlines are met, reports are submitted, funding comes in, and nothing breaks. But that stability isn't coming from the system. It's being maintained.

Someone is checking what might slip, filling in gaps before they become visible, and making sure the organization doesn't lose its place.

The system works because someone is actively preventing it from breaking.

What looks like a functioning system is often just someone making sure it doesn't fail.

That kind of continuity doesn't transfer. When work moves, roles change, or someone steps away, it doesn't carry forward in a usable way. It has to be rebuilt, not because the work is complex, but because it was never fully held in the first place

The part that's harder to say

The people functioning as infrastructure are usually the last ones to see it.

Not because they lack awareness. Because the holding feels like the job. The context-carrying, the gap-filling, the quiet prevention of things falling through, it doesn't feel like infrastructure. It feels like competence. It feels like leadership. It gets mistaken for what good operators do.

And so organizations keep running. Leaders keep holding. And the gap between what the system can do and what a person is quietly doing for it keeps widening, invisibly, until it can't.

The system works, but only because someone is constantly preventing it from breaking. That's not a role. That's infrastructure. And infrastructure that lives in a person doesn't transfer.

Have you ever thought about what your organization would look like a month after you left?