The Problem Is in the Space Between

We recently worked with an organization where a key process was taking up to two months. Clients were getting lost somewhere in the process. Leadership knew something was broken, but couldn’t pinpoint where.

So they did what most organizations do, they looked at each department involved and asked: are you doing your job?

Intake? Yes. Eligibility? Yes. Enrollment? Yes. Client services, support, resources and referral? Yes, yes, yes.

Every department was doing their part. And yet clients were still getting stuck. The process was still taking two months. The problem was still there.

So where was it?

It wasn’t in any one department. It was in the space between them.

The handoffs. The dependencies. The moments where one team’s work ends and another team’s work begins. The places where a client’s file sits waiting because it’s not clear whose job it is to move it forward.

Ten departments touched this key process. Ten. And each one understood their piece. But no one had ever mapped how all ten connected; where the handoffs were, where the gaps lived, where the delays actually came from.

That’s the thing about problems that live in the space between: no one owns them. So no one sees them.

This is the difference between functional understanding and systemic understanding.

Functional understanding is knowing what you do. Your tasks. Your responsibilities. Your piece of the work.

But functional understanding is narrow, even within your own team. You might know your job without fully understanding how it fits into the whole. Why it matters. Who it affects. What happens when it’s late or incomplete or done differently than expected.

Now multiply that across departments. Across locations. Across an entire organization.

Everyone knows their piece. No one sees the whole.

Systemic understanding is different. It means seeing how the parts connect. The handoffs. The dependencies. The upstream causes and downstream effects. The context that explains why things work and why they break.

You cannot make meaningful organizational change from a place of functional understanding.

You can optimize a task, but you can’t improve a process. You can fix a symptom, but you can’t solve the root cause. You can make a change, but you can’t make it stick.

Here’s what it looks like when organizations try to change without systemic understanding:

You fix a problem in one place, and it shows up somewhere else.

You implement something new, and it breaks something downstream no one anticipated.

You roll out a change, but it doesn’t stick, because the people executing it don’t understand how it connects to everything else.

You solve the same problems over and over again.

So what did we do?

We mapped the entire key process lifecycle across all 10 departments. Every handoff. Every decision point. Every gap where the process broke down between teams.

For the first time, leadership could see the whole system, not just the parts. They could finally see where clients were getting stuck, and why. And once they could see it, they knew exactly what needed to change.

That’s what systemic understanding gives you. Not just visibility into the pieces, but clarity on how they connect.

If you’ve tried to make changes before and they didn’t stick, if problems keep coming back, or cross-functional work never gets easier, the issue probably isn’t effort or intent.

It’s that you were trying to fix a system you couldn’t fully see.

Start there.