"GCCs: one company, two continents, one team"

A global capability centre is an unusual kind of team. It is a multinational's own people, in India, doing the company's real work, while reporting to a parent on another continent. It is not a vendor and not a branch office. It is the same company, running in two places at once.

That is the whole promise of the model, and it is also its hardest problem. Everything good about a GCC and everything that holds one back comes down to the same question: is it actually one team, or two teams that share a logo. The answer is not decided by the org chart, which can declare them one company on day one. It is decided by the health of the relationship across the distance — the trust, the belonging, the alignment that either bind the two halves into one team or leave them politely separate. And that relationship, unlike the org chart, does not form on its own.

The seam is where the trouble lives

Most of the friction in a GCC is not inside the centre. The people in the centre usually work well together; the internal team health is often strong, because they share a floor, a language of daily work, and all the accidental connection that co-location provides. The strain sits at the seam between the centre and the parent, and it is made of ordinary things that compound into something structural.

This is the crucial diagnostic point, and it is the one most often missed. A GCC leader worried about team health tends to look inside the centre, where things are usually fine, and misses the actual problem, which lives at the boundary with the parent. Reading the centre on its own will show a healthy team and tell you nothing about the gap that is actually holding the GCC back. The seam is invisible from inside either office; it only appears when you read the relationship between them, which is exactly what almost no one does. This is why we insist, for a GCC above all, that the reading has to be aimed at the right place — and for a GCC the right place is the seam, not the centre.

The ordinary physics that pulls the two halves apart

Time zones mean the two halves of a team are rarely awake together, so decisions wait, context is lost, and the centre often learns what changed after it changed. A team that overlaps for only an hour or two a day cannot build the easy, continuous connection a co-located team takes for granted; every exchange is scheduled, compressed, and slightly formal, and the informal glue never gets a chance to set. The asynchrony is not just an inconvenience; it structurally starves the relationship of the casual contact that trust is built from.

Distance means the parent forms its picture of the centre through status reports rather than through people, which is a thin and easily skewed way to know a team. You cannot build trust in a spreadsheet of throughput; you build it in people, and the parent rarely sees the centre as people. And culture means the same words carry different weight in each place, so silence gets read as agreement, and caution gets read as a lack of ideas. A centre that is being respectful in its own cultural frame can read as passive to a parent in a different one, and a parent being direct can read as harsh to a centre — and neither side knows the misreading is happening. None of this is anyone's fault. It is the natural physics of running one team across ten thousand kilometres. But left alone, the physics wins, and the centre slowly becomes a place work is sent to rather than a place decisions are made.

Reporting lines are not relationships

An org chart can connect the centre to the parent with a clean set of reporting lines, and those lines create the illusion that the connection exists. It does not. A reporting line is a channel for tasks and accountability; it is not a relationship, and it does not carry trust. Two people can have a reporting relationship for years and not trust each other, because trust is built from shared experience and exposure, not from an arrow on a chart. The GCC that mistakes its reporting lines for its relationships will keep wondering why the connection feels thin despite everyone being formally linked.

This is the trap of assuming structure produces connection. Combining two groups on a chart, or connecting them with reporting lines, announces a relationship without producing one — the same error mergers make, which we examine in post-merger: two cultures, one team. The centre and the parent can be perfectly connected on paper and function as two separate teams in practice, and the gap between the formal connection and the real one is exactly where a GCC underdelivers. The relationship has to be built in people, deliberately, on top of the structure — the structure alone never fills it in.

Why a GCC is not an outsourcing arrangement

It is worth being clear about what a GCC is not, because the confusion sits underneath a lot of seam problems. A GCC is not outsourcing. In an outsourcing relationship, the arrangement is transactional by design — a vendor delivers a defined scope for a price, and neither side needs to belong to the other. A GCC is the opposite premise: it is the company's own people, meant to be as much a part of the company as any team at headquarters. The whole point of the model is that the centre is not a vendor but a limb of the same body.

