Engineering Leadership · Chapter 5 of 8
Running a distributed and GCC organisation
Where most Indian engineering leadership actually happens, and the specific things that make it work or not.
A large share of leadership roles in this atlas are in India, running teams whose stakeholders are elsewhere. The difficulties are structural rather than cultural, and most are addressable by design.
Treat the overlap window as the scarce resource it is
You get a few hours a day of overlap with headquarters. What goes into it determines what your teams are unblocked on for the next twenty-four hours. So: decisions and unblocking in the overlap, status in writing outside it. A synchronous meeting spent on updates that could have been read is the most expensive thing that happens in a distributed organisation.
The perception problem, and its actual cause
Centres are frequently described as execution arms, and leaders respond by trying to build trust. That rarely works, because the cause is usually structural rather than attitudinal. The questions that diagnose it:
- Does anyone here own a product outcome end to end, or do we own components of outcomes owned elsewhere? If the second, no amount of relationship-building changes the perception, because the org chart says what it says.
- Is someone from here in the room when the roadmap is set — at the point of decision, not at the readout? Being consulted is not deciding.
- Where do our strongest people go when they leave? If they leave at the same level for product companies, we are not offering scope, and that is measurable.
- Who presents our work upward? If it is always someone from headquarters, the centre is invisible regardless of what it delivers.
The move that actually changes it
Get one whole charter transferred — a product surface small enough that headquarters can afford to let go, with the decision rights attached, not just the headcount. One genuine transfer of ownership does more in a year than five years of relationship-building, because it changes what people here can put on a CV.
And negotiate it before accepting the role. Scope promised to follow rarely arrives, and it is the single most common reason these roles disappoint.
The unglamorous half
Leaders arriving from pure engineering backgrounds are consistently underprepared for the statutory side: entity governance, labour law, data residency, and in regulated industries a local board or regulator. It is real work, it is not delegable in the way people assume, and having a credible answer about it separates candidates at site level.