Operating Model vs. Org Chart: Why They're Different

A reorganization gets announced, usually with real fanfare and a genuinely well-produced town hall presentation. Boxes move on a chart, new reporting lines get carefully drawn and re-circulated, new titles get printed on new business cards, and everyone in the organization waits, with varying degrees of patience, for things to actually start feeling different. Often, disappointingly, they don't. This isn't because the reorg was badly designed, or because the people who designed it were careless or unsophisticated. It's because an org chart and an operating model are two genuinely different things, describing two different layers of how an organization actually functions, and redrawing one of them doesn't automatically, or even usually, change the other. This exact disappointment plays out enough times, in enough organizations, across enough industries, to be best thought of as one of the most predictable and most avoidable disappointments in corporate life.

open_in_full

What an org chart shows, and what it hideslinkshare

An org chart shows who reports to whom, and it's genuinely useful for exactly that specific purpose: clarifying formal reporting lines, spans of control, and who is accountable for what on paper, for the purposes of performance reviews, compensation, and formal escalation. What it doesn't show, and was never designed to show, is how decisions actually get made day to day, in the messy, informal, human reality of an organization running under real time pressure. Who gets consulted, quietly, before a production schedule changes? Whose informal sign-off does a plan genuinely need, even though that requirement appears nowhere on any process document anyone could point to? Which relationships carry more real, practical influence over an outcome than the formal reporting line would ever suggest to someone reading the chart cold?

That informal decision architecture, built up over years of people learning, through direct and sometimes painful experience, who actually needs to be looped in, is often far more stable, far more durable, and far more resistant to change than the org chart sitting nominally on top of it. That durability is exactly why redrawing the chart so often changes far less than everyone involved genuinely expected it to.

The elements of a real operating modellinkshare

An operating model captures the things an org chart is structurally incapable of capturing, however well designed the chart happens to be. It captures where decision rights actually sit in practice, as distinct from where they're formally assigned. It captures what information genuinely flows to whom, through which channels, and how much of it arrives filtered, delayed, or quietly reshaped by the time it reaches the person meant to act on it. It captures which processes are genuinely standardized across the organization versus which ones are locally flexible in ways nobody has ever written down. And it captures how accountability is actually enforced in practice, who genuinely faces real consequences when something goes wrong, rather than how accountability is described on paper in a job description nobody has reread in years.

open_in_full

Two organizations can have identical-looking org charts, box for box, line for line, and have completely different operating models underneath them, because the same boxes and lines can support very different underlying patterns of how decisions genuinely get made. This is, arguably, the single hardest part of this idea for most leadership teams to fully internalize. The chart and the model are not two views of the same thing. They are two different things that happen to sometimes overlap, and treating an update to one as an automatic update to the other is where a great deal of reorganization effort quietly goes to waste.

Why redrawing boxes rarely changes behaviorlinkshare

The gap between the two explains a familiar, recurring disappointment that plays out almost identically across very different industries. A reorganization happens, the new chart looks genuinely cleaner and more logical than the one it replaced, and six months later the same specific people are still being informally consulted before anything significant moves, the same unwritten approvals are still quietly required before a decision proceeds, and the same bottlenecks are still functioning as bottlenecks, just now reporting, on paper, to someone with a different title than before.

Behavior, in any organization, is governed overwhelmingly by the operating model, not by the chart hanging in the boardroom. If a reorganization didn't deliberately and specifically touch decision rights, information flow, or how accountability actually gets enforced day to day, it was never realistically going to change behavior in any meaningful way, however logical and well considered the new formal structure looks on the page. This isn't a criticism of the people designing these reorganizations. It's simply a description of how much harder the informal layer is to actually move compared to the formal one, and how easy it is to mistake progress on the easy layer for progress on the hard one.

Diagnosing your actual operating model versus your official onelinkshare

The way to find your organization's real operating model, as opposed to the one implied by its official documentation, is to trace a handful of recent, genuinely real decisions backward, step by careful step. For each one: who was actually consulted, in what specific order, and for what reason, not who the process document says should have been consulted, but who genuinely was, based on honest recollection, calendar invitations, and email threads rather than on what anyone assumes should have happened.

Do this exercise for four or five recent decisions, chosen somewhat at random rather than cherry-picked to prove a point, and a pattern usually emerges surprisingly quickly, often revealing an operating model quite different from what the org chart or the official process documentation would lead an outsider to expect. This gap, once it's made visible through the exercise, is usually far more informative than the chart itself, because it shows you, with real specificity, where the actual leverage points for organizational change genuinely are, as opposed to where the org chart implies they should be.

What this means for anyone trying to speed up decisionslinkshare

