How Your Rollout in Waves Can End in a Tsunami

14. November 2022
Kategorien
Newsletter abonnieren

Multinational system implementations rarely fail because of technology. They fail because the rollout model collapses under its own operational reality.

One of the most common triggers is a misunderstanding of what a rollout in waves actually implies.

Most organizations believe they are reducing risk when they move away from a big bang deployment. In practice, many simply replace one form of risk with another. Less visible. More persistent. And often far more damaging over time.

To understand why, it is worth separating two concepts that are constantly mixed up in boardrooms and steering committees.

A phased rollout reduces functional scope. The system goes live for all users, but only with a subset of capabilities. A typical example is a CRM rollout where contact and opportunity management go live first, while pipeline management or advanced reporting follow later. The organization limits complexity by limiting what the system is expected to do.

A rollout in waves does the opposite. It keeps the full functional scope intact but limits exposure by rolling the system out to a subset of users, typically by country, region, or business unit. The idea is simple. You learn in one environment before scaling to the next.

On paper, this is sound. In reality, it creates a structural tension most organizations underestimate.

The moment the first wave goes live, the program stops being a project and becomes an operating system.

What many still call “hypercare” is not a temporary phase. It is the beginning of Business as Usual under entirely new conditions. Release management, incident management, user support, training, data corrections, interface fixes. All of it starts immediately, and none of it is optional. The volume is not marginal. It is overwhelming.

At the same time, the system reveals its gaps.

No amount of testing replicates real usage across a live organization. Users start to see where processes do not fit, where data does not behave as expected, where reports do not answer the questions they actually have. The result is a surge of change requests. Not cosmetic improvements, but structural adjustments required to make the system usable. Many of them urgent. Some of them critical.

And while this is happening, the rollout is supposed to continue.

Each additional wave requires its own effort. Local discovery. Data migration. Configuration. Training. Regulatory adjustments. What looked like replication turns into re-engineering. Every country introduces variations that need to be absorbed into the core system, often under time pressure and with incomplete information.

This is where most wave-based rollouts start to stall.

Not because the idea of waves is flawed, but because the operating model behind it is.

The most common failure pattern is brutally simple. Organizations treat everything that happens after the first go-live as one problem and assign it to one team.

One team is expected to stabilize the live system, deliver change requests, and prepare the next wave. In theory, this looks efficient. In practice, it guarantees overload, conflicting priorities, and constant context switching. Stability suffers because the team is pulled into future work. Future waves slip because the team is consumed by current issues. Change requests pile up because neither side has the capacity to absorb them properly.

The rollout does not fail overnight. It slows down. Then it fragments. And eventually, it stops.

A rollout in waves only works if the organization accepts that it is no longer running a project, but a system with three competing demands that need to be managed separately.

First, there is the stabilization layer. This is pure Business as Usual. It focuses on keeping the system running, resolving incidents, managing releases, and supporting users. Its success metric is stability.

Second, there is the change layer. This team translates user feedback into system improvements. It prioritizes and delivers change requests, manages enhancements, and evolves the solution. Its success metric is usability and business fit.

Third, there is the rollout layer. This team prepares and executes the next waves. It handles onboarding of new countries or units, including all local adaptations. Its success metric is scale.

These layers are tightly connected, but they cannot be collapsed into one without creating structural failure.

Some individuals may contribute across layers, especially in smaller programs. But as a model, the separation is non-negotiable if the rollout is meant to continue beyond the first wave.

The real mistake is not operational. It is temporal.

Most organizations only start thinking about this structure after the first go-live, when the pressure is already visible. By then, it is too late. The system is live, the demand is real, and the organization is reacting instead of designing.

A rollout in waves does not buy you time.

It consumes it in a different pattern.

If you do not design for that pattern before the first wave goes live, the rollout will not scale. It will stall under the weight of its own success.

In simple terms: a rollout in waves does not require one team that works harder. It requires three teams that are designed differently.

