How Restructuring Became the Easy Answer — and the Most Common Mistake

The org chart is not where organizational transformation begins. It is the final outcome of a chain that starts with strategy, runs through leadership, culture, and processes, and ends with execution.

Chapter One: The Meeting

The screen displayed a new org chart. Neat boxes, clean reporting lines, and job titles grander than the ones before. One department had moved to a different division. A small unit had been elevated to a standalone department. An old title had disappeared, replaced by a longer one that everyone agreed sounded more modern.

The discussion went on for hours, all of it about who reports to whom.

Who reports directly to the CEO?

Who deserves a General Manager title?

Should HR sit under the CEO, or under Shared Services?

There were plenty of questions, and even more answers.

But one question never made it into the room:

What problem are we actually trying to solve?

Nobody asked whether the strategy was clear.

Or whether decision rights were exercised in practice the way they appeared on paper.

Or whether departments knew how to work with one another.

Or whether decisions were slow because of too many management layers, or because managers were afraid to make them.

The structure was there in every detail.

The organization itself seemed to be missing from the meeting.

People left feeling reassured. They had made a big decision, or so it seemed. New memos would go out, signatures would change, and some employees would need to update their titles on LinkedIn. All of these were signs that something important had happened.

A few months later, decisions were still slow.

Departments were still passing the buck.

Customer complaints kept coming.

The old problems returned, this time under new titles.

And here lies one of the most persistent paradoxes in management:

The boxes change quickly. The behavior inside them takes more than an executive decision.

 

Chapter Two: The Defendant Who Never Speaks Up

I have yet to meet a manager who, at the start of an organizational crisis, said:

“The problem is how I lead.”

But I have often heard:

“The problem is the structure.”

And the reason is understandable.

Structure is a convenient culprit.

It doesn’t object, doesn’t offer its own version of events, and doesn’t ask to see the findings. It can be blamed for slow decisions, poor collaboration, rising costs, and declining performance, without ever raising its voice in its own defense.

Admitting the problem might lie in leadership, culture, or conflicting interests is far less comfortable.

Because changing the structure asks us to move other people.

Changing leadership may ask us to start with ourselves.

That is why, in times of crisis, structure becomes the organizational scapegoat. We pin on it problems it never created, redraw it, and expect it to fix what we lacked the courage to confront.

There is a psychological comfort in restructuring.

It creates a sense of momentum.

And in management, momentum is easily mistaken for progress.

Workshops are held, models are drawn, and a “new chapter” is announced. Everyone feels the organization is transforming, even though real transformation may not have begun at all.

An organization doesn’t change when its map changes.

It changes when the way decisions are made changes, along with how authority is distributed, how work flows, what gets rewarded, and what behavior is accepted.

All of that is much harder than drawing a new box.

 

Chapter Three: The First Wrong Question

A restructuring project usually begins with a question that sounds perfectly reasonable:

“What is the right structure for us?”

But that question comes too late.

The question that should come first is:

“What strategy do we want this structure to serve?”

And before that:

“What problem is preventing us from executing that strategy?”

Without a clear answer, the debate about structure happens in a vacuum.

A company may choose a centralized structure when its strategy demands fast decisions close to the customer.

It may choose decentralization when its business needs standardization and cost control.

It may adopt a matrix structure in pursuit of collaboration, only to discover that its managers have no culture of sharing authority in the first place.

In each case, the structure didn’t fail on its own.

It was asked to resolve a contradiction that reporting lines never created, one that came from decisions left unmade before the chart was drawn.

This is why there is no universally successful structure.

There is only a structure that fits a specific strategy, at a specific stage, within a culture and set of capabilities able to run it.

What fits today may become a burden tomorrow.

The problem isn’t that structures change.

The problem is that some organizations change them before understanding why.

 

Chapter Four: Different Schools, One Verdict

Management models go by different names, but strikingly, they tend to arrive at the same warning.

The Harvard model starts with strategy.

Burke-Litwin starts by understanding the forces that drive an organization, from the external environment, leadership, and culture to systems and performance.

McKinsey’s 7-S refuses to reduce the organization to its structure, placing it alongside strategy, systems, skills, staff, style, and shared values.

Galbraith’s Star Model makes structure just one of five points, alongside strategy, processes, rewards, and people.

EFQM doesn’t stop at asking what the organization changed. It looks at whether results actually changed.

It is as if these schools, despite speaking different languages, came together to tell every leader the same thing:

Don’t start at the end.

Structure is not the organization.

It is one expression of it.

It doesn’t create strategy; it is built to serve it.

It doesn’t create culture; it reveals some of its effects.

It doesn’t guarantee execution; it can only enable or obstruct it.

Fixating on structure is like redrawing the floor plan of a house when the real problem is in the foundations.

 

Closing: The Question That Should Come First

Was the structure ever the problem?

If structure is the first thing an organization reaches for when it stumbles, why is it so often the last thing to change its results?

Share your love
Avatar photo
Feras Fahad Aloraedi
Articles: 5

Leave a Reply

Your email address will not be published. Required fields are marked *

Working Hours

  • Mon - Fri 9AM - 8PM
  • Sat - Sun 10AM - 5PM

الشبكات الاجتماعية

تواصل