GBS Process Discovery Before Migration

Process discovery is not documentation work. It is risk control, and in most GBS migrations, it does not receive the discipline it deserves. Organisations spend considerable energy planning transitions schedules, knowledge transfer dates, and go-live deadlines, while far less attention goes to understanding how work actually flows across the organisation. Not the process written in manuals, but the process people follow every day.

That gap is where migrations quietly fail.

>> The Work Behind the Work

Across many GBS transformations we have supported, we see the same pattern. Process manuals describe how work should happen, but operational reality often contains additional steps, workarounds, and local variations that were never formally documented, and these differences remain invisible until migration begins. Process discovery is treated as documentation work. Process discovery exists to surface that hidden complexity before it moves. When this step is rushed, that complexity does not disappear. It simply moves into the GBS.

>> Why Process Discovery Matters

Large organisations operate across multiple countries and entities, and core processes such as O2C, P2P and R2R rarely operate in a single consistent way. Over time, local teams adapt the process to their environment – regulatory requirements introduce additional steps, systems create manual workarounds, and teams develop practical fixes to keep operations running, some of which persist simply because that is how the work has always been done.

After years of these adjustments, the process shown in documentation often looks very different from the process people actually perform. Because operations continue to function locally, leadership rarely sees the gap.

Process discovery exists to make these differences visible before migration begins. When those differences are not resolved early, the GBS receives processes that behave differently across entities – exceptions increase and teams begin escalating issues that were previously hidden inside local operations.

The migration did not create the problem. It exposed it.

>> Signals That Process Discovery Was Incomplete

In most organisations, the signals appear only after migration begins. Local entities begin requesting frequent exceptions because process rules were never clearly defined. Different countries escalate the same issue for different reasons because the process was never aligned. Documentation exists, but teams interpret it differently because key decisions were never made during process discovery.

When these signals appear, the GBS is expected to stabilise the situation – often while being held accountable for problems it did not create.

From our experience, this is where many organisations realise the migration did not create complexity. It only made it visible.

>> Why Fit Gap Discipline Matters

In many migrations we have worked with, the challenge is not the fit-gap analysis itself. It is whether leadership treats this phase with enough discipline to resolve what the analysis reveals. Fit gap analysis correctly identifies differences between global process design and local operations, but the decisions that should follow are often delayed or avoided.

Local process variants are documented but left unresolved, entities continue expecting their previous way of working, and global standards remain theoretical because leadership hesitates to enforce them. When migration proceeds under these conditions, the GBS becomes the place where these unresolved differences surface.

Fit gap discipline changes this.

It requires leaders to decide which variants remain due to regulatory requirements, which historical practices should be removed, and which processes must follow the global standard, because only after these decisions are made can the final process be clearly documented and consistently executed.

Analysis identifies the differences. Discipline ensures those differences are resolved before migration.

>> When Fit Gap Discipline Is Weak

Migration may still go live on schedule, but instability usually appears soon after. Exceptions increase because local entities continue operating differently, confusion develops between GBS teams and business units, and escalations grow because process expectations were never aligned. In many situations, the GBS is blamed for service issues even though the underlying problem existed long before migration began.

The issue is not GBS performance. It is unresolved process complexity.

>> Visibility Before Migration

Process discovery is ultimately a visibility exercise – one that reveals how processes actually operate across entities, exposes the distance between global design and operational reality, and most importantly, allows leadership to resolve those differences before migration happens.

When process discovery and fit gap discipline are handled properly, the GBS receives stable processes that can operate consistently across locations. When they are rushed, the GBS inherits unresolved complexity.

In GBS migrations, speed does not create stability. Visibility does.

But even when processes are clearly understood and documented, one critical question still remains: can the new team actually run the work independently?

In the next article, we examine why knowledge transfer should not be treated as a simple handover activity.