This distinction has real, practical teeth beyond being an interesting observation about organizational behavior. If a leadership team is trying to speed up a particular category of decision, approvals, escalations, capital requests, whatever the specific bottleneck happens to be, redesigning the org chart in isolation will very often accomplish close to nothing, because the actual friction lives in the informal operating model, not in the formal reporting structure that the chart describes. Similarly, if an organization is trying to genuinely empower a newly created role, a new head of digital transformation, say, or a newly elevated operations lead, giving that role an impressive title and a clean box on the chart doesn't automatically confer the informal standing that real decision-making influence actually requires. That standing has to be built deliberately, through visible early wins and consistent, reliable follow-through over time, and it takes considerably longer to build than it takes to redraw a chart.

A short diagnostic before the next reorganization is finalizedlinkshare

If you're facing a reorganization decision right now, or suspect one is coming, there's a fairly quick way to test whether the proposed change will actually touch the operating model before it gets finalized and announced. Take the three or four decisions that currently frustrate people most, the ones that take too long, or that seem to require sign-off from someone whose formal role doesn't obviously call for it, and ask, for each one, exactly which specific person's informal involvement the new structure is meant to change. If the honest answer is "we're not sure, but the new structure feels cleaner," that's a signal the reorganization is addressing the chart rather than the model. If the answer names a specific person, a specific point in the decision chain, and a specific reason that person's involvement will genuinely change under the new structure, you're looking at a reorganization with a real chance of changing behavior rather than merely changing labels.

It's also worth asking a slightly uncomfortable, and often revealing, follow-up question: is the organization genuinely prepared to actively manage the transition of informal influence, or is it simply assuming the new chart will handle that transition on its own, without anyone having to do the harder work of actually redirecting it? Typically, the reorganizations that do succeed in shifting the operating model are the ones where someone senior explicitly and visibly redirects requests to the newly empowered role for a sustained period, deliberately routing questions there, deferring to that person in meetings, being seen to do so repeatedly, rather than simply announcing the new structure and hoping the informal patterns catch up on their own. Left to itself, an informal pattern built up carefully over years rarely reorganizes itself just because a chart changed somewhere above it. It has to be actively, visibly, and repeatedly redirected by people whose own behavior others in the organization are already watching closely and quietly following.

The planner who kept the real decision no matter who sat above herlinkshare

A reorganization at one organization moved a planning function under a new vice president, with a genuinely cleaner-looking reporting structure and clearer, more logical titles throughout the affected part of the business. On paper, it was hard to argue with. The new structure addressed several long-standing complaints about unclear accountability, and the leadership team that approved it did so with real confidence that it would meaningfully speed up how planning decisions moved through the organization.

Six months later, nothing about how schedules actually got changed on the ground had meaningfully shifted. The informal decision path, who genuinely got consulted, and in what specific order, before a schedule change actually went ahead, remained exactly, almost precisely, where it had always been, entirely unaffected by the new reporting lines drawn confidently above it. The new vice president was informed of changes, courteously and on schedule, but the substantive decision-making continued to run through the same specific, experienced planner who had held real informal influence over these calls for years, regardless of who that planner's manager happened to be on any given week. The org chart had changed, cleanly and visibly. The operating model, the thing that actually governed how the decision got made, had not moved an inch. It took a fairly candid conversation, a full six months after the reorganization had been announced with such confidence, for anyone in leadership to actually notice.

If the reorg didn't touch who decides what, it changed the chart, not the modellinkshare

open_in_full

Before the next reorganization in your organization gets announced as the fix for a behavioral problem or a decision-speed problem, it's genuinely worth asking, directly and specifically, whether the proposed change actually touches decision rights, information flow, and real accountability, or whether it only touches the boxes and the lines connecting them. A reorganization that leaves the underlying operating model untouched will reliably produce a cleaner-looking chart and precisely the same underlying behavior it was meant to fix, which is rarely, if ever, what anyone in that boardroom actually signed up for when they approved it.

If you want a quick way to test this before your own organization's next reorganization gets finalized, trace three recent decisions the way described above, and ask each proposed structural change a direct, specific question: does this particular change alter who was actually consulted in that decision, or does it simply relabel the box that person already sat in? The answer tends to tell you, well before the new chart is ever printed, whether you're about to change how your organization actually works, or simply change what it calls itself on a slide that gets filed away until the next reorganization comes along to repeat the same well-intentioned exercise.

Disclaimer

Industry situations in this chapter are composite illustrations unless explicitly attributed to a public source. They are not claims about any particular company, plant, vendor, or incident. External standards, research, and public case studies should be verified before publication. Implementations must be validated against local safety, quality, cybersecurity, regulatory, contractual, labour, privacy, and data-governance requirements. AI recommendations and autonomous actions should remain within clearly defined human authority, operational controls, and tested recovery procedures.

#OperatingModel #ManufacturingLeadership #OrganizationalDesign #SteelIndustry #OperationsExcellence #ChangeManagement #PlantManagement #DecisionRights #Industry40 #ExecutiveLeadership