GCC Playbook
What 13 Years of Building a GCC Taught Me
Not theory. Not frameworks borrowed from consulting firms. These are the lessons learned from building Gartner Digital Markets India from five people to 200+ — and making it strategic.
Capability vs Hiring
Building a GCC Is Not Hiring
"Most GCC leaders confuse building a team with building a capability. They are not the same thing — and the difference shows up three years later."
Hiring is filling seats. Capability building is creating a function that can operate, adapt and improve without constant direction from the centre. The GDM India GCC did not become strategic because it hired good people. It became strategic because those people were organised into a system — with clear mandates, career pathways, quality frameworks and commercial accountability.
The test of a GCC capability is not whether the team can perform when everything is working. It is whether the team can perform when the leader is absent, the market shifts, or the business is acquired. All three happened at GDM India. The capability survived all three.
Scope Expansion
How Strategic GCCs Earn Scope
"The GCCs that earn scope do not ask for it. They demonstrate the capability to handle it — and then wait for the conversation to come to them."
Scope is not given. It is earned. Every expansion of the GDM India mandate — from Reviews to Revenue Operations to AI Transformation — came not from a restructuring exercise but from a demonstration that the current capability could handle more.
The practical implication: do not lobby for bigger mandates before you have delivered on the current one. Master what you own. Make it undeniably good. Then let the results create the conversation about what comes next. This requires patience that most ambitious leaders find uncomfortable. But it is the only route to sustainable scope expansion — one that survives leadership changes, budget cycles and acquisitions.
Growth Architecture
Scaling Capability Before Headcount
"Every time I scaled a team, I had already built the infrastructure to support 3× current volume. Headcount followed capability. Never the reverse."
The instinct when a GCC is growing is to hire first and build systems second. This creates fragility — a team whose performance depends on informal knowledge, individual expertise and the assumption that the same people will always be available.
Scale starts with process design, quality frameworks and knowledge architecture. When these are in place, new people can reach full productivity quickly and the capability does not degrade as it grows. At GDM India, the transition from 50 to 200+ people was smooth not because exceptional people were hired at scale — but because the systems were ready before the people arrived. Build the container before you fill it.
HQ Relationships
Building Trust With Headquarters
"The moment HQ starts treating the GCC as a strategic partner — not a delivery centre — is the moment the relationship changes permanently. That moment has to be earned."
Most GCCs are trapped in a dependency relationship with headquarters: HQ makes decisions, GCC executes. Breaking out of that relationship requires two things: demonstrated judgment and proactive communication.
Demonstrated judgment means making decisions at the GCC level that headquarters would have made — and being right. Proactive communication means surfacing problems before HQ asks, sharing insights that HQ does not have, and providing context that makes headquarter decisions better. At GDM India, the Executive Committee membership was not given — it was the result of years of demonstrating that the India perspective made global decisions better.
Revenue Inside Operations
Creating Revenue Inside Shared Services
"Operations teams sit closer to revenue than they realise. The question is whether anyone is willing to measure it — and own it."
Every shared services or GCC function has latent commercial value — in the vendor relationships it manages, the data it generates, the quality signals it captures, or the operational leverage it creates for revenue-facing teams.
The GDM India GCC did not start as a revenue centre. It became one because Vicky was willing to identify the commercial mechanism, build the case, test the hypothesis with minimal resources, and then scale what worked. The annual revenue impact did not come from a corporate initiative or a strategic mandate. It came from four interns, a proof of concept, and the discipline to follow the evidence wherever it led. Most shared services leaders never ask the revenue question. That is the opportunity.
Leadership Development
Developing Future Leaders
"The measure of a leader is not what they accomplish. It is what the people they developed accomplish — after they are gone."
Leadership development inside a GCC is not a talent programme. It is an operating model. The question is not "who has leadership potential?" — it is "what are we doing, systematically, to develop everyone's leadership capability?"
At GDM India, this meant clear career pathways, stretch assignments with real accountability, mentorship structures built into the operating calendar rather than left to individual initiative, and a culture where failure was treated as data rather than liability. The three consecutive Mentorship Awards were a recognition of outcomes — not effort. The outcome was a team of 10 senior leaders, most of whom joined as individual contributors and grew into their roles under a system designed to develop them.