Chief GBS Orchestrator
Chief GBS Orchestrator
The emerging top role in Everest Group's "future of GCCs" view (GCC Philippines Summit 2026 (PHx)): a leader accountable for enterprise flow, execution coherence, and value realization, who owns outcomes across human + AI execution.
- Peer to the CIO / CFO / CHRO — not a sub-function. The role elevates GCC/GBS leadership from delivery management to enterprise orchestration.
- Sits atop the five "future of GCCs" statements: work matters more than functions; judgment trumps execution; AI exposes weak models (it won't fix them); funding follows workflows, not headcount; work is placed in a network, not allocated to centers or vendors.
Why the role appears now
As agentic teams blur the human/agent line and value moves to high-context work, someone must own the flow across the enterprise rather than a functional silo. This is the org-design answer to the Headcount-to-Value Pivot and the antidote to the GCC Value-Perception Gap (a single accountable owner of value realization). Compare the IT-side org rethink in Designing IT Roles for an AI Era (Talent Strategy POV).
2026-08-10 — Cohen's management-skill vocabulary, and D'Appio's capability-boundary critique
Seth Cohen (CIO, Procter & Gamble) in his LinkedIn post independently reaches for "orchestration" as the load-bearing vocabulary for the AI-era management skill — from the CIO seat, not the GBS/outsourcing seat Everest is naming. This is a second-register touch on the same word: Everest names it as an org-design role; Cohen names it as an individual management skill every manager will need. Same skill; different unit of analysis.
Load-bearing counter from the same ingest — Saverio D'Appio: "calling the skill 'orchestration' risks making it sound like a coordination problem when it's really a judgment problem about capability boundaries that keep shifting underneath you." This is the honest critique of the vocabulary — whoever holds the Chief GBS Orchestrator role in practice is doing capability-boundary judgment continuously, not fixed coordination. The role prescription should probably be framed as "orchestrator" externally but understood as "capability-boundary judge" operationally. Cross-link: Bounded vs Unbounded Tasks is the vault's anchor on the underlying question, and the Manager as Translator concept holds the broader articulation-skill thesis this role is one org-design expression of.