The reporting ritual
Most organisations don't have a governance process. They have a reporting ritual. It happens monthly. Sometimes quarterly. The right people are in the room. Someone presents the NPS results. A slide deck moves through the key metrics. Notes are taken. And then everyone goes back to their desks. And nothing changes.
The reason is structural: most CX governance meetings are designed to report — not to decide. That single distinction explains why organisations can run rigorous monthly governance for two years and still find the same customer problems on the same agenda, meeting after meeting.
McKinsey research finds that 61% of executives consider at least half their decision-making time ineffective. Only 37% say their organisation's decisions are both timely and high quality. In CX governance specifically, the problem compounds: a reporting meeting is structurally incapable of producing the output it is supposed to deliver.
"This is why CX dashboards improve while customer experience doesn't. The organisation is measuring better. It is not deciding better."
The four failure modes
Failure Mode 1: Data without diagnosis. The meeting presents metrics but does not interrogate them. NPS is down three points. The slide moves on. Nobody asks: what decision does this require?
Failure Mode 2: Discussion without decisions. The meeting generates good conversation. Problems are identified. Root causes are debated. The meeting ends with a general sense that something should be done. No decision is recorded. No owner is named. No deadline is set.
Failure Mode 3: Actions without authority. The meeting does produce actions — but the person assigned the action does not have the authority to complete it. It requires sign-off from a function that was not in the room. The action stalls. It reappears — slightly reworded — at the next meeting.
Failure Mode 4: Attendance without accountability. Representatives from every function are present — but they are there to report on their area, not to make decisions about the whole. When a cross-functional issue is raised, each representative defers to their function head.
A meeting without decision authority is not governance. It is theatre. McKinsey research on decision effectiveness finds that organisations which excel at decision-making generate returns more than four times higher than their peers.
The four requirements of a real governance meeting
1. Decision authority in the room. The people present must have the authority to make decisions — not to recommend them to someone else. The meeting must be chaired by someone with cross-functional mandate: a CEO, COO, or CCO with real authority.
If every decision made in your governance meeting requires subsequent approval from someone who was not in the room, you do not have a governance meeting.
2. A structured decision log. Every meeting must produce a decision log — not meeting minutes, not action points, but a record of decisions made, owners assigned, deadlines set, and the consequence if the deadline is missed.
Without a stated consequence, a deadline is a suggestion.
3. Pre-read data, not in-meeting presentations. Data should arrive before the meeting, not during it. Send the data in advance. Open the meeting with one question: given what we know, what decisions do we need to make today?
4. Escalation as a designed outcome. A well-designed governance meeting has a clear escalation path: who receives escalated decisions, in what timeframe, and by what mechanism. Escalation is not a failure of governance. Unresolved escalation is.
What a real CX governance meeting looks like
Before the meeting: Customer data distributed to all participants at least 48 hours in advance. The meeting does not begin with a presentation. It begins with a decision.
10 min — Opening: Review of the decision log from the previous meeting. Each open item is confirmed complete, formally escalated, or closed with explanation. No item carries forward without a named reason and a named owner.
40 min — Agenda: Two or three pre-agreed topics, each framed as a decision to be made — not a problem to be discussed. Each topic owner presents the issue in under five minutes, proposes a decision, and invites challenge. The meeting decides. The decision is logged immediately, including owner, deadline, and consequence if missed.
10 min — Escalations: Items that cannot be decided in the room are formally escalated with a named recipient, deadline, and consequence. Recorded in the decision log — not deferred to the next meeting.
5 min — Close: The decision log is read back. Every participant confirms their commitments.
The governance audit
Pull up the notes from your last three CX governance meetings. Count the decisions made — not actions, not follow-ups. Decisions. With a named owner and a deadline. Then count how many of those decisions were completed by the agreed deadline.
If the first number is zero: you have a reporting ritual. Rename it accordingly — and then design the governance meeting your organisation actually needs.
If the second number is significantly lower than the first: you have a decision log without enforcement. The decisions are being made. The accountability structure to execute them is missing.