GCCs Should Create Value, Not Just Reduce Costs

A cost mandate is a finite resource. It can be delivered once, it is booked once, and after that it can only be defended. Every capability centre built purely on a savings case eventually reaches the quarter where there is no further saving to announce, and the conversation shifts from what the centre achieved to what it costs. That shift is not a communication failure. It is what a cost mandate is designed to produce.

A value mandate behaves differently because it compounds. Ownership accumulates, context deepens, and the centre becomes progressively harder to replace. The difference between the two is not ambition or messaging. It is a set of design decisions taken in the first six months, most of which are irreversible in practice once made.

This guide sets out why the cost mandate plateaus, what specifically has to be different in a value oriented centre, and how to make the transition if you already have a centre stuck in the first mode.

Why the cost mandate plateaus

The arithmetic is unforgiving. A savings case compares a new cost base against a previous one, and that comparison can only be made once. In year one it produces a large, satisfying number. In year two the comparison is against year one, and the only way to produce another saving is to reduce cost further, which in a people business means either fewer people or cheaper people.

This is where the mandate turns against itself. Reducing seniority is the fastest available lever, and it directly removes the capability that would have allowed the centre to do anything more valuable. A centre that responds rationally to a cost mandate systematically dismantles its own potential, and it does so while hitting every target it was given.

The plateau typically becomes visible between month eighteen and month thirty. The centre is running well, the savings are real and booked, and leadership starts asking a question the centre has no way to answer: what would we lose if this went away? If the honest answer is a cost increase and some disruption, the centre is a procurement decision rather than a capability, and it will be treated as one.

What a value mandate actually requires

Value creation is not a cultural aspiration that can be added later by changing how the centre is described. It requires four specific structural conditions, and each of them is expensive in exactly the terms a cost mandate is trying to minimise.

The cost and value mandates compared

The two mandates diverge on almost every operating decision. The table below sets out where, because in practice the divergence shows up as a series of small choices rather than one large one.

Note the utilisation row. A centre running at full allocation has no capacity to improve anything, which is why high utilisation targets and value mandates are structurally incompatible.

The utilisation trap

One decision deserves separate treatment because it is so commonly made without recognising its consequences. A centre measured on utilisation will be scheduled close to full allocation, since idle capacity looks like waste on a cost report.

But every improvement a team makes to its own systems, every piece of tooling, every refactor that reduces future cost and every exploratory piece of work happens in capacity that was not allocated to a scheduled deliverable. A centre at ninety five percent allocation cannot improve anything. It can only execute, and it will look extremely efficient while its systems slowly degrade.

The practical answer is to allocate deliberately rather than maximally. A commonly workable split reserves a meaningful share of capacity for work the team chooses, defended explicitly in the operating plan so it is not the first thing cut when a deadline approaches.

How to make the transition if you are already stuck

Most centres reading this already exist and are already operating on a cost mandate. The transition is possible, and it is slower than a fresh build because it requires changing expectations that have been reinforced for several quarters, in both directions.

Three questions that expose which mandate you are really running

Stated intent is a poor guide, because almost every capability centre describes itself as a value partner regardless of how it operates. These three questions produce a more reliable answer, and all of them can be asked in a single review meeting.

The first is what happens when the centre encounters genuine ambiguity. If the answer is that it escalates and waits, the centre is running a cost mandate whatever the strategy document says. The second is what the centre worked on that nobody asked it to. If the answer is nothing, there is no capacity for value creation and none will occur. The third is what would have to be rebuilt if the centre closed tomorrow. If the answer is nothing specific, no capability has accumulated and the centre remains a procurement arrangement.

• When the team hits ambiguity, does it decide or does it wait?
• What did the team build in the last quarter that nobody asked for?
• What specifically would have to be rebuilt if the centre closed?
• Who is the most senior person in the centre, and what do they decide?
• How many people have held the same problem area for more than a year?

What to watch for

The transition fails in predictable ways, and most of them are failures of nerve rather than of design.

• Announcing a value mandate while leaving cost per FTE as the headline metric
• Transferring ownership but retaining an approval gate, which transfers accountability without authority
• Cutting the reserved improvement capacity at the first schedule pressure
• Expecting the change to show in delivery metrics within one quarter
• Adding headcount to a centre that has no decision authority, which multiplies the bottleneck
• Leaving the same onshore approver in place while telling the team it now owns the decision

Frequently asked questions