Anything else looks efficient on paper.

And fails in reality.

Tags

Das könnte Sie auch interessieren

The Five Elements of a Strong Governance Structure for Critical Projects

16. Januar 2025

Every executive has nightmares about that project—the one that spirals into an unmitigated disaster.  In general there are four ways a project can end up in a boardroom-shaking failure that can destroy value, reputations, and trust in one fell swoop. 1. The Titanic Failure: The project chugs along, oblivious to the iceberg ahead, burning millions

Weiterlesen

Why Every Critical Project Needs Board Supervision

15. Januar 2025

Projects are like icebergs—what you see above the surface is just the tip. Below lies the complexity, risk, and opportunity that can sink your ship if ignored. Too often, boards treat projects like black boxes, leaving management to deliver results without sufficient oversight. This hands-off approach might work for routine initiatives, but when it comes

Weiterlesen

Why Every Critical Project Needs Independent Reviews

14. Januar 2025

«Trust, but verify.» That timeless adage applies as much to critical projects as it does to diplomacy. Without an independent review, even the best-run projects can veer off course, leaving organizations blindsided by delays, cost overruns, or outright failures. Here’s the uncomfortable truth: internal stakeholders are often too close to the project to see the

Weiterlesen

Why Every Critical Project Needs an Executive Sponsor

13. Januar 2025

Launching a critical project without an executive sponsor is like sending a ship to sea without a captain—good luck steering through the storm. Projects don’t fail because of bad intentions. They fail because of a lack of alignment, authority, and support.  That’s where the executive sponsor steps in—not just as a figurehead but as the

Weiterlesen

Why Every Critical Project Needs a Dedicated Project Manager

12. Januar 2025

Far too often, organizations assign critical projects to people who already have full-time roles or, worse, delegate management to a loosely organized team with no single point of accountability. The results? Missed deadlines, blown budgets, and a whole lot of finger-pointing. Here’s the hard truth: if the project is important, it deserves a dedicated project

Weiterlesen

When $100 Million Technology Projects Fail, It’s the Board’s Fault—Every Single Time

2. Januar 2025

In Switzerland, rumors suggest that both Bank Julius Bär and Raiffeisen Schweiz are grappling with failed technology projects, each costing over $100 million so far. Bank Julius Bär is reportedly trying to replace its existing core banking system for the Swiss booking center with Temenos, while Raiffeisen Schweiz is attempting to build a modern e-banking

Weiterlesen

Top Ten Leading Indicators of Troubled Projects for Executives

5. August 2024

If you are a senior executive or a board member in the role of executive sponsor, project sponsor, or steering committee member it is key to recognize potential issues before they become critical.  Recognizing early warning signs can make the difference between a project’s success and failure.  Whilst lagging indicators are metrics that reflect past

Weiterlesen

Why Every Critical Project Needs a Steering Committee

28. Juli 2024

Critical projects are like Formula 1 races—you don’t just need a driver; you need a pit crew, strategists, and decision-makers ready to adapt in real time.  That’s your steering committee. Big projects come with big risks, competing priorities, and high expectations. Without a steering committee, those challenges turn into roadblocks. Decisions get delayed, alignment falters,

Weiterlesen

The Most Important Role on Any Large Transformation Project

22. Juli 2024

The most important role on a large transformation project is the project sponsor.  Not the project manager.  According to the Project Management Institute (PMI)’s 2018 Pulse of the Profession In-Depth Report, «1 in 4 organisations (26%) report that the primary cause of failed projects is inadequate sponsor support«.  By contrast, «organisations with a higher percentage

Weiterlesen

Project Trouble Assessment for Executives

17. Juli 2024

Is your project headed for trouble?  Find out! If you are a senior executive or a board member in the role of executive sponsor, project sponsor, or steering committee member it is key to recognise potential issues before they become critical. Recognising early warning signs can make the difference between a project’s success and failure.

Weiterlesen