The trouble is that a GCC left to the physics of distance drifts toward behaving like the outsourcing arrangement it was meant to transcend — the parent handing over defined scopes, the centre executing at arm's length, neither side building the belonging the model promised. When a GCC underperforms its promise, this drift is usually why: it was set up to be one company and allowed to operate like a vendor relationship, because operating like a vendor is what distance produces by default. The connection work across the seam is what keeps a GCC on the right side of that line — an integrated part of the company rather than an internal vendor. Without it, the model quietly collapses back into the thing it was supposed to improve on, and the centre becomes, in practice, an in-house supplier that happens to share a logo.

What is actually at stake

This matters more than a morale conversation, because it decides how the parent sees the centre. A GCC that feels connected to the parent, trusted by it, and aligned with where it is going gets handed more consequential work. A GCC that feels like a distant execution arm gets handed tasks and kept at arm's length. The difference between those two futures is rarely skill. The centres are full of capable people. The difference is the health of the relationship across the seam.

That is why the soft things are the strategic things here. Trust between the centre and the parent, a real sense of belonging to one company, and genuine alignment on direction are not nice-to-haves. They are what move a centre up the value chain, and their absence is what keeps one stuck doing execution work forever, regardless of how capable its people are. A GCC's ceiling is set less by the talent in the centre than by how much the parent trusts it, and that trust is a team-health property that can be built — or left to the physics, which will keep the two halves apart.

Connection has to run both ways

One reason seam-building fails is that it gets treated as the centre's job — the centre works to feel more connected to the parent, while the parent does nothing to connect to the centre. That does not work, because a relationship built from one side is not a relationship. If the centre reaches across the seam and the parent does not reach back — does not invest the time, does not treat the centre as people, does not include it in the decisions that matter — the effort curdles into resentment, because the centre feels the asymmetry: it is doing the work of belonging to a parent that treats it as headcount.

Real connection across the seam requires the parent to invest as much as the centre, which is often the harder sell, because the parent holds the power and feels less of the pain of the distance. The centre feels the seam every day; the parent can ignore it, because from headquarters the centre is a line in a report that is being delivered. So the parent has to be brought to see the centre as people and to spend real relationship effort on the seam, not because it is generous but because the value of the whole model depends on it. A GCC leader working only on their own side of the seam will exhaust themselves against a parent that never meets them halfway. The work has to engage both leaderships, both halves, reaching across from both directions — which is exactly why it has to be designed rather than left to the goodwill of whichever side happens to feel the distance most.

The belonging gap that costs people

There is a specific and expensive version of the seam problem: belonging. A person in the centre can belong strongly to their immediate team and their floor while belonging weakly to the company as a whole — the company being a distant headquarters they have never visited, run by people they have never met, that appears mainly as demands arriving on a screen. That split is common and quietly costly, because belonging to the company is one of the things that holds good people, and it is exactly the thing that thins out with distance.

This connects to a hard number. The teams furthest from headquarters often carry the highest quiet flight risk, because their organisational belonging is the thinnest — they are held by their local team and by pay, but not by any felt connection to the larger company, which makes a competing offer easier to accept. This is the retention math playing out along the seam: the centre's best people are the most mobile, and thin belonging to the parent is precisely the condition that lets them go. A GCC that builds real belonging across the seam is not doing an inclusion nicety; it is protecting its most valuable and most mobile people from the isolation that makes them leave.

Where connection has to be built on purpose

Connection across a seam like this does not happen by accident, because the accidents that build it elsewhere — the corridor conversation, the shared lunch, the after-work drink — cannot cross a continent and a time zone. So it has to be designed. This is the single most important thing to understand about GCC team health: the mechanisms that build connection for free in a co-located company are simply unavailable, and if you do not deliberately replace them, the connection does not exist. There is no natural fallback. Left alone, distance produces distance.

That means moments where the two halves of the team are genuinely together, not just on a call, and where the point is to build the relationship rather than to run the status update. It means the parent seeing the centre as people with judgment, not headcount with throughput — which usually requires actual contact between the humans, not more reporting. And it means both halves working from the same understanding of where the company is going, so the centre is deciding with the parent rather than waiting on it. We think about a GCC across the same eight dimensions as any team — trust, communication, alignment, collaboration, decision-making, energy, belonging, and leadership — but the readings that matter most are the ones taken across the seam, not within one office. A centre can look healthy on its own and still be only loosely joined to the company it belongs to. That gap is the one worth closing.

