ChatGCC: Why GCCs Struggle and How to Avoid Failure
- 23 minutes ago
- 24 min read
Episode 2
Hosted by Patricia Connolly and Aditya Jayaraman
Key Takeaways
GCCs rarely fail because of bad strategy — on paper they're usually well designed. They fail gradually, drifting from their original purpose until they become "an ODC in disguise."
A Global Capability Center or "GCC" and an Offshore Delivery Center or "ODC" are fundamentally different: a GCC is employee-centric and built for business value, while an ODC is contractor-based and built for task execution. Confusing the two is where disappointment begins.
Drift usually traces to three patterns: unclear definitions of success, weak leadership empowerment, and scaling without the right foundation.
Culture, talent fit, and governance are the most underestimated determinants of success — and all three must be built in from day one.
The hardest part of a Build-Operate-Transfer model is the transfer. Plan it from the start, or risk a transition that never fully happens.
Why Good GCCs Quietly Go Wrong
Global Capability Centers are booming — and many of them are quietly failing to deliver what was promised. The striking part, as Jayaraman observes, is that they don't fail for lack of strategy: "On paper, they're usually quite well designed. There's a clear mandate, a strong business case, leadership backing." The board signs off, the center launches, and then a few years in it feels underwhelming — never scaling the way it was meant to, or drifting away from its original purpose.
What was supposed to become a strategic capability turns into something else: a high-cost delivery engine, or a center perpetually trying to reinvent itself. As Connolly puts it, the failure doesn't happen where you'd expect.
"GCCs rarely fail at the boardroom level. They fail in the way reality sets in after lunch." — Patricia Connolly
This episode isn't about fixing the problem yet — it's about naming the real reasons GCCs drift, the ones that set in early but aren't recognized until much later. If you've ever sensed your GCC isn't quite becoming what it was meant to be, the most useful first step is recognizing when it has started to slide into an offshore delivery center in disguise.
GCC vs. ODC: Knowing the Difference
A lot of the confusion starts with the model itself. A GCC, in Connolly's definition, "has a defined strategic purpose — to create business value and innovation through an employee-centric workforce that operates as one team with headquarters." An ODC is a different animal entirely: typically contractor-based, disconnected from the broader vision by design, and focused on executing defined tasks, usually driven primarily by cost.
Those are two very different objectives, and when they get mixed up, the disappointment starts — you expect business outcomes but you're getting output. That's how many GCCs begin to fail, Connolly notes, "maybe not dramatically, but subtly. They still operate, they still deliver to a degree, but they never really become what they were meant to be."
Where the Drift Begins
The breakdown is rarely one big failure. It's gradual, and a few patterns show up consistently.
The first is a lack of clarity. Companies don't always define what success actually looks like — cost savings, capability building, innovation, or business growth. "When that's not clear from day one," Connolly says, "the GCC starts drifting, even if the teams seem busy." She points to a company that set up what looked like a GCC but whose real intent was a contractor move into a lower-cost center; by year one it was wrestling with slow hiring, poor retention, and leaders with no clear sense of purpose — confusion that showed up everywhere, in morale, delivery, and outcomes.
The second is leadership empowerment. If the GCC isn't truly empowered and most decisions still sit with HQ, local ownership never forms — and, as Jayaraman notes, the HQ leader ends up carrying the entire load on top of their existing job. Without clear ownership and an articulated mission, people improvise. That slows decisions, creates bottlenecks, and can drive strong leaders away.
The third is scaling without a foundation. Companies try to ramp quickly without the right leadership, structure, clarity, or empowerment in place. That's when you hear, in Aditya's words, "we thought we'd be at 100 people by now, but we're only at 20," or "we've just started hiring and we're already losing people." The issue isn't speed itself — it's scaling before the underlying support systems can keep up.
Culture: The Most Underestimated Factor
Culture is where many GCCs are won or lost, and it's the factor leaders most often skip. A GCC isn't just a delivery engine, Aditya argues — "it is a cultural extension of the parent organization, the mothership." The trouble is that culture doesn't wait to be designed.
"If culture isn't intentionally built, it builds itself." — Patricia Connolly
When that happens, employees fill the gap themselves, and you end up with a fragmented GCC: poor communication, different ways of working, mismatched expectations. The most successful centers invest in culture early — defining how decisions are made, how teams collaborate, how accountability works, and what everyone is working toward — while aligning the parent's principles with the local environment's strengths.
This is where SMC Squared's approach is deliberate from day one. During startup, its talent, marketing, and HR teams meet with client leaders to absorb the company's culture, history, and values, then build a value proposition that positions the company correctly in the talent market. Everything from there is infused with brand and culture, so a new hire identifies with the parent's purpose from their first day. The payoff, Connolly says, is that employees work "as a valued part of the team — not in a contractor model or distant from headquarters. That's culture when it's running best."
Hiring for Fit, Not Just Skills
Talent acquisition is where GCCs are fundamentally different from traditional outsourcing. "You're not pulling from a bench," as Jayaraman frames it. "You're building something from the ground up." Connolly emphasizes that SMC Squared has never kept a bench by design: "We never wanted to fit a candidate halfway. Everything matters when you're hiring, especially early on, when you're defining the DNA of the organization."
The focus is on fit — not just technical capability, but alignment with how the organization operates, plus the right industry and geography, language competency, growth potential, and long-term retention. The cautionary version is a center that hires purely for skills. If a parent company sets up a GCC to advance its data journey but the operator simply chases Databricks, Snowflake, and Redshift résumés, the center drifts from the original objective over time. The goal is people who don't just work for the company but think like it — especially since employees may eventually transition to work for the parent directly.
Governance From Day One
Governance is where GCCs either stabilize or struggle. It isn't just oversight, Connolly notes — "it has to be embedded into how the GCC operates day-to-day, and it starts right from the beginning." The most effective models don't bolt governance on as an afterthought; they weave it into a structured playbook adopted from day one, spanning hiring, delivery, outcomes, and performance management.
The absence of it is telling. When Connolly talks with leaders whose GCCs are underperforming, governance often "isn't even on the table" — the focus is on filling seats, with no clear answer to where the center is going, how progress is measured, how it's communicated, or how change is managed. Things turn reactive, and consistency and quality break down. Strong governance, by contrast, inherently mitigates risk — which is exactly why C-level leaders and boards respond to it when it's raised early.
Vendor Dependency and the Transition Trap
One of the core reasons companies build GCCs is to regain control — over talent, IP, delivery, and outcomes — and reduce their reliance on external vendors. But that only works if the GCC is truly integrated and capable. Otherwise you get a hybrid in which the GCC exists but the vendor dependency never actually goes away, and the original mission gets diluted.
The most overlooked piece is the transition itself. Many GCCs are built on a Build-Operate-Transfer (BOT) model, expecting eventual transfer to the company's own entity — but that end goal has to be mapped from the very beginning. Patricia is candid about how often it goes wrong: some vendors want clients to stay dependent and quietly create roadblocks; in other cases the transfer happens too early, before the GCC is stable. "We hear horror stories about GCCs that go through an ownership transition," she says, "and only 50% of the team actually moves to the parent company." Avoiding that fate takes structure — clear milestones, capability assessment at every stage, and leadership in place to move with the GCC when ownership shifts.
The Bottom Line
Step back, and the pattern is clear. GCCs don't struggle because the model is broken.
"They struggle because the keys to execution are maybe not understood, making it very hard to succeed." — Patricia Connolly
The difference between average and high-performing GCCs comes down to a handful of things done well: strategic clarity, culture, talent, governance, disciplined execution, and a planned transition. Get them right and the model works remarkably well. Get them wrong and you end up with something that looks like a GCC but doesn't deliver like one.
Listen to ChatGCC Episode 2 — for the full conversation, including real examples of GCCs that drifted and what it took to get them back on track.
New here? Start with Episode 1: Introducing ChatGCC.
Frequently Asked Questions
Why do Global Capability Centers fail? GCCs rarely fail because of bad strategy. They drift gradually due to unclear definitions of success, weak leadership empowerment, scaling without the right foundation, neglected culture, hiring for skills over fit, lack of governance, and poorly planned transitions — until they function more like an offshore delivery center than a strategic capability.
What is the difference between a GCC and an ODC?
A GCC has a defined strategic purpose — creating business value and innovation through an employee-centric workforce that operates as one team with headquarters. An ODC (offshore delivery center) is typically contractor-based, disconnected from the broader vision by design, and focused on executing defined tasks, usually driven by cost.
How important is culture to a GCC's success?
Culture is one of the most underestimated factors. A GCC is a cultural extension of the parent organization, and if culture isn't intentionally built from day one, it builds itself — leading to fragmentation, poor communication, and mismatched expectations.
What is the Build-Operate-Transfer (BOT) model, and where does it go wrong?
In a BOT model, a partner builds and operates the GCC before transferring it to the company's own entity. It fails when the transition isn't planned from the start — some vendors create roadblocks to keep clients dependent, and transfers attempted too early can leave only part of the team moving to the parent company.
ChatGCC is hosted by Patricia Connolly and Aditya Jayaraman, and backed by SMC Squared and Hexaware.




