The Scale of the Operation
At its peak, 190 technical support staff operated across centres in North America, EMEA, and APAC, providing 24/7 coverage to a global enterprise customer base for security and building technology products. Running an operation at this scale requires a different kind of leadership than running a team of twenty. You can’t supervise directly. The tools of scale are frameworks, reporting systems, and the leadership development of the people who run the centres on your behalf.
"At 190 people across three continents, management by walking around is not a strategy. Management by data, governance, and developing leaders who can lead without you — that’s the actual job."
The Four Pillars of the Operating Model
Governance & ITIL
Implemented ITIL-aligned process standards across all regional centres — incident management, problem management, change control. A common operating language and consistent escalation structure regardless of location.
Reporting Infrastructure
Built a cross-regional reporting layer covering ticket volume, first-contact resolution, SLA compliance, and backlog trends across all centres. Without this, every regional conversation was anecdotal.
Leadership Development
Hired and developed regional managers in each centre — people who could lead their teams with appropriate autonomy while operating within the global framework. The model only works if the leaders running each centre believe in it.
Cross-Regional Coordination
Weekly cross-regional calls, shared escalation protocols, and a common case management platform giving every agent visibility into active cases regardless of which centre opened them.
Budget Management at $12M
Managing a $12M operational budget across four centres in three currencies requires more than a spreadsheet. The discipline that proved most valuable: connecting every budget decision to performance data. When a centre requested additional headcount, the question was always “what does the data show about current utilisation, and what is the projected volume increase that justifies the addition?”
What ITIL Implementation Actually Looks Like
ITIL is a framework, not a product. Implementing it across a global operation means translating abstract process categories into specific procedures agents in Shanghai, Echt, London, and North America follow consistently. The work is primarily documentation, training, and enforcement.
What changed: Incident classification became consistent across centres. Escalation thresholds were explicit rather than manager-dependent. Problem management became a standard operational practice. Change management for platform updates had a defined review and approval process that prevented uncoordinated changes from creating new incidents.
Operational Benchmarks
What We Learned
Distributed operations run on shared frameworks, not supervision. Without the framework, you have four separate teams that happen to share a budget line.
Data is the only substitute for proximity. Cross-regional metrics — aggregated and trended — gave leadership the visibility to make good decisions without being physically present.
ITIL without reporting is a process document nobody reads. The framework only drove behaviour change because the reporting infrastructure made compliance visible. Published compliance metrics create accountability in a way that abstract process standards don’t.