Built for a moment

Every center is built for a moment. There was a room, once, where it did not exist yet. Someone in that room decided how big it would be. Someone decided what it would be allowed to decide. Someone chose which work would move to it, and which would stay. Someone set how it would be counted in the budget. And someone, usually without writing it down, decided which handful of people would be trusted to make it real.

Five decisions, made at the start. All of them right. They had to be, because the center worked. It delivered what it was asked to deliver, earned trust it was never guaranteed, and grew. If you lead a global capability center today, this is your origin story, whatever the year on the founding slide. It is also, in a way almost nobody notices at the time, the origin of everything this series is about.

The scale of what those rooms set in motion is easy to state and hard to absorb. By Nasscom and Zinnov's latest count, India hosts 2,117 global capability centers employing about 2.36 million people, generating $98.4 billion in revenue, with 506 of the Forbes Global 2000 now operating from the country. The number of centers has grown by roughly a third just since FY2021. Almost every one of those centers began the same way: a moment, a room, five decisions.

And almost every one of them will eventually meet the same quiet problem. The moment passes. The decisions stay.

Growth is where the story turns, and it turns in a way that flatters everyone involved, which is part of why it goes unexamined. A center that doubles has, by definition, succeeded. More work trusted to it, more people hired, more functions under its roof. Nobody audits a success.

But growth does something subtle. It changes what the center is while leaving in place the way it was built. The shape is still the one drawn for a smaller center. The decision rights still sit where they sat on day one, several levels and several time zones away. The work is still divided the way it was first divided, in pieces that made sense to move first. The center is still counted the way it was counted at the start, usually as a cost. And the whole thing still holds together the way young organizations do, on a handful of people who make it work.

I spent seven years inside one of these centers as it grew from its first hires to more than twenty-five hundred people, and I can tell you the strangest thing about this transition: there is no day on which it happens. No meeting where the build officially expires. The center of year seven simply wakes up inside the architecture of year one, and everyone is too busy delivering to notice.

What they notice instead is a pattern. It looks like this.

Sit with each of those for a moment, because each one arrives with its own perfectly reasonable local explanation. The approvals are climbing because the new global process requires it. The departures are a market problem; everyone is losing people. The heroics are just what a committed team looks like. Every explanation is plausible. Every explanation is about the surface.

Here is what I watched happen, more than once, in more than one company. A leadership team meets these signals one at a time and treats them one at a time. The approval problem gets an escalation matrix. The attrition problem gets a retention budget and an engagement survey. The heroics problem gets a recognition program, which is a way of thanking people for absorbing a strain nobody has named.

Picture the quarterly review where this happens, because it happens in a room you know. Item four on the agenda is cycle time, and the room agrees the new approval workflow needs a fast lane for routine items. Item seven is attrition, and the room approves a market correction for two critical bands. Item nine is a delivery risk on the flagship program, and the room notes, with real gratitude, that two senior engineers worked through the holiday to hold the date. Three items, three owners, three actions. The meeting ends on time. Nobody in the room has said anything wrong, and nobody has said the true thing either, which is that items four, seven, and nine are the same item.

Or worse, the signals get read as people problems. The manager who cannot keep up. The leader who left because she "wasn't the right fit for the next phase." The team that "needs to mature." This reading is worse because it is cruel to exactly the people carrying the most, and because it guarantees the pattern will repeat with their replacements. A center can cycle through three generations of managers this way, each inheriting the same impossible shape, each departing with the same private conclusion about themselves.

The signals are neither three separate problems nor a people problem. They are one problem, surfacing in different places: the center has outgrown the way it was built. Once you see it this way, the pattern stops being mysterious. Approvals climb because decision rights were placed when the center was unproven, and nobody moved them when it proved itself. Strong people leave because they are accountable for outcomes they cannot fully decide, or because they are personally holding up a structure that should be holding them. Delivery runs on effort because effort is what fills the gap between the work a center does and the way it was designed to do it.

The rest of this series takes the problem apart into its five surfaces, one essay each. They are worth naming here, in order, because the order itself tells the story.

