Key takeaways
- Before a new GCC head makes any big call, the useful work is mapping the decision rights, what the centre owns versus what the parent still controls: budget, hiring authority, roadmap, vendor calls.
- The published 90-day playbook is about strategy and stakeholders. The version that decides the first year is about authority and the bench, who you can actually hire, and who you inherited.
- The strongest starts spend early capital settling hiring authority and securing two or three defensible wins that build the case for a larger charter later.
The published playbook and the actual playbook diverge fast.
We spoke to GCC heads who had been in role under a year, 17 of them, and asked what actually filled their first 90 days. The written version is familiar: learn the business, meet the stakeholders, set a strategy. Almost no one described their real first quarter that way.
What they described was quieter and harder. They spent the early weeks working out where their authority genuinely ended, which of their inherited leaders were load-bearing, and which senior seats would decide the next 2 years. The strategy work was real, but it sat on top of those answers. Get them wrong and the strategy never lands.
The setting makes the margin for error thin. India’s GCC count has crossed 1,700 centres, per Nasscom, and the parent organisations behind them are watching capability metrics more closely than headcount now. A new head arrives into a mandate that’s already half-written by the parent, and the first job is to read what it actually says, the operating version.
Map the mandate before you spend any of it.
Every GCC head runs a centre that shares control with the parent, and the split is rarely written down cleanly. The mandate you were given in the interview describes intent. The mandate you actually hold shows up in who signs off on what. So the first exercise is dull and decisive: list the calls that matter and mark, for each, whether you own it, share it, or only advise on it.
Four lines carry most of the weight. Budget: can you move money between line items, or does every reallocation route back to the parent function. Hiring authority: can you approve a leadership hire and its number, or do you get a headcount and a band you can’t flex. Roadmap: do you shape what the centre builds, or receive a backlog set elsewhere. And vendor calls: can you choose a partner and sign, or route procurement through a global desk. Where you land on those four defines the real size of the seat, and it’s almost never what the title implies.
The mapping tells you which early moves are safe to make alone and which will trigger a call from the parent you didn’t expect. Heads who skip it tend to discover the boundaries the expensive way, mid-decision, with a hire or a budget line already in motion.
The first 90 days test whether you have the authority and the bench to execute any plan at all. Map that honestly before you announce anything, or the plan writes cheques the seat can’t cash.
Sachith Rai · Managing Director and Founder, Recruise
| Decision area | What the centre often owns | What the parent tends to hold |
|---|---|---|
| Budget | Operating spend within an agreed envelope; some discretion on tooling | The size of the envelope, reallocation between major line items, capex sign-off |
| Hiring authority | Filling approved roles; shaping job design and the interview bar | Total headcount, the salary bands, and often sign-off on leadership hires |
| Roadmap | Sequencing and delivery of committed work; local prioritisation | What gets built at all, the backlog set by the global product or function owner |
| Vendor and partner calls | Recommending partners; managing the relationship day to day | Procurement approval, master contracts, and the preferred-supplier list |
| Where authority is ambiguous | Leadership hires, mid-cycle reallocation, net-new capability the parent didn’t ask for | These are the seats where the boundary is untested; settle them before a live decision forces it |
Read the real org behind the chart.
The second read is the leadership team you inherited. The org chart tells you the reporting lines. It doesn’t tell you which of those leaders the centre actually runs on, which have the trust of the parent function, and which are holding a seat the next phase will outgrow. Those are the facts that decide how much you can attempt in year one.
The heads who started strongest made an uncomfortable move early: they formed honest views on the inherited bench before they announced anything new. That meant working out who could grow into the next phase and who could not, the call most new leaders defer for a year and then regret, because by then the weak seat has cost a delivery cycle. Early capital spent on the bench compounds. The same capital spent on a launch that the bench can’t deliver evaporates.
Reading the real org also surfaces the informal decision-makers: the person the parent calls when something breaks, the architect everyone defers to, the finance contact who quietly gates spend. None of them appear on the chart with that weight. A head who maps them in the first month negotiates from a much clearer picture than one who meets them for the first time in a crisis.
Find where authority is ambiguous, and settle it early.
The most dangerous line on the decision-rights map is the one where nobody is sure. Ambiguous authority looks fine until a live decision lands on it, at which point it becomes a negotiation you’re running under time pressure, with a hire or a budget already committed.
Hiring authority is where this bites first and hardest. A head who has to fight for sign-off on their first critical leadership hire has already lost time they won’t recover, and has signalled to the parent that the seat is smaller than advertised. The strong starts treated that clarity as a day-one conversation: what leadership roles can I approve, at what number, without routing back. Settling it before the first hard vacancy forces the question is the single biggest predictor of a strong first year we saw.
The same logic covers mid-cycle budget moves and any net-new capability the parent didn’t explicitly ask for. Raise the boundary question while it’s hypothetical and you get a calm answer. Raise it once you’ve already acted and you get a governance conversation. The order matters: agreement first, action second, on every call where the map showed a grey zone.
Secure the early wins that earn a larger charter.
Authority in a GCC is earned, and the currency is delivered proof. The heads who expanded their remit fastest closed two or three visible, defensible wins inside the authority they already had, and let those results make the argument for more.
The wins that travel are the ones the parent already cares about: a critical leadership seat filled faster than the parent expected, a delivery milestone the global team had quietly written off, a cost or capability metric that moved in a direction the board reports on. A Head of Data Engineering placed in 11 weeks against a global search that had run for 5 months does more for a new head’s standing than any strategy deck. It’s concrete, it’s attributable, and it changes how the next budget conversation opens.
Charter expansion follows evidence. A head who has shown the centre can own a hard hire and land it, or take on a capability and deliver it clean, is negotiating from a track record. That’s how the ambiguous rows on the decision-rights map get redrawn in the centre’s favour over the following year, one demonstrated result at a time.
The 90-day sequence, in the order it actually runs.
Put together, the opening quarter has a shape. Map the mandate first, the four decision lines and where you truly sit on each. Read the real org next, who is load-bearing, who is informal, who the next phase will outgrow. Then find the ambiguous authority and settle it while it’s still hypothetical, hiring rights above all. Only then reach for the early wins, chosen because they fall inside the authority you have confirmed and because the parent already values them.
The onboarding pack prescribes a different sequence, and this one is slower to show on a stakeholder update than a launched initiative. But it’s the one the heads who started well actually followed. The strategy still gets written. It just gets written on top of a clear read of what the seat can do, which is the difference between a plan that lands and one that stalls the first time it meets a boundary nobody had mapped.
Frequently Asked Questions
What should a new GCC head do in the first 30 days?
Map the decision rights before making any large call. List the calls that matter, budget reallocation, hiring authority, roadmap, vendor sign-off, and mark for each whether you own it, share it, or only advise on it. The mandate described in the interview is intent; the mandate you actually hold shows up in who signs off on what. Draw that map first, then read the leadership team you inherited to see who the centre genuinely runs on.
Why does hiring authority matter so much in the first quarter?
Because a head who has to fight for sign-off on their first critical leadership hire loses time they won’t recover and signals to the parent that the seat is smaller than advertised. Settling hiring authority, which leadership roles you can approve, at what number, without routing back, before the first hard vacancy forces the question was the single biggest predictor of a strong first year among the heads we spoke to. Treat it as a day-one conversation.
How does a GCC head expand their charter over time?
By delivering visible, defensible wins inside the authority they already hold. Close two or three results the parent already cares about, a critical seat filled faster than expected, a delivery milestone the global team had written off, a metric the board reports on, and let the evidence make the case. Charter expansion follows a track record, so the ambiguous decision rights get redrawn in the centre’s favour one demonstrated result at a time.
What is decision-rights mapping for a GCC leader?
It’s the exercise of writing down, for every consequential call, whether the centre owns it, shares it with the parent, or only advises. Four lines carry most of the weight: budget, hiring authority, roadmap, and vendor and partner calls. The most important cells are the ambiguous ones: leadership hires, mid-cycle reallocation, net-new capability, where nobody is sure who decides. Those are the seats to settle while the question is still hypothetical, because they turn into pressured negotiations once a live decision lands on them.
One hiring pattern worth knowing, every ten days.
The Mandate Desk is our read on the senior GCC talent market — one signal that moved, the read behind it, and one thing worth doing. Written from live placement data.
More from Recruise Insights.
GCC Leadership A Director in the US and a Director in your India GCC aren't the same hire
US parents level India roles off their own org chart. The title travels; the span and the decision rights don’t, and the search inherits the difference.
GCC Leadership Hiring authority is the mandate conversation nobody has upfront
The charter says the GCC head owns the centre, yet senior hires still route through headquarters. That gap shows up as slow, compromised hiring.
GCC Leadership The proximity trap: when a GCC leader can’t let go of the work
As span grows, the best builders lose the distance the role now needs, staying too close to the work they used to do. A leadership-psychology read, distinct from the org-design side of span of control.
Have a senior seat to fill?
Tell us the mandate — the role, the level, the market. We’ll come back with what the market is really doing on it, and how we’d run the search.