A lot has been written about Global Capability Centers. What a GCC should look like, why ownership matters more than headcount, why talent arbitrage is the real story. But it has a blind spot you only see from inside. It’s easy to write about what a GCC should be. It’s harder to talk about what happens when headquarters has to decide how much ownership it is actually willing to give.
I’ve been part of setting up a few GCCs, and I have compared notes with several other leaders navigating similar decisions in their own organizations, and what follows is the pattern that kept emerging, almost identically, across those conversations.
Why Mandates Get Pulled Back
If you are part of a GCC, you will probably hear at some point that the mandate is being “realigned”. Sometimes that is a genuine strategic call. But often the reason is less strategic than it appears, and it tends to come in a few flavors.
The first is a gap between expectation and reality: HQ hoped to get strategic work done at a lower cost but couldn’t move that work out because letting go of control is harder than it sounds. So, the GCC is left with a mandate on paper and little substance underneath.
The second is almost the opposite: Your GCC is doing great work, and HQ starts to question where certain decisions should sit. Anything with real decision rights begins to look like it belongs closer to home. It rarely announces itself as a loss of trust. It shows up as a redrawn reporting line, a new approval requirement, or a roadmap conversation quietly moving elsewhere. The building stays in India. The deciding doesn’t.
The third is a leadership change: A new leader takes over at headquarters or within the GCC and reassesses strategies set by their predecessor. That’s not unreasonable. New leaders are supposed to bring scrutiny. But in practice, it often means the GCC’s mandate gets frozen while the questioning happens. Work stops flowing because teams become cautious about committing new scope to a relationship under review. What’s left is capacity, infrastructure, delivery muscle, with nothing substantial being routed to it.
The fourth is the one GCC leaders do not always enjoy listening to: Not every loss of mandate starts at headquarters. I’ve seen GCCs mistake scale for strategic relevance and headcount growth for influence. The case for ownership weakens when the center cannot connect its work to business outcomes, develop leaders who can carry enterprise accountability, or make difficult trade-offs independently. Mandates are rarely sustained by capability alone. They survive because the business trusts the people making those decisions.
The Cycle You Will Probably Go Through
It usually starts with real ambition. India will own engineering, product, design, the full stack, and for a while, it works. Then product and design get pulled back, and your GCC becomes an engineering site. Efficient and reliable but stripped of the work that excited people in the first place.
Eventually the separation starts creating its own problems. You cannot permanently separate those building the product from those deciding what to build and expect either to excel. So, headquarters swings back and hands product to India again, almost as a new decision.
I have rarely seen a warning stop this cycle. In conversations with multiple GCC leaders, the details change, but the pattern usually doesn’t. Every leadership team that’s about to hand product back to headquarters believes their situation is different, that this time an engineering-only model will work because it will be managed better. Nobody sets out to repeat a mistake. They just don’t recognize the cycle until they are already living it.
The Sentence That Settles the Argument
If you’ve been in enough of these rooms, you’ll recognize it: “This needs to be closer to the business.” Sometimes that is genuinely true. But it gets used more often than the situation actually justifies, because it sounds like good management rather than a control decision, and arguing against it sounds like arguing against customer centricity itself.
It is, however, harder to defend today. Online meetings, chat groups, war rooms, and occasional travel offer more ways than ever to stay close to the business.
I’ve seen this work in practice. Across organizations, I built business-critical products that needed close engagement with the business. I took full accountability and built empowered teams around them, and the model worked so well that it was replicated in other parts of the business. What kept those products close to the business was ownership, more than where anyone sat.
So, before anything gets pulled back, ask what specifically would be lost if it stayed where it is. Name it. If nobody can point to a real capability gap or a proximity requirement, ask whether the decision is being driven by control, uncertainty, or inertia. It’s a harder conversation, which is probably why it is so rarely had.
What Gives a GCC Staying Power
For a GCC to succeed, it needs meaningful end-to-end accountability for at least one business-critical function, with clearly defined decision rights. Other teams can be built around it, but that function needs to be strategic to business growth and clearly valued by headquarters. The GCCs that held their ground had an independent charter they could run from India, however small. Credibility came from delivering that function well. Then the conversation about the next mandate changed.
Ownership doesn’t hold by itself. What helps is fairly unglamorous: a written charter defining GCC decision rights, so a new leader inherits a document and not just a relationship; an executive sponsor at headquarters whose goals depend on what the GCC delivers; shared outcome metrics; and a deliberate handover whenever a leader changes on either side, ideally before the reassessment begins.
Otherwise, you may have built a very good delivery organization, but not the capability center you set out to create.
