The org chart your team actually follows

Every company has two org charts.

The one on paper, and the one that actually runs the place.

The paper one has clean lines and titles. The real one is a web of informal authority, tribal knowledge, and whoever people actually go to when something breaks. It was never drawn. It assembled itself over time, around the people your team trusts, regardless of what their title says.

Most CEOs know this in the back of their mind and do nothing about it. It feels too intangible to address, too political to name out loud.

But here is what I keep seeing: the companies where this gap is widest are also the companies with the worst internal customer experience.

And most of their leadership teams have never thought about their employees as customers at all.

The idea that your employees are customers isn't a soft, HR-flavored concept. It's a structural one.

Think about it this way. Every employee in your company is receiving something from other parts of the organization: information, resources, decisions, support, clarity. That's the internal transaction. And just like an external customer relationship, the quality of that transaction determines whether the person can do their job well or spends half their day working around broken handoffs.

When Finance takes two weeks to approve something that could have been done in a day, Operations pays the cost. When leadership changes direction without explaining the reason, the team invents one. When a manager hoards information because that's how they maintain influence, the people below them make decisions in the dark.

None of this shows up on a customer satisfaction survey. It just shows up as friction. Slow execution. Good people leaving for reasons that sound vague in the exit interview.

I call this the Internal Delivery Gap: the distance between what your team needs to perform and what they actually receive from the people and systems around them.

Here's what I find interesting when I work through this with leadership teams.

The leaders who close this gap fastest are almost never the ones who launch a new engagement initiative or hire a Chief People Officer to fix culture. Those things can help. But they are downstream of the real problem.

The leaders who close it fastest are the ones who start treating internal communication and internal service with the same rigor they apply to external customer experience.

They ask: if this were a customer-facing process, would we tolerate this lag? If a client had to wait this long for a decision, would we accept that?

The answer is almost always no. The internal version gets a pass because it's invisible to revenue, at least in the short term.

It isn't invisible to the people living it every day.

There is a specific version of this that I see most often in companies between, say, 50 and 300 people.

The company has grown past the stage where the CEO or president has direct line of sight to how information moves. But it hasn't yet built the formal systems to replace what the CEO used to do informally, which was serve as the connective tissue between teams.

So there's a period, sometimes years long, where nobody is performing that function. Teams drift. Assumptions compound. The informal org chart gets more and more disconnected from the official one.

The fix isn't complicated, but it requires the CEO to do something that feels counterintuitive: to stop thinking of internal communication as a nice-to-have and start resourcing it like a critical operational function.

That means someone owns it. There are feedback loops. There are clear standards for how quickly internal requests get a response, how decisions get communicated, how trade-offs get explained.

It sounds basic. It isn't widely practiced.

The companies that get this right end up with something genuinely hard to replicate. Teams that move faster, collaborate better, and don't require the CEO to be in every room to function.

Which is the actual goal.

THIS WEEK'S KEY QUESTION

Pick one internal handoff in your company. One place where one team depends on another to do their job well.

Ask the receiving team: what do you actually need from that handoff, and what do you usually get?

Then ask the delivering team what they think they're providing.

The gap between those two answers is your starting point.

-N.F

P.S. Forward this to one person on your leadership team who runs an internal function. If this triggers a conversation worth having, I'd like to hear how it goes. Reply and tell me.