Why Organisational Design Matters More Than Strategy

A case study in operational friction

A hotpot chain in Singapore that started with one flagship outlet that worked almost too well: simple menu, fast turnover, strong margins, loyal customers.

Nothing complicated.

When the founder decided to expand, the thinking was straightforward:

If outlet A works, replicate it for outlet B. Then repeat for C,D... same thing.

On paper, it made perfect sense.

The Expansion Plan That Looked Right

The first few new outlets opened quickly.

Same branding. Same menu. Same kitchen setup. Same hiring profile.

The founder was also deliberate about one thing:

keep the structure flat.

No unnecessary bloat, stay lean, stay agile.

At the same time, to "professionalise" the business, he brought in experienced hires:

A CFO from a regional retail group.

A HR Director from hospitality.

An operations lead from a global facilities management chain.

From the outside, it looked like a business maturing nicely—growth plus capability.

Strategy? Solid.

What Started Happening

Nothing broke overnight or dramatically.

Revenue was still coming in. Outlets were still busy. New locations kept opening.

But inside the system, something else was building.

Not failure.

Friction.

At one outlet, procurement started sourcing slightly different ingredients because "supplier A couldn't keep up" and the CFO was questioning ad hoc requisitions from supermarkets that cost more.

At another, the kitchen team adjusted prep processes to deal with peak-hour pressure saying "not enough hands to help out."

The new CFO introduced tighter cost controls—some outlets complied strictly, others found ways around it to keep service moving.

The HR Director rolled out hiring standards, but outlet managers quietly made exceptions to fill urgent shifts.

None of these decisions were irrational. In fact, each made sense locally.

The Illusion of a "Simple Business"

The founder kept repeating a line:

This is a simple business.

At the product level, he was right. Hotpot is not aerospace engineering.

But the business was longer just hotpot.

It had become a multi-site operating system.

Different location.

Different teams.

Different vendors.

Different pressures.

Same concept.

Very different realities.

This is where most scaling businesses misread the situation.

They assume the simplicity of the product equals simplicity of operations.

It doesn't.

Where Strategy Quietly Stops Working

The strategy—to replicate a proven model—was not wrong.

What was missing was the structural design to support replication.

Because replication at scale is not copying; it is controlled consistency across variation.

And that requires architecture.

Instead, what emerged was a familiar pattern: each outlet started becoming its own version of the business.

Not dramatically different.Just slightly… off.

Over time, those small differences began to compound.

• Inventory mismatches.

• Different cost structures across outlets.

• Inconsistent customer experience.

• Managers solving problems in ways that made sense locally—but conflicted with each other at system level.

The leadership team responded the way most do: more meetings. More reporting. More oversight. But nothing quite “clicked.”

Because the issue wasn’t a lack of effort.

It was a lack of structural clarity.

The Real Cost of Friction

What the founder experienced wasn’t chaos. It was something more subtle—and more dangerous: a business that still worked… but required increasing effort to keep it working.

More intervention.More checking.More “quick fixes.”

Margins began to leak quietly.

Not from one big failure, but from a thousand small inconsistencies.

This is exactly the pattern described in our white paper:

Organisations rarely fail because of strategy or talent, but because structural clarity erodes as complexity increases.

Why Hiring Senior People Didn’t Fix It

Bringing in a CFO and HR director didn’t solve the problem. In some ways, it made it worse.

Because now there were more perspectives, more policies, more initiatives—but still no clear architecture tying everything together.

Each leader optimised their own domain.

Finance pushed cost discipline.HR pushed standardisation.Operations pushed speed.

All valid.

But not always aligned in execution.

Without a clear operating doctrine, the organisation didn’t become stronger. It just became busier.

The Shift That Needed to Happen

What the business actually needed wasn’t a new strategy.

It needed to answer a different question:

How is this organisation designed to operate at scale?

Not in theory.In practice.

• Who decides what at outlet level vs central?

• How are suppliers governed across locations?

• What must remain consistent—and what can vary?

• When something goes wrong, how does it escalate, and to whom?

• How does leadership see what’s really happening across outlets without relying on ad hoc updates?

These are structural questions.

And until they are answered deliberately, the organisation continues to rely on improvisation.

Strategy Sets Direction. Structure Determines Reality.

The hotpot chain didn’t fail. In fact, it kept growing.

But growth became heavier: less predictable. More dependent on key individuals. Harder to control.

Because strategy told them where to go.

But structure was supposed to determine how the business actually runs every day.

And that part was left to evolve on its own.

The Takeaway

Most leaders think organisational design is something you “clean up later.”

After growth. After expansion. After things stabilise.

In reality, structure is what allows growth to stabilise in the first place. Without it, expansion doesn’t scale—it stretches.

And stretched systems don’t break immediately. They just get harder and harder to hold together.

If you’re running a multi-site operation—or planning to become one—it’s worth asking a simple question:

Are we scaling a model… or just multiplying variations of it?

If you’re curious where friction might already be building in your organisation, our online diagnostic is a useful place to start.

No pressure. Just a clearer view of how your system is actually operating.

Take Self-Assessment