India has 6,500 global technology and functional leaders*, growing at 40% a year, on track to cross 30,000 by 2030. A decade ago, the number was 115. And yet most GCC heads are still structured as single operational hubs who check everything. That gap, between what Indian GCC leadership can deliver and how centers are actually led, is one of the most expensive problems the industry refuses to name.
*6,500 global technology and functional leaders as of FY 2024
Across 220+ GCC engagements, Zinnov has seen center heads resolve into one of three patterns. The pattern is rarely visible from the outside in year 1. By year 3, it defines everything: the quality of the team, the trust of global stakeholders, the trajectory of the mandate.
GCC heads in India typically resolve into one of three leadership patterns: the cog, who maintains; the clog, who centralises; and the lightning rod, who transforms.
The cog keeps the machine running. The center is stable, compliant, functional. Deliverables are met, attrition is manageable, headquarters is not unhappy. But the center does not compound. It maintains. The cog is indispensable to continuity and invisible to strategy.
The cost: Headquarters respects them, depends on them operationally, and never gives them more. The mandate never expands because no one can imagine the cog doing something different. The center plateaus not with a crisis but with a permanent ceiling dressed up as a steady state.
The clog is what happens when operational control becomes a permanent identity. Every decision routes through them. Partners brought in for specialist expertise get checked, second-guessed, eventually frozen out. Functional leaders learn to wait for approval rather than act on judgment. The center was built to generate momentum. The clog absorbs it.
The cost: The best people leave first, usually within 18 months. They leave for one of three reasons: the work shrank, the ceiling appeared, or the peers left. When the first strong performer goes, it gives the next one permission. Partners disengage. Headquarters recalibrates its expectations downward. The center keeps growing, headcount looks fine, but growth and momentum are not the same thing. By the time someone names the problem, it is years in the making.
The lightning rod transforms what they touch. There is a fact worth borrowing here: when lightning strikes sand, it turns it to glass, something new, something harder, something that was not there before. The lightning rod hires domain leaders and genuinely steps back. Builds direct relationships between India and global teams rather than sitting in the middle. Makes themselves operationally unnecessary, to become strategically essential.
The consequence: The center earns mandate expansion not by asking for it but by demonstrating it. Global stakeholders stop managing the India relationship and start depending on it. A global pharma company’s India center is a useful example. 30-40% of its India leaders now hold global functional mandates, running critical platforms for AI, data, and global operations from Chennai. The center moved from receiving directives to originating the decisions that govern outcomes across geographies. That did not happen because headquarters decided to trust India more. It happened because the center head spent years building toward it.
The difference between these three patterns is not talent or pedigree. It is a choice, made through a hundred small decisions, about what the role is actually for.
A center head is hired for domain expertise, building instinct, the ability to earn trust on both sides of the table. What nobody warns them about is what comes next.
6 months in, the operational weight lands. Hiring decisions. Compliance questions. Partner escalations. A global stakeholder who needs an answer by end of day. The center head steps in and handles it. Then handles the next thing.
In the early days this is necessary. Someone has to hold the center together while it finds its feet.
The problem is when that phase never ends. When handling everything stops being temporary and becomes identity.
That is the fork. And the direction taken there determines which of the three patterns takes hold.
A mid-sized software GCC had been running well for over a year. The team was productive, partner relationships were working, and the global sponsor was satisfied. Then the company brought in a dedicated center head.
Within months the operating rhythm changed. Decisions that had been made by functional leads started routing upward. Partners who had been given clear scope found themselves being checked on work they had been trusted to own. The center head was not obstructive by nature. They simply believed that everything significant should pass through them.
18 months later the global sponsor flew in to ask what had happened. Overall attrition numbers looked fine. What the numbers did not show was that three of the center’s strongest functional leaders had left, the partners with the deepest domain knowledge had pulled back their best people, and the work being produced had settled into a reliable but unremarkable rhythm. The center head was the last to see it. They were too busy.
The pattern endures because the short-term signals point the wrong way.
A busy center head looks like an engaged one. Sign-offs look like rigour. Centralization looks like accountability. For a global sponsor who needs a single point of contact and someone to call when things go wrong, the controlling center head feels reassuring.
The cost is invisible in Quarter 1. It compounds through year 2 and 3.
The lightning rod’s value is harder to see. Decisions that run without them do not get attributed to them. The team they have built does not signal their importance, it signals their absence. In most organizations you do not get rewarded for making yourself unnecessary.
Until the center built the other way starts outperforming yours.
The instincts that built a generation of GCC heads and leadership teams, centralized sign-offs, control as a proxy for quality, one person accountable for everything, were built for a period of stability that no longer exists.
Technical skill half-life is collapsing from 10 years to 2-5. Engineering roles are being redefined mid-tenure.
The skills that mattered at hire may not matter in 18 months. Ben Horowitz’s peacetime versus wartime distinction is useful here: peacetime leaders optimize for process and predictability; wartime leaders optimize for speed, agency, and decisions made close to the work by people who understand it.
The clog is a peacetime leader in a wartime role. A center head who centralizes decisions is not just inefficient in this environment. They are a bottleneck at exactly the moment speed matters most. The organizations furthest ahead have stopped building for the former.
27% of GCCs set up in the last 5 years are already at portfolio or transformation maturity, a journey that traditionally took a decade. The centers getting there fastest share one trait: their leaders distributed authority early and built functional depth rather than operational control.
Most global sponsors evaluate their center head on the familiar numbers: headcount, attrition, cost, delivery. These measure whether the center is running. They do not measure whether it is building.
The better diagnostic is simpler. What does the center do when the center head is not in the room?
If the answer is wait, the center has a clog problem, regardless of what the dashboards say.
If the answer is decide, build, and move, the center has a lightning rod. That center is compounding in ways that will not appear this quarter but will define the next 5 years.
64% of site leaders at India’s most mature GCCs now hold dual mandates, running India operations while also leading global portfolios in product, engineering, or cybersecurity. That is not a coincidence. Those leaders are not running India. They are running something global, from India. The India label has become the least interesting thing about them.
India’s GCC ecosystem has the talent, the track record, and the leadership depth to build this kind of center. The only thing standing between most GCCs and that outcome is a choice about what the center head role is actually there to do.
The cog, the clog, and the lightning rod are often the same caliber of person. What separates them is what they chose at the moments that defined the role.
A center head who becomes a clog will hit a ceiling. The center will hit it with them. By the time it is visible to everyone else, the choices that built it are years in the past.
A center head who becomes a lightning rod builds something that outlasts their tenure, and exceeds what any single person could have produced alone.
The value of a GCC head is not in what they control. It is in what they orchestrate. The best ones have always known the difference.
So the question, not for a direct report, not for a future hire, but for the person reading this:
When the operational pull arrived, what did you choose?
And what is that choice costing you today?
This is the 5th piece in our What No One Tells You series on Global Capability Centers (GCCs). If you’re new here, the earlier articles cover ground worth reading first:
THANK YOU
FOR YOUR RESPONSE
