Journal · Transformation Operating Model
Your Global Delivery Centre Has Capacity. Does It Have a Mandate?
Before expanding the centre’s remit, define what it owns, which decisions it can make and how the enterprise will measure the value created.
Capacity is not authority
Global delivery centres are often measured by headcount, utilisation, service levels, delivery volume and cost efficiency.
These measures show whether a centre delivers efficiently. They do not show whether the centre has the authority to improve business outcomes.
A centre might have skilled teams, operational data and a strong improvement pipeline, yet depend on other functions to approve funding, change processes or implement solutions.
The enterprise has increased delivery capacity without necessarily increasing its ability to improve performance.
The executive question is not how much more work the centre can absorb. It is what the centre should own, which decisions it should control and which outcomes it should be accountable for delivering or influencing.
This article uses “global delivery centre” broadly to include global capability centres and similar enterprise delivery organisations.
Three forms of contribution
A centre’s role generally falls into one of three categories. These are operating-model choices, not mandatory stages in a maturity journey.
1. Execute
The centre delivers work defined and governed elsewhere. Responsibilities might include application operations, infrastructure, engineering delivery or business processing.
Performance is measured through service quality, cost, productivity and delivery commitments.
This is appropriate when the enterprise wants reliable execution and retains process ownership and decision authority elsewhere.
2. Own a service or process
The centre becomes responsible for the performance and continuous improvement of a defined service or end-to-end process.
This requires authority over operational priorities, workflow changes and improvement initiatives, supported by appropriate funding, information and expertise.
3. Develop an enterprise capability
The centre develops and improves a defined capability against agreed business objectives. Its remit might include specialist expertise, innovation, automation and technology choices within delegated boundaries.
Capability ownership does not mean ownership of every related business decision or outcome. Enterprise leadership retains responsibility for decisions outside the centre’s defined remit, while shared decisions should have explicit owners and escalation routes.
The right model depends on business need, demonstrated capability, risk and the enterprise operating model. Some centres should remain focused on execution. Others should own services or processes. Broader capability ownership should be earned through evidence, not assumed from scale.
McKinsey’s 2025 analysis describes global centres moving from efficient support towards partnership and leadership as they demonstrate their ability to deliver superior solutions. Its framework describes three phases: the “right to play”, the “right to partner” and the “right to lead”. Read McKinsey’s analysis.
EY’s November 2025 Global Capability Centre Pulse Survey reported that 92% of surveyed centres aimed to deliver value beyond cost arbitrage and 87% planned to manage end-to-end global processes. The survey covered leaders from GCCs operating out of India. These figures describe survey respondents, not the entire global delivery sector. Read EY’s survey findings.
The direction is clear: efficiency still matters, but enterprise expectations increasingly extend beyond delivery volume.
The structural problem: responsibility without control
Consider a centre responsible for global application operations.
Its teams identify recurring incidents, inefficient workflows and automation opportunities. They have the expertise and operational evidence to improve performance.
Yet another function controls the budget. Business owners approve process changes. Architecture teams govern technology decisions. Local units control adoption and exceptions.
The centre is accountable for service performance but controls only part of the system that determines the result.
The organisation has created an accountability boundary narrower than the performance boundary.
Three problems follow:
- Accountability exceeds authority. The centre is expected to improve outcomes without the decision rights required to deliver the improvement.
- Improvement depends on external priorities. Funding and approvals sit with stakeholders whose priorities might differ.
- Expertise is disconnected from decisions. Those closest to operational problems lack the authority to resolve them.
More headcount will not fix this. Neither will relabelling the centre as a strategic partner.
The solution is a mandate aligned with the responsibility the enterprise expects the centre to fulfil.
A mandate defines the centre’s purpose, scope, intended outcomes, authority, resources, boundaries and accountability.
Four decisions executives must make
1. Define ownership
Specify whether the centre supplies resources, owns a service, manages an end-to-end process or develops an enterprise capability.
Also distinguish ownership from contribution.
A centre might operate a digital platform and improve reliability while business leaders retain responsibility for adoption, policy and commercial outcomes. Where responsibility is shared, name the owners and define the dependencies.
Leadership has four legitimate choices: retain the current remit, expand ownership, defer expansion until readiness improves, or redesign an arrangement where responsibility and authority are misaligned.
More responsibility is not automatically better.
2. Delegate the decisions and resources required
Every material responsibility needs corresponding decision rights, resources, information and escalation routes.
The mandate should specify which decisions the centre can make across:
- Operational priorities and process changes.
- Approved operating expenditure and improvement funding.
- Workforce planning, skills and capacity allocation.
- Vendor selection and technology choices within defined limits.
- Data access, quality, reporting definitions and permitted use.
- Resource reallocation within approved boundaries.
The enterprise should retain control of decisions involving material investment, regulatory interpretation, legal commitments, enterprise risk appetite and policies affecting multiple business units, where appropriate.
The boundaries must be explicit. The centre needs sufficient authority to act within its remit and a clear route for decisions outside it.
Delegating responsibility while retaining control of the resources required to fulfil it creates an incomplete mandate.
3. Establish readiness
Reliable delivery is necessary, but it does not automatically demonstrate readiness for broader ownership.
Before expanding the remit, assess whether the centre has:
- Strong service or domain expertise.
- Reliable operational data and performance reporting.
- Leadership able to make trade-offs and accept accountability.
- Appropriate security, compliance and risk capabilities.
- Resilience and continuity arrangements for critical services.
- Cross-functional and cross-geography working capabilities.
- Stakeholder management and business adoption expertise.
- Evidence of sustained improvement beyond routine delivery.
Readiness should be demonstrated, not inferred from headcount, tenure or delivery volume.
Where gaps exist, define the required capability, investment and evidence needed before reconsidering the proposed responsibility.
4. Measure outcomes the centre can influence
Service levels, utilisation, delivery volume and cost remain useful. They do not establish whether the centre has improved business performance.
Depending on its remit, measures might include cycle time, incident recurrence, service resilience, customer experience, quality, risk reduction, automation adoption and realised benefits.
Measurement should distinguish planned benefits, actual performance, claimed value and validated outcomes where independent or cross-functional validation is appropriate.
It must also distinguish direct centre performance from benefits requiring action elsewhere.
For example, a centre might deliver an automated workflow, but financial savings depend on business units changing staffing, processes or expenditure. The mandate should identify who owns those actions and who validates the benefit.
The centre should not be held solely accountable for benefits it lacks the authority or practical control to secure.
Align accountability, authority and control
These concepts are related but distinct.
- Accountability: being answerable for an outcome.
- Authority: having the right to make specified decisions.
- Control: having the practical ability to influence the factors determining performance.
A centre might hold formal authority over a process but lack control because another function owns the budget, critical data or business adoption.
Conversely, it might manage daily operations but lack authority over the investment or policy decisions needed to resolve recurring problems.
The operating model must make these boundaries visible.
Where outcomes depend on business adoption, policy changes or local behaviour, name the business owners responsible for those conditions. Shared outcomes need agreed measures, explicit dependencies and clear escalation routes.
The principle is straightforward: assign accountability in proportion to the decisions, resources and dependencies each party controls.
Delegated authority needs boundaries and review
A broader remit does not mean independence from enterprise governance.
Security, data residency, architecture standards, financial controls, regulatory obligations and enterprise risk requirements still apply.
The delegation model should specify which decisions remain enterprise-controlled, which the centre can make independently and which require escalation.
It should also define the conditions for reassessment. Material control failures, repeated performance shortfalls, unresolved audit findings, significant changes in business need or loss of required capability should trigger review.
Name the authority responsible for amending or withdrawing delegated decision rights, along with the evidence required for such a decision.
Delegation should be deliberate, bounded and reviewable, rather than permanent by default.
What a clear mandate looks like
Consider a centre responsible for a global technology service.
Its mandate states:
The centre owns the global service, its operating performance, continuous improvement roadmap and approved service budget. Within defined standards and financial thresholds, it can prioritise work, change workflows, allocate capacity and select appropriate technology.
Enterprise architecture, regulatory policy, material investment and customer-policy decisions remain subject to the relevant enterprise approval. Business leaders retain responsibility for adoption and benefits dependent on business decisions.
The centre is accountable for service outcomes within its remit. Shared business outcomes have named owners, agreed measures and explicit dependencies.
The mandate also specifies available resources, escalation routes, review authority and the conditions for changing or withdrawing delegated decision rights.
The precise boundaries depend on the service, risk profile and enterprise structure. The essential feature is the alignment of responsibility, authority, resources and measurement.
The executive test
Before expanding a centre’s remit, leadership should be able to answer eight questions.
- 01Purpose: Which enterprise capability or business outcome requires greater ownership?
- 02Mandate: What purpose, outcomes, scope, authority and boundaries will be assigned?
- 03Authority: Which operational, financial, technology, people and process decisions will the centre make?
- 04Dependencies: Which decisions, resources and outcomes still require business, corporate or local approval?
- 05Readiness: What evidence demonstrates the centre’s ability to manage the proposed responsibility?
- 06Measurement: Which operational and business outcomes will establish whether the change delivers value?
- 07Accountability: Who resolves conflicts, accepts residual risk and intervenes when performance falls short?
- 08Review: Which conditions trigger reassessment, redesign or withdrawal of delegated authority?
If these questions have no clear answers, expanding the remit is unlikely to resolve the underlying problem.
Leadership should first determine whether the centre needs greater authority, additional capability, a different funding arrangement or clearer accountability across the enterprise.
Capacity is an input. Mandate determines how much value the centre can create.
Global delivery centres should not be judged solely by the work they absorb or the cost they remove.
Their contribution depends on a clear purpose, responsibility matched by authority, resources aligned with decision rights and measures connected to outcomes they can influence.
Some centres should focus on efficient execution. Others should own end-to-end services or processes. A smaller number might be suited to broader enterprise capability ownership.
The choice should follow business need, demonstrated readiness, risk and the operating model required to deliver the intended outcome.
The starting point is not a target headcount or a new organisational label. It is a decision about ownership.
What should your global delivery centre be authorised to own, which decisions and resources must accompany that ownership, and what evidence will demonstrate the value created?
Related frameworks
Related
Read next.
Journal · Transformation Operating Model
AI Transformation Does Not End When the New System Goes Live
Transformation is not only about what the organisation becomes. It is also about what the organisation is willing to leave behind.
Journal · Transformation Operating Model
AI Will Not Replace Your Operating Model. It Will Expose It.
When AI changes how work gets done, the operating model changes with it.
Journal · Organisation & Operating Model
Global Standardisation Does Not Mean Global Uniformity
Global transformation needs consistency, but consistency does not require identical execution. The executive challenge is deciding what must remain common, where local variation is legitimate, and how global delivery works across time zones, handovers and cultures.