The hidden friction inside many GCCs (that doesn’t show up on dashboards)

Some of the friction inside GCCs is not loud.

It doesn’t escalate.

It doesn’t turn dashboards red.

But it quietly shapes behavior.

Over the past decade, many Global Capability Centers have evolved dramatically.

From cost centers to capability hubs to strategic partners

- The charter has expanded.

- The ambition has grown.

- The language has matured.

But inside many GCCs, a quiet friction remains.

Not because capability is missing.

Not because leaders lack intent.

The friction begins when:

 - Expectations are  GCC-level

 - Evaluation is GDC-level

 - Autonomy feels ODC-level

That’s when behaviour shifts.

When expectations are GCC-level, teams are asked to:

- challenge and influence upstream decisions

- Navigate ambiguity

- exercise judgment

- co-own outcomes

But if evaluation still focuses on:

 - SLAs, timelines, utilization

- compliance, visible proof

the operating signal changes.

And if autonomy still requires:

- repeated validation

- layered approvals

- external comfort before closure

then the system behaves differently from the ambition.

None of these models are wrong.

GCC, GDC, and ODC each serve a purpose.

The friction emerges only when:

- the label says “strategic partner” (GCC)

- but the review model says “delivery engine” (GDC)

- and the decision rights say “execution arm” (ODC)

This hidden friction doesn’t show up in dashboards.