Blog · 6 min read

Personal Operating System for a GCC Site Leader

By Anupam Tandon · August 2025

TL;DR

Site leaders need a personal OS: priorities, HQ rhythm, people time, and hard stops. Otherwise the calendar runs the mandate.

A personal operating system for GCC site leaders

The site lead role fills with inbound requests until there is nothing left for mandate work. Build a personal OS on purpose.

Core blocks

Mandate time: deep work on charter, quality, and key hires
HQ rhythm: predictable communication, not endless Slack firefighting
People time: managers and critical ICs, not only escalations
External hygiene: partners, compliance, facilities in bounded slots
Hard stops: recovery and thinking time protected like a customer meeting

Weekly ritual

Sunday or Monday: three outcomes for the week tied to the charter. Friday: what moved, what slipped, what to tell HQ.

30 / 60 / 90

30: Write your OS on one page.
60: Share cadence expectations with HQ and your leads.
90: Review calendar reality vs intent; cut ruthlessly.

Takeaway

If you do not design your week, everyone else will.

Leaders who protect focus protect the center.

“Structure matters, but the first three or four hires decide whether your India team becomes a capability or an expensive supplier.”
— Anupam Tandon, ContextDelta

Want this applied to your roles? Book a discovery call.