Your Org Chart Is Lying to You

It is 5:15 PM on a Thursday. You are staring at a fresh PDF of the proposed company structure. The boxes are crisp. The solid lines denote hard reporting. The dotted lines suggest strategic alignment. Marketing now reports to Product. Operations sits under the newly minted Chief Delivery Officer. On paper, it looks symmetrical and neat. You click save, lean back, and feel a brief wave of relief. The messy friction of the last six months is officially solved.

Except it is not.

I know this because three years ago, I was the one who drew those exact boxes. We were launching a major software update, code-named Project Titan, and the friction between our Engineering and Product teams was reaching a boiling point. Deadlines were slipping. Tempers were flaring. My brilliant solution? A massive reorg. I literally sat at my desk, moved 45 people around on a PowerPoint slide, and thought: there. Now they have to talk to each other.

On Monday morning, the new chart goes live. And by Tuesday afternoon, Sarah from Logistics is still bypassing her new manager to message Dave in IT directly, because his approval is the only way to get a shipping label generated. In my case, my shiny new Cross-Functional Pods completely disintegrated by mid-week. Engineers were still ignoring the new product managers and secretly messaging the old engineering leads to figure out what they should actually build.

You fixed the map. But the territory stayed exactly the same.

Why Restructuring Rarely Fixes Anything

We treat reorganisations like a reset button for bad habits. When a department gets bogged down or two teams stop sharing information, the instinctive executive response is to redraw the boundaries. Move the head count. Change the reporting lines. Put a new box on top of the old boxes.

The data suggests this is a costly illusion. A global survey of 2,063 executives by McKinsey & Company found that only 23 per cent of organisational redesigns actually meet their stated objectives.

Why do the vast majority fail? Because a formal organisation chart only shows you authority. It tells you who has the legal right to approve a budget or conduct a performance review. It tells you nothing about how work actually gets done.

During Project Titan, I thought giving the Product VP official ownership over the engineering queue would force alignment. What I failed to realise was that the engineers didn't lack a manager. They lacked a clear way to handle conflicting technical priorities. The reorg didn't fix the code. It just changed who got yelled at when it broke.

Work Flows Sideways, Not Downward

Work does not travel down solid black lines. Work flows across the white space between the boxes.

Think about the last time a critical project stalled on your desk. Was the roadblock caused by a failure of command inside your own team? Or was it sitting in a queue in another department?

In a study of 7,600 managers across 262 companies, researchers Donald Sull, Rebecca Homkes, and Charles Sull found a massive discrepancy in trust. Eighty-four per cent of managers said they could rely on their own boss and direct reports. But when asked if they could rely on colleagues in other functions all the time, that number collapsed to just 9 per cent.

We have spent decades optimising our businesses for vertical control while the actual delivery of value is almost entirely horizontal. When you restructure, you are usually just building thicker, taller walls around the silos. You are making the vertical lines bolder while the horizontal gaps get wider.

The People You're Quietly Punishing

When you redraw an organisation chart without looking at workflow, you also commit a quiet act of sabotage against your most valuable people. Every company has an informal network: the go-to subject experts and the quiet fixers.

Research into collaborative overload by Rob Cross, Reb Rebele, and Adam Grant looked at network data across more than 300 organisations. They discovered that 20 to 35 per cent of all value-added collaborations come from just 3 to 5 per cent of employees.

These hyper-collaborators are the invisible load-bearing pillars of your business.

During my reorg, I completely overlooked a senior engineer named Marcus. Marcus didn't have a fancy title, but he was the informal routing hub who knew how our legacy database interacted with the new frontend. When I moved Marcus to a completely different pod under a new manager, his formal layout changed but the requests didn't stop. He was stuck attending twice as many status meetings for his new role while still fielding late-night messages from desperate colleagues trying to fix the database. Within three months, Marcus burned out and left. The Project Titan rollout ground to a near-total halt.

When you drop a new org chart onto the business, you disrupt these established channels. You force your best people to spend half their week requesting permission through new gatekeepers just to keep doing the work they were already doing. Eventually, the friction burns them out. They resign. And the formal structure collapses inward because the informal scaffolding was kicked away.

What to Fix Instead of the Chart

If the org chart is a lie, what is the truth?

The truth is the interaction. If you want to fix a broken business unit, look at its inputs and its outputs. Track a single customer request or a disputed invoice from the moment it enters the building to the moment it leaves. Watch the hand-offs.

After Marcus left, I finally put PowerPoint away. Instead, I grabbed a stack of sticky notes and tracked how a single feature request actually moved from a customer's lips to code deployment.

We found the real problem. It wasn't a structural issue. It was a flow problem. A feature request would sit in a digital tray for nine days waiting for a budget sign-off from a finance VP who didn't even understand the feature. Moving teams around on a chart would never have fixed that nine-day delay.

You cannot fix a flow problem by changing a job title. You fix it by changing the cadence of communication and removing redundant sign-offs.

The next time you feel the urge to open PowerPoint and start nudging rectangles around a slide, stop. Put the boxes away. Go find the people sitting in the white space, and ask them what is getting in their way.

An organisation is not a drawing of an engine. It is the heat and the friction generated by the parts moving together.

Key Takeaways

• Map a real workflow, not a role. Pick one core business deliverable, such as a monthly client report or a product update, and physically trace every pair of human hands it touches. Count the hand-offs across different departments.
• Audit your digital waiting rooms. Open your shared ticketing systems or project management software and find the exact staging posts where tasks sit untouched the longest. Focus your next operational intervention on the entry point to that queue.
• Identify your informal routing hubs. Ask three team leaders one question: if our official process documentation disappeared tomorrow, who is the first person you would call to get an urgent request pushed through? Protect those people from new administrative burdens.
• Count the required signatures. Look at your standard approval chains and strip out any sign-off step that exists purely to give a manager visibility rather than to catch an active compliance risk.