The leadership seam decides the rest

As with any organisation, the connection at the top sets the pattern for everyone below, and in a GCC the leadership seam is where the whole relationship is won or lost. If the centre's leadership and the parent's leadership are genuinely one team — trusting each other, aligned, deciding together — that models and enables connection throughout both halves. If the leadership seam is itself two teams, wary and misaligned across the distance, then no amount of connection-building lower down will hold, because the division at the top cascades exactly as it does within a single company, described in the leadership team sets the weather.

This is why GCC connection work has to reach the leadership seam specifically, not just the working teams. A centre head who has a real, trusting relationship with the parent's leadership can bring consequential work and genuine belonging back to the centre; one who is kept at arm's length by the parent's top team cannot, however capable the centre. The relationship between the leaderships is the load-bearing one, and it is the one most worth building deliberately, because everything else about the seam follows from it.

Reading across the seam

Because the problem lives at the seam, so must the measurement. Reading the centre's internal health tells you little about the GCC's actual problem; what matters is reading the health of the relationship across the seam — trust, belonging, and alignment between the centre and the parent — and reading it again over time to see whether it is strengthening. That is a different and more revealing measurement than an internal engagement survey, because it reads the boundary where the value is actually won or lost. A GCC that measures only its internal morale is measuring the half that is usually fine and ignoring the half that decides its future.

And because the seam can be read, it can be improved on purpose and the improvement confirmed, the same way measurement changes the conversation for any team. This lets a GCC leader show the parent something concrete — that the connection is real and strengthening — which is itself part of how the centre earns more consequential work. The reading is not only a diagnostic; it is evidence the centre can use to change how the parent sees it, which is the whole game.

The bridge is the business

There is a reason this is the first industry we write about. A GCC is, from the inside, exactly what we are built around: one company that has to work as one team across two homes. We know that seam because we live on it. The team experiences that make a GCC feel like one company, and the measurement that shows the connection is actually strengthening, are the difference between a centre that is tolerated and one that is trusted.

We do not treat the GCC as an abstract case study, because it is the shape of our own work — India and beyond, held together as one team across distance. That is not a marketing line; it is the reason we understand the specific ache of the seam, the way distance quietly starves a relationship, the difference between reporting to someone and being trusted by them. A GCC that wants to become a capability rather than a cost is working on exactly the problem we work on, in exactly the geography we work in.

A worked example

A GCC head, worried that the centre feels undervalued, commissions an internal engagement programme — events, recognition, culture-building inside the centre. The internal readings improve; people on the floor feel more appreciated. And nothing changes in how the parent treats the centre, because the actual problem was never inside the centre. It was at the seam: the parent still saw the centre as throughput, still made decisions without it, still handed it execution rather than ownership. All the internal engagement work aimed at the half that was already healthy and left the half that mattered untouched.

Reading the seam first would have found this — strong internal health, thin cross-seam trust and belonging — and aimed the work where it counted: at building a real relationship between the centre and the parent, especially at the leadership level, so the parent came to see the centre as people with judgment worth trusting. Same effort, redirected from the centre's internal morale to the seam that decides the centre's future. The measurable result is not a happier floor; it is the parent handing the centre more consequential work, because the connection across the seam finally became real. That redirection, from the centre to the seam, is the single most valuable move a GCC leader can make, and almost no one makes it, because the centre is where they naturally look.

The bridge is the business, again

The centres that win the next decade of work will be the ones whose leaders treated the relationship with the parent as something to build, not something to assume. It is the highest-leverage team investment a GCC can make, and almost no one is making it deliberately — because the seam is invisible from inside either office, and the physics of distance quietly does its work while everyone attends to the half of the team that was already fine.

Read the seam, build the connection across it on purpose, reach the leadership relationship specifically, and confirm it is strengthening. That is how a GCC stops being one company pretending to be one team and becomes one — and how a centre full of capable people finally gets treated as the capability it already is. The org chart made them one company in a day. Only the deliberate work across the seam makes them one team, and that work is the whole difference between a centre that is tolerated and one that is trusted with the future.