6.2 CX Governance Structures

A CX strategy dies in the gap between “we agreed” and “someone decided.” Governance is the operating system that closes that gap. In Domain 2, CCXP candidates are expected to understand how decision rights, forums, ownership models, and escalation paths keep customer experience work aligned across business units, functions, and channels.

Governance is not bureaucracy for its own sake. It is the minimum structure needed so trade-offs are explicit, priorities stick, and customers do not experience the organisation’s org chart.

Why Governance Is a Strategy Competency

Experience is created at the seams: sales promises meet operations capacity; digital design meets contact-centre policy; product roadmaps meet compliance rules. Without governance:

• Local teams optimise channel or product KPIs that harm end-to-end journeys
• Initiatives duplicate or contradict each other
• Insight never reaches the person with authority to fund a fix
• Executives sponsor CX verbally but reallocate resources quietly

Exam pattern: when a scenario shows strong maps and weak progress, diagnose governance and decision rights, not only “more culture training.”

---

Decision Rights: The Core of Governance

Decision rights specify who may decide what, with what input, and under what constraints. Vague ownership (“CX owns experience”) fails because experience is multi-owned. Better models name decisions, not only titles.

RACI as a practical tool

Many organisations use RACI (Responsible, Accountable, Consulted, Informed) for CX decisions. Exam-useful principles:

• Exactly one Accountable party per decision class (avoid dual accountability without a tie-breaker)
• Responsible parties do the work; they are not automatically decision owners
• Consulted includes customers’ advocates (VoC, frontline, research) before irreversible choices
• Informed groups get change notices early enough to prepare operations

Decision rights failures to recognise

• Accountable everywhere, responsible nowhere — committees endorse, no one delivers
• Shadow vetoes — informal influencers reverse decisions after meetings
• Channel kings — each channel rewrites the intended experience independently
• Metric dictatorship — a single score owner blocks journey investments that help customers but temporarily dip the score

---

Forums: Multi-Level Operating Rhythm

Forums create the calendar and agenda where decisions happen. Different altitudes need different rooms.

Executive / CX steering committee

Purpose: set direction, approve major investment, resolve enterprise trade-offs, hold leaders accountable for outcomes.

Typical members: C-level sponsor, CX lead, product, operations, marketing/brand, digital, finance, risk/compliance as needed.

Cadence: monthly or quarterly for portfolio; ad hoc for major escalations.

Inputs: strategy progress, portfolio health, risk issues, cross-BU conflicts, benefit realisation.

Cross-functional journey / programme boards

Purpose: run priority journey programmes end-to-end; manage dependencies across functions.

Members: journey owner, process owners, tech product owners, insight lead, change/training lead.

Cadence: biweekly or monthly.

Outputs: backlog priorities, release readiness, pilot decisions, issue logs.

Working groups and squads

Purpose: design and implement specific components (notification redesign, billing root-cause pack, onboarding prototype).

Cadence: sprint or weekly delivery rhythm.

Community of practice (CoP)

Purpose: share methods, standards, and lessons; build capability. A CoP is not a substitute for a decision forum. It spreads practice; it does not allocate enterprise budget.

Exam cue: if every issue goes to the executive committee, governance is over-escalated. If nothing ever reaches executives, governance is under-powered.

---

Ownership Models

Ownership answers: who wakes up responsible when the journey fails?

Common ownership patterns

1. Central CX with federated delivery — a centre of excellence sets standards, methods, and portfolio view; business units deliver local execution. Strong for consistency; risk of ivory-tower standards if federal partners lack authority.
2. Distributed ownership with light centre — BUs own journeys; central team provides tools, research support, and facilitation. Strong for speed; risk of fragmented intended experience.
3. Journey ownership model — named journey owners accountable for end-to-end outcomes across silos, with matrix influence over channel and product partners. Strong for customer outcomes; requires real decision rights and executive air cover.
4. Product-led experience ownership — product managers own experience for digital products; CX partners on research and standards. Works in digital-native firms; weaker for multi-channel service enterprises unless extended.

There is no single correct model for all industries. The exam cares whether the model matches complexity and whether accountability is real (budget, metrics, escalation authority), not merely ceremonial.

What “real ownership” requires

• Named individual (not only a committee)
• Linked metrics on the owner’s scorecard
• Authority to convene partners and escalate blockers
• Access to insight and capacity for closed-loop action
• Visibility in governance forums

---

Cross-Business-Unit Governance

Customers experience one organisation. Internal structures often do not. Cross-BU governance prevents local optimisation that harms the whole.

When cross-BU structures are essential

• Shared customers across product lines (retail banking + cards + insurance)
• Multi-channel journeys with handoffs (store → app → contact centre)
• Shared platforms (CRM, billing, identity, logistics)
• Brand promises that cannot be fulfilled by one unit alone

Mechanisms that work

• Shared intended-experience principles approved at enterprise level
• Joint OKRs / outcome metrics for priority journeys (not only BU P&L)
• Portfolio visibility so parallel projects do not collide
• Service-level agreements between units for handoff quality
• Funding models that recognise shared benefits (chargebacks, joint investment pools)

Conflict patterns

---

Escalation Paths

An escalation path is a predefined route for issues that exceed local authority, capacity, or risk tolerance. Without it, teams either stall or invent political workarounds.

Design elements of a healthy escalation path

1. Thresholds — what triggers escalation (severity, regulatory exposure, multi-BU impact, investment size, brand risk)
2. Evidence pack — minimum data required (customer impact, volume, cost, options, recommendation)
3. Time service levels — how fast each tier must respond
4. Authority at each tier — what that forum can decide alone
5. Feedback loop — how the decision returns to frontline and customers

Example path:

• Tier 1: Team lead resolves individual recovery within policy
• Tier 2: Process owner / journey working group for systemic local fixes
• Tier 3: Cross-functional journey board for multi-function changes
• Tier 4: Executive steering for investment, policy, or brand trade-offs

Escalation anti-patterns

• Escalating every complaint to executives (noise drowning signal)
• Escalating without options or data (dumping problems upward)
• “Escalation” that is really a CC list with no decision owner
• Skipping tiers for political favourites, undermining the system

Scenario: telecom multi-play provider

A telecom sells bundled mobile, broadband, and TV. Customers face three billing units and three repair orgs. CX creates a Household Journey Board with shared metrics for move, billing accuracy, and fault resolution. Decision rights: board can resequence backlog items under a fixed quarterly envelope; larger platform investments escalate to Enterprise CX Steering with finance. Critical outages use a 24-hour severity path to operations and brand comms. Result: fewer “not my department” dead ends and clearer ownership when bundles fail — classic cross-BU governance in action.

---

Governance Health Checks

Use these diagnostics in exam scenarios and real assessments:

• Are priority journeys named with accountable owners?
• Do forums produce decisions, or only slide reviews?
• Can a cross-BU issue reach a decision within a known time?
• Are standards enforced at release gates, not only in brand books?
• Is benefit realisation reviewed after go-live?
• Do frontline escalations connect to systemic learning?

---

Exam Anchors

Match the failure mode to the governance gap: stalled trade-offs → missing decision rights or weak steering; siloed delivery → missing cross-BU forums or journey ownership; chaos escalations → missing thresholds and paths; lots of meetings, no change → forums without authority. On the CCXP, governance competence is designing who decides, where, with what evidence, and how conflicts rise — so strategy becomes operational reality.