The missing middle: why first-time managers in GCCs struggle, and what fixes it

In most growing GCCs, there is a moment when a brilliant engineer becomes a manager. Often it happens fast. A team grows, a lead moves on, a new mandate arrives, and the best individual contributor is asked to step up. On Monday they write code. By Friday they are running one-to-ones, chasing hiring and fielding calls from HQ.

Some thrive. Many struggle quietly. And because the middle layer of a centre is where decisions are made and people are developed, the effect of that struggle spreads across the whole organisation.

Why the middle goes missing

Rapid growth is the main cause. When a centre doubles in size, it needs far more managers than it has developed. The fastest route is to promote the strongest engineers, analysts and testers, because they understand the work and have the respect of their peers.

The problem is that the skills that made them excellent individual contributors are not the skills that make a good manager. Deep expertise, attention to detail and personal ownership of output can become liabilities if they lead a manager to keep doing everything themselves.

The captive-centre context adds pressure. GCC managers sit between a local team and global stakeholders, often across several time zones. They are expected to represent India’s view to HQ, translate HQ priorities for their team and make decisions that used to be made elsewhere.

---

The four common struggles

Watch new GCC managers in their first year and the same patterns appear.

They keep doing the work. It feels productive and it is what they know. But every hour spent on hands-on work is an hour not spent developing the team, and the team learns to wait for the manager to step in.

They avoid difficult conversations. Giving critical feedback to a former peer is uncomfortable. Many new managers delay it, and small performance issues grow.

They escalate decisions. Unsure of their authority, new managers pass decisions up the chain or across to HQ. Each escalation reinforces the view that the centre is not ready to own.

They struggle with distributed teams. Leading people you rarely see, with stakeholders in other time zones, needs deliberate rhythms and communication. Few people learn this naturally.

Strong individual contributor

Confident manager

• Solves the problem personallyHelps the team solve it
• Measures success by own outputMeasures success by team results
• Avoids conflict to keep peaceHas the hard conversation early
• Asks HQ when unsureDecides within agreed limits, briefs HQ
• Communicates when neededRuns a regular rhythm of one-to-ones

---

What actually builds confident managers

Most organisations respond to the missing middle with a classroom course: a day or two on leadership models, followed by a return to work. Feedback scores are good. Behaviour rarely changes.

What works is closer to how people learn any difficult skill: practice, feedback and time.

Spread it over months, not days

Behaviour change needs repetition. A programme that runs over three or four months, with short sessions and practice in between, gives managers time to try new approaches, fail safely and adjust.

Practise on real situations

The most useful sessions use the situations managers actually face: the underperforming team member, the HQ stakeholder who changes priorities weekly, the request to deliver more with the same people. Role plays built from real cases transfer far better than generic examples.

Add coaching

One-to-one coaching from an experienced leader helps managers work through their own specific challenges. It also gives them a safe place to admit what they find hard, which they rarely do with their own manager.

Give them a real project

An on-the-job project, sponsored by a senior leader, turns learning into results. A manager who leads a visible improvement in their area builds confidence and earns credibility with both their team and HQ.

A four-month manager journey

1. Month 1

   Foundations

   • From doing to leading
   • One-to-ones and feedback
   • Baseline team feedback

2. Months 2–3

   Practice and coaching

   • Delegation and decisions
   • Leading distributed teams
   • One-to-one coaching

3. Month 4

   Applied project

   • Lead a real improvement
   • Present to sponsors
   • Repeat team feedback

---

Measuring whether it worked

If the goal is better managers, measure management, not training. Three measures are practical for most centres:

1. Team feedback. A short 180-degree survey at the start and end of the programme shows whether team members see a difference.
2. Escalations. Track how often decisions that the manager owns are escalated to HQ. A falling number is one of the clearest signals of growing confidence.
3. Retention. Over a longer period, compare attrition in teams led by programme participants with the wider centre.

Strengthening the middle layer is not quick. But it is one of the highest-return investments a GCC can make, because every other priority, from AI adoption to winning the next mandate, runs through those managers.

---

Choosing who to promote, and preparing them first

Much of the missing middle problem starts with how managers are chosen. Promotion to management is often treated as a reward for technical excellence, which means the people promoted are not always the people who want to lead, or who would be best at it.

A few changes make a large difference.

Separate the career paths. Centres that offer a credible technical career path, with senior and principal roles that carry real status and pay, take pressure off the management track. Strong engineers who would rather stay hands-on no longer have to become managers to progress.

Look for leadership signals early. The best future managers often show it before they have the title. They help colleagues, handle disagreements well, communicate clearly with stakeholders and care about the team’s results rather than only their own. Ask current managers to nominate people who show these signals.

Prepare before the promotion. A short pre-management programme for high-potential individual contributors, covering basics such as one-to-ones, feedback and delegation, lets people try the role before taking it on. It also helps some decide that management is not for them, which is a good outcome too.

Support the first 90 days. The first three months in a management role set habits that last for years. A clear transition plan, a mentor who is an experienced manager and early feedback from the team help new managers start well.

None of these steps is expensive. Together, they reduce the number of managers who struggle, and make development programmes far more effective for those who need them.