5 KPIs That Prove Your GCC Is a Value Center, Not a Cost Center

The problem with most capability centre metrics is that a struggling centre can produce good numbers on nearly all of them. Throughput can be raised by taking smaller work. Utilisation can be raised by allocating everything. Cost per head can be improved by hiring more junior people. Each of these makes the centre worse and the report better.

The five metrics below are useful precisely because they are hard to fake. Each one requires the centre to actually be creating value in order to move, and each one degrades if the centre takes the easy path. Together they form a scorecard that cannot be gamed without genuinely improving.

None of them is a cost metric. That is deliberate. Cost belongs in the report, but it belongs in the appendix once the centre is past its first year.

1. Escalation rate

Escalation rate is the proportion of work items that require an onshore decision before they can proceed. It is the single most revealing metric available and the least commonly tracked.

It is hard to fake because the only way to reduce it is to genuinely increase the centre s ability to decide. A centre can raise throughput by taking easier work, but easier work also escalates less, so the metric moves for the right reason either way. A centre cannot lower escalation rate by working harder; it can only lower it by knowing more and being permitted more.

Track it as a trend rather than a level, because the starting level depends on the domain. What matters is direction. A centre where escalation is flat after four quarters is a centre where authority has not actually moved, whatever the governance documents say.

2. Systems owned end to end

Count the systems, services or roadmap areas for which the centre holds full responsibility with no onshore approval gate. Not systems it contributes to; systems it owns, including the right to decide how they change.

This is a small integer, usually between zero and about ten, and its bluntness is its strength. A centre that has been running for two years with a count of zero has a scope problem that no other metric will surface as clearly. It also resists gaming, because ownership either exists or it does not, and everybody involved knows which.

The useful refinement is to track how the count changes and what was transferred each quarter. A count that has not moved in a year indicates the transfer programme stopped, which usually happens quietly rather than by decision.

3. Onshore hours consumed per unit of output

This is the most underused metric in the entire field. Measure the onshore leadership and engineering time spent supervising, reviewing, unblocking and coordinating the centre, then express it against the centre s output.

It matters because onshore time is the cost that the capability centre was supposed to reduce and is the one nobody counts. A centre that appears cheap while consuming two days a week of a principal engineer s time onshore is not cheap; the cost has simply moved somewhere the model does not look.

It is difficult to fake because reducing it requires the centre to genuinely need less help. It also has a useful property as a leading indicator: it usually starts falling a quarter or two before ownership metrics move, because the team stops asking before it formally takes over.

4. Regretted attrition among senior engineers

Total attrition is a weak metric because it mixes very different events. The number that matters is regretted attrition among senior engineers: people you wanted to keep, at the level where context is concentrated, leaving voluntarily.

It is a value metric rather than a people metric because senior departure is the fastest way a capability centre loses accumulated context, which is the actual asset. It is also the earliest reliable warning that something structural is wrong. Senior engineers leave when the work stops being interesting, which usually means ownership was withdrawn, scope narrowed or decisions moved back onshore.

It is hard to fake because compensation alone does not hold senior people in a market where they have options. A centre with strong senior retention is almost always a centre where the work is genuinely worth doing.

5. Adopted proposals

Count the number of things the centre proposed that the business subsequently adopted. Not tasks completed; ideas originated in the centre that changed what the company does.

This is the clearest evidence that a centre has moved from executing to contributing. It requires the centre to understand the business problem well enough to have an opinion, and it requires the organisation to be willing to receive one. Both conditions have to hold, which is why the number is so informative.

It starts at zero for every centre and stays there for a while, which is normal. What matters is whether it ever moves. A centre in its third year with a count of zero is a centre the business has never treated as a source of ideas, and that is a relationship problem rather than a capability problem.

How they fit together

Individually each metric can be explained away. Together they are difficult to argue with, because they move in a coherent pattern only when the centre is genuinely improving.

If throughput and cost per head improve while these five stay flat, the centre is optimising its report rather than its contribution.

How to instrument them

Four of the five come from systems you already run. Only onshore hours requires a new habit, and it can be sampled rather than tracked continuously.

What to stop reporting

Adding metrics without removing any produces a report nobody reads and a centre that optimises for whatever is at the top. Three things should move to the appendix or disappear.

• Cost per FTE as a headline. Keep it available, move it to the appendix after year one.
• Utilisation as a target. A centre at full allocation cannot improve anything.
• Raw throughput without reference to what was delivered, which rewards taking smaller work.
• Headcount as a measure of progress, which confuses growth with contribution.
• Savings versus original baseline after year two, when the comparison has stopped being informative.

Frequently asked questions