The dual operating system: accelerating change alongside the line organization

Why are hierarchies slow when it comes to change?

Because they weren't built for it. Traditional management processes are organized around fixed decision paths, and that is exactly what makes them reliable: responsibilities are clear, workflows repeatable, results predictable.

That strength turns into a weakness as soon as the fundamentals shift. If you stay in reactive mode and respond to change only once it has arrived, you won't keep pace with the nature and the speed of that change.

The problem isn't a matter of effort. A hierarchy can try to be as fast as a network, and it won't get there, because every alignment runs through a defined position.

This observation is older than the current debate about agility. It also explains why the same companies look exemplary in calm times and cumbersome in turbulent ones: it is the same trait, a strength in one case and a burden in the other.

The usual answer is to rebuild the structure. New units, new boundaries, new reporting lines. That is expensive, takes a long time and usually doesn't solve the problem.

Why is restructuring rarely the answer?

Because it triggers psychological uncertainty. People who don't know where they'll stand after the restructuring hold back, and holding back reduces exactly the contribution to your goals that you need right now.

In the worse case, open resistance forms. It is rarely directed at the strategy and almost always at the change to people's own situation.

On top of that comes a timing problem. A restructuring ties up leadership's attention for months, and those are the same months in which the new strategy should be picking up speed.

So the question is a different one: how do you gain speed without touching the structure? The answer is a second system that works alongside the existing line organization.

What is a dual operating system?

An internal community of decision-makers, multipliers and supporters from different levels of the hierarchy and different functions, connected across the entire company.

This network doesn't replace the hierarchy. It works alongside it, on the topics the line organization is too slow for, and it reports back into the line.

The second benefit is the one rarely talked about: you become less dependent on the existing leadership cascade and on the middle management layer where change tends to get stuck.

Who belongs in the network?

People with influence in the company, regardless of their position. Anyone people turn to when they want to know what's really going on belongs there.

If you ran your second strategy workshop with a wider group, you already know the candidates. If not, now is the time to find them.

Membership should be voluntary and still selective. An application process sounds like something for a large corporation, and it works just as well in a company with 200 employees: anyone who steps forward wants to make something happen, and that's the most important prerequisite.

A good selection question is: who would you ask if you wanted to know what the workforce really thinks about a decision? The names that come up are your candidates.

Watch for spread across levels and functions. A network made up only of department heads is the leadership team under another name and gives you no additional access to the organization.

How do you get the system running?

In six steps, in the order that has proven itself.

• Start the selection. For the network itself and for a steering group that leads the transformation.
• Set the dates. Kickoff, meeting rhythm and reporting routine, before the work begins.
• Link it to the cascade. The routines of both systems have to fit together, otherwise you end up with two separate worlds.
• Clarify the rules. What can the network decide, what does it hand over to the line organization, and who backs it up?
• Build the communication. A path that runs in both directions, not just top down.
• Develop a narrative. Challenges and promises of impact become the story that holds the whole thing together.

The fourth point is where networks like this fail. Without explicit backing from management, a member gets overruled by their line manager at the first conflict, and after that nobody takes part anymore.

Don't lose sight of the target picture along the way. While you transform, the world keeps moving and there will be adjustments. But without a consistent perspective, an organization still won't get going.

What's different in mid-sized companies?

The scale, not the principle. A company with 150 employees doesn't need a network of 40 people. Eight to twelve are enough, as long as they're the right ones.

The advantage is the short distance. Where management knows everyone, the elaborate selection process falls away and a network can be set up in two weeks instead of two months.

A time limit also helps. A twelve-month membership with the option to extend takes the finality out of the commitment and makes it easier to win over someone whose day-to-day plate is already full.

The downside lies in the same point. Where everyone knows everyone, the temptation is strong to staff the network with the usual suspects. Then you get the same perspectives in a new format.

Count on a year before the second system really carries weight. In the first months it's one meeting among many. Only once the network has pushed something through that the line organization couldn't move does taking part become attractive.

One tip from practice: include at least one person who is skeptical about the effort and whose judgment counts in the company. Convince that person and you convince half the workforce without any further effort.

After six months, deliberately check whether the system is still needed. If the line organization now decides fast enough on its own, it has served its purpose, and ending it properly is better than letting it run on as a mandatory meeting.

Honesty also means this: not every company needs such a system. Where twenty people work and management walks the production floor every day, the network is already there. The effort pays off from the size at which information needs two levels to arrive.