Looking back at every GCC launch I have been part of, one early choice shaped almost everything that followed. It was not the location, the hiring plan or the reporting structure, although all of those matter. It was the first workload to move to a GCC. What a new global capability centre does in its first few months becomes the story headquarters tells about it, and that story is remarkably difficult to change once it has been told.
Most leaders make this choice quickly, often under pressure to show savings or relieve an overloaded team at home. The decision can look like a scheduling detail at the time. In my experience across cross-geography engagements spanning more than 14 countries, it is one of the most strategic decisions in the entire GCC journey.
The good news is that this choice is entirely within leadership’s control. With a little deliberate thought, the first workload can become the foundation of trust rather than the source of a reputation the centre spends years trying to escape.
The GCC cost model looks very different once you replace assumptions with real numbers.
Why the First Workload Becomes the Centre’s Reputation
People at headquarters rarely judge a new GCC on its strategy documents. They judge it on what they experience directly: the work that comes back, how quickly questions are answered, and whether problems get solved or escalated. Within a few months, those experiences harden into a shared view of what the centre is capable of. That view then decides what work it will be trusted with next.
This is why the first workload carries so much weight. If it goes well, the centre earns a reputation for reliability, and headquarters starts offering more meaningful work. If it struggles, the label “not ready” appears in conversations, and it tends to stick long after the original problems have been fixed. I have seen capable teams spend two years proving themselves against an impression formed in their first quarter.
Leaders sometimes underestimate how human this dynamic is. A GCC is not judged only by metrics. It is judged by the stories managers tell each other over coffee, and those stories are built from the earliest work the centre delivers.
The Natural Instinct That Sets a GCC Up to Struggle
The most common instinct is to send the work nobody at headquarters wants. Undocumented processes, legacy maintenance, and tasks full of exceptions all seem like sensible candidates. They free up the home team immediately, and on paper the transfer looks efficient. I understand completely why leaders make this choice, especially when the business case was built on relieving pressure.
The difficulty is that this work is hard precisely because it lacks clarity. It often depends on knowledge that lives only in the heads of a few experienced people at headquarters. When it moves to a new team without that context, mistakes are almost inevitable, and they happen in full view of the people who are forming their first opinion of the centre.
The hidden risk is that the hardest work does not test the new team’s capability. It tests how well headquarters documented its own processes, and the new team takes the blame for the gaps.
Within months, the centre is struggling in public, and headquarters concludes that the model does not work. In reality, the model was never given a fair start. I have seen this pattern repeat in different industries, and the cause is almost always the same first decision about what to move.
Choosing the Right First Workload to Move to a GCC
What I recommend now is the opposite of the natural instinct. The right first workload to move to a GCC is well-understood work with a clear owner and a measurable result. It should be important enough that success is noticed, but stable enough that the new team can learn the business while delivering. The goal is a visible win that headquarters can see and talk about.
| Characteristic | Weak First Workload | Strong First Workload |
|---|---|---|
| Documentation | Lives in a few people’s heads | Clearly written and recently used |
| Ownership | Unclear or shared across teams | One named owner at headquarters |
| Success measure | Hard to define or argue about | Specific, visible and agreed in advance |
| Exception volume | High and unpredictable | Low and well understood |
| Business visibility | Invisible until something breaks | Noticed when it is delivered well |
Good candidates are often found in work that headquarters values but does not have capacity to expand. A well-defined product module, a reporting stream with clear rules, or a testing function with established standards can all work well. The common thread is clarity, because clarity lets the new team succeed on its own merit.
Sequencing GCC Work So Trust Grows Naturally
Once the first win is in place, the harder and messier work moves far more smoothly. The centre has credibility, headquarters has confidence, and both sides have learned how to work together. I think about this as a deliberate sequence rather than a single transfer.
- Start with a clear win. Move one well-documented workload with a measurable outcome in the first 90 days.
- Build the working rhythm. Establish communication, escalation and review habits while the stakes are manageable.
- Document as you transfer. Use each handover to capture knowledge that headquarters has never written down.
- Expand into adjacent work. Add related responsibilities that build on what the team already knows.
- Move the complex work last. Transfer legacy and exception-heavy processes once trust and context are firmly in place.
This sequence also changes how the business case reads. Savings may arrive slightly later in the first quarter, but they are far more durable, because the centre is not spending its second year recovering from a difficult start. I covered the importance of this early period in more depth when writing about the first 90 days of a GCC.
The Human Side of a First Win
The first workload matters for headquarters, but it matters just as much for the people in the new centre. A team that experiences early success builds confidence, takes ownership and starts proposing improvements. A team that struggles in public becomes cautious, waits for instructions and avoids risk. Those habits form early and shape the culture of the centre for years.
I have always believed that a GCC becomes a strategic partner only when its people feel trusted to think, not just to execute. That trust starts with work they can genuinely own and deliver well. When I look at the centres that grew into real partners, as I described in building a GCC that operates as a strategic partner, almost all of them had a strong first chapter.
Leaders at headquarters play an important part here too. Celebrating the first win openly, and crediting the new team by name, sends a clear signal across the organisation. It tells everyone that the centre is part of the company, not a cost line sitting somewhere else.
Measuring the First Workload Fairly
Even a well-chosen first workload can be judged unfairly if success is not defined in advance. Headquarters often compares the new centre against an idealised version of how the work used to be done, forgetting the delays and errors that existed before the transfer. Without agreed measures, every small issue becomes evidence that the centre is struggling.
I recommend agreeing three or four simple measures before the first piece of work moves. These might include delivery timeliness, quality against an agreed standard, responsiveness to questions and the number of escalations. Crucially, the baseline should be measured at headquarters before the transfer, so the comparison is honest. In my experience, this baseline often surprises leaders, because the original process was rarely as smooth as memory suggests.
Fair measurement protects both sides. It gives the new team a clear target and the confidence that good work will be recognised. It also gives headquarters an objective way to see progress, rather than relying on anecdotes from the busiest managers. When results are shared openly every month, the conversation shifts from opinion to evidence.
This discipline also prepares the centre for its next stage. Once measurement habits are established on the first workload, they extend naturally to more complex work. The GCC becomes known not only for delivering, but for being transparent about how it delivers, which is one of the strongest foundations for long-term trust across geographies.
Designing the First Chapter Deliberately
The first workload to move to a GCC is never just a transfer of tasks. It is the opening chapter of a relationship that may last many years, and it sets the tone for everything that follows. Choosing clear, owned and measurable work first gives the centre a fair chance to show what it can do.
The harder work will still move, and it should. It simply moves more successfully once the centre has earned trust and built the context it needs. Patience in the first quarter often saves years of rebuilding confidence later.
If you were launching a GCC next quarter, what would be the first piece of work you would trust it with? The answer to that question may shape the centre’s future more than any other decision you make.
The teams that build GCCs that scale always start with one thing: a clear picture of what it actually costs before they commit.