The strain shows first in Structure: the shape that carried the center up becomes the thing it is carrying. Managers hold more than a manager can hold, and growth gets absorbed by adding people, because the design has no room built into it. It shows next in Authority: the work moved to the center, and the authority to run it did not, leaving leaders answerable for outcomes they cannot fully decide. And it shows in Ownership: work arrived in pieces, the pieces multiplied, and the wholes never formed, so the center delivers parts that are assembled into outcomes somewhere else.

Those three are where the strain appears. The fourth surface, Standing, is usually where it starts. Most centers are born as a cost decision, and how a center is funded, measured, and positioned is set in that moment. The work changes with the years. The counting often stays where it began, and the counting quietly shapes everything else: a cost line is handed pieces, given approvals, and grown with headcount.

The fifth surface, Continuity, explains why all of this stays hidden for so long. Every young center is carried by a few remarkable people, and what begins as strength quietly becomes exposure. Delivery holds because certain people absorb the strain. Everything works. The working is the concealment.

If the diagnosis is this legible in hindsight, it is fair to ask why capable leadership teams miss it in the moment. I do not think the answer is blindness. I think the answer is that every surface of the problem has an owner, and the problem itself has none.

The site leader owns delivery, and delivery is fine. HR owns attrition, and attrition has a plan. Finance owns the budget, and the budget was approved. The global function heads own their functions, and each function, viewed alone, is performing. The one thing no role description in the entire enterprise contains is a sentence like: revisit the founding architecture of the center when the center outgrows it. The five decisions from the founding room were made by people who have since been promoted, retired, or reorganized away. Their decisions remained behind, ownerless, doing exactly what they were designed to do, for a center that no longer exists.

There is a quieter reason too, and it took me years inside to admit it. Questioning the build feels, from inside, like ingratitude. The build is the thing that worked. It carried the center from a floor of empty desks to a delivery record the enterprise depends on. The people who benefited most from it, the founding leaders, the first hires, the sponsors who bet on it, are the same people who would have to declare it outgrown. Institutions are rarely dismantled by the people they made.

You could argue that this has always been true of growing organizations, and you would be right. What makes it urgent for capability centers, specifically, right now, is the speed and the stakes. The Indian GCC ecosystem added nearly half a million people between FY2024 and FY2026, growing from about 1.9 million to 2.36 million. Nasscom and Zinnov project 2,100 to 2,200 centers and up to 2.8 million people by 2030. Centers are reaching in three or four years the scale that used to take a decade, which means they are outgrowing their founding build faster than any generation of centers before them.

The stakes have moved just as fast. The same FY2026 landscape report carries a title that would have sounded absurd fifteen years ago: from delivery engine to enterprise nerve centre. Its findings describe enterprise authority migrating to India-based leaders and centers taking ownership of products, platforms, and AI-led transformation. The industry, in other words, has renamed itself. The question this series asks is whether each individual center's build has kept up with its own new name.

Reading the problem whole also changes what a leadership team can do with it. In every center I have read closely, when two or three surfaces strain together, they share a single root, and the root is findable. A center strained in structure and standing at once is usually a center that cannot fund its own redesign. A center strained in authority and continuity at once is usually a center where trusted relationships are doing the work that formal authority should. Treat the surfaces separately and you buy five partial fixes. Find the root and the conversation becomes one conversation, which is the only kind a busy enterprise ever finishes.

One more thing deserves saying plainly, because it changes how everything that follows should be read. Nothing in these five surfaces is a failure. A center that never grew would never feel any of this. The strain is the evidence of the success. The founding decisions were right; that is precisely why the center outlived them. The question a serious leadership team asks is never whether the center was built well. It was. The question is whether the way it was built still fits where it is going.

There is a way to read that question with some rigor: the same fifteen statements, across the five surfaces, put in front of ten to fifteen of a center's leaders and read as one pattern. That instrument exists, and it sits behind this series. But the essays come first, because before a center can be read, its leaders have to recognize the story. The next five essays are that story, one surface at a time, beginning with the shape.

Nasscom & Zinnov, GCC Value Orbit: From Delivery Engine to Enterprise Nerve Centre, India GCC Landscape Report FY2026, July 2026. zinnov.com

Nasscom & Zinnov, India GCC Landscape Report: The 5-Year Journey, 2025. nasscom.in