On paper, your operations manager runs operations.
Your sales lead runs sales. Your production manager runs production. The boxes are there. The lines are drawn. The titles are real.
But when something goes sideways, a crew conflict, a customer escalation, a job that falls behind schedule, everyone ends up in your office. Not because they can’t handle it. Because the org chart never told them they were supposed to.
The structure on paper and the structure in practice are two different things. And the gap between them is where most of your daily friction lives.
An Org Chart Is Not an Operating Structure. It’s a Reporting Diagram.
Most org charts tell you who reports to whom.
They don’t tell you who owns what outcomes. Who makes which decisions independently. Where one person’s authority ends and another’s begins.
That information, the operational structure, is almost never written down.
So people fill the gaps informally. They make assumptions about what they own based on their title, their relationship with the owner, and what they’ve gotten away with or been corrected on in the past.
The result is a shadow org chart, the actual map of how decisions get made, who people really go to, and where work actually flows, that bears only partial resemblance to the one on the wall.
Until the shadow org chart and the official one match, you don’t have a structure. You have a hierarchy with an informal operating layer on top of it.
The Plumbing Company With Three Operations Leaders and No Clear Operations Owner
I worked with a plumbing contractor about a year ago. Twelve million in revenue. His org chart showed an operations manager, a field supervisor, and a service coordinator, three distinct roles with three distinct titles.
In practice, all three of them were making decisions that overlapped with each other constantly.
The operations manager would set the dispatch schedule. The field supervisor would change it based on what the crews told him. The service coordinator would reroute jobs based on customer calls, without telling either of them.
Every conflict, and there were several every week, ended up with the owner making the call. Not because he wanted to. Because no one had ever drawn a line that said: when these three roles disagree, this is how it gets resolved, and this is whose call it is.
The org chart had three boxes. None of the three boxes had defined decision rights. So the informal layer took over and the owner became the tiebreaker for every ambiguous situation.
That’s not an accountability problem. It’s not a communication problem.
It’s an ownership design problem. The roles existed. The authority boundaries didn’t.
What an Operational Structure Actually Requires
A real operating structure answers three questions for every seat in the business.
What does this person own completely? What do they flag before acting on? And what do they never touch because it belongs to someone else?
The Results Ownership Map is the document that answers all three.
Not a job description. A job description tells you what someone is responsible for in general terms. A Results Ownership Map tells you exactly what outcomes this person drives, which decisions are theirs to make without asking, and where their authority ends relative to every other seat in the business.
For the plumbing contractor, that meant three documents, one for the operations manager, one for the field supervisor, one for the service coordinator, that drew the lines explicitly.
The dispatch schedule is owned by the operations manager. Changes to it require her sign-off. The field supervisor surfaces conflicts but doesn’t unilaterally reroute. The service coordinator reroutes within defined parameters and flags anything outside them.
Once those lines existed in writing, the owner stopped being the tiebreaker. The map was the tiebreaker.
This work is part of what Base Camp — the initial multi-day alignment session inside PBOS — is designed to do.
Not build an org chart. Build an operating structure where the authority boundaries are explicit, agreed upon, and documented so the business can actually run against them.
The org chart shows the hierarchy. The operating structure tells people how to use it.
What the Gap Between Org Chart and Reality Keeps Costing
Every decision that falls into an undefined gap routes to the owner.
Not because the team lacks judgment. Because the structure never told them they had the authority to use it.
Roles with overlapping ownership produce friction between departments that is experienced as a personality conflict but is actually a design problem.
The operations manager and the field supervisor aren’t clashing because they don’t get along. They’re clashing because they both believe they own the same thing and the org chart never told either of them otherwise.
The business stays slower than it should be. Every ambiguous situation triggers a pause, a conversation, an escalation.
Speed, margin, and capacity all get taxed by a shadow operating layer that the official org chart pretends doesn’t exist.
A business Built to Sell or Built to Sail™ has an operating structure that runs without the owner filling the gaps. The org chart is accurate. The authority is explicit. And decisions get made at the level they belong, not at the top by default.
If Your Org Chart and Your Operating Reality Don’t Match, the Gap Is Costing You.
If decisions keep escalating to you that should be handled below you, the ownership boundaries haven’t been drawn clearly enough. I do a 30-minute Discovery Call where we look at where the operational structure is informal, where authority overlaps, and what it would take to make the org chart reflect how the business actually runs. No pitch. Just a conversation about where your business is and what’s in the way.