Bram De VosCustomer experience is created across the organisation, but that does not remove the need for a team responsible for the way it is measured and improved. This article covers what that team should own, the three structures that work, the four roles that matter before any headcount discussion, and the traps that quietly turn a CX team into a reporting desk.
Key takeaways:
- Departments own their part of the experience; the CX team owns the system used to listen, prioritise and follow up. Confusing the two is the root of most dysfunctional setups.
- Three structures cover almost every case: centralised, embedded specialists, and hub and spoke. Start centralised, grow toward hub and spoke as demand grows.
- Staff roles before headcount: a lead, an analyst, journey owners and a programme manager can be one person or eight, but the responsibilities are the same list.
- Judge the team on fixes shipped and their measured effect, never on the score alone. Forrester expects metrics obsession to pull 15% of CX teams into a death spiral under 2026 budget pressure.
- A small team with a mandate beats a large team with a dashboard.
Why team design suddenly matters more
For four consecutive years, customer experience quality in the US has declined; in Forrester's 2025 CX Index, 25% of brands lost ground and only 7% improved. Forrester's analysts attribute the slide partly to weaker employee experience and waning customer obsession: organisational problems, not measurement problems.
That is worth sitting with for a moment. Most companies now run surveys, dashboards and feedback tooling, yet the experience customers actually receive keeps getting worse. The missing piece is rarely another metric. It is a team constructed so that findings travel from the data to the department that can act, with someone accountable at every step.
Ownership at the top has largely been settled; most sizeable organisations now have a chief experience officer, chief customer officer or an equivalent. The question below that title is still open in most companies: who does the work, and how is it organised?
What a customer experience team actually does
The CX team does not own every interaction a customer has. Those interactions are delivered by teams throughout the business, many of whom will never report to the CX lead.
What the team can own is the system that improves the experience:
- Listening. Surveys, reviews and customer interactions, collected across every touchpoint.
- Analysis. Turning scores and open feedback into ranked priorities.
- Activation. Getting the right finding to the right department, with the evidence attached.
- Follow-up. Closing the loop with customers and re-measuring after every fix.
- Reporting. One honest set of numbers for leadership.
In other words: departments own their part of the experience. The CX team owns the system used to listen, prioritise and follow up. Write that boundary down early, because every trap described later in this article is a blurred version of it.
The system needs something to aim at. A team that maintains beautiful listening infrastructure with no stated business goal is a cost centre waiting for a budget review; the goal comes from the customer experience strategy, and the team's job is to serve it.
Three ways to structure the team
A centralised team. All CX work sits in one department: measurement, analysis and improvement projects. This fits companies that are starting out, or that have one dominant customer journey. The risk: the team keeps working on its own and produces reports nobody asked for.
Embedded specialists. Each department has its own CX person, close to the work. This fits large organisations with very different business lines. The risk: five departments, five definitions of the customer, and no one watching the whole journey.
Hub and spoke. A small central team runs the tooling, the analysis and the standards; named people inside each department act on the findings. The hub guards consistency, the spokes deliver the change.
A centralised model is often the simplest place to start, because a new discipline needs focus. Add named contacts in the departments as demand grows. Fully embedded specialists tend to make sense only in larger, diverse organisations, and even then a small central hub is useful for consistency.
A decision test that beats the org chart
If you are torn between models, answer three questions honestly:
- How many genuinely different journeys do you run? One dominant journey argues for centralised; a retail arm plus a B2B arm plus a service business argues for spokes.
- Where does change actually get made? If every fix lands in operations, put your first spoke there and nowhere else.
- Who defends the findings when they are inconvenient? If the answer is "nobody outside the CX team," no structure will save you; solve the sponsorship problem first.
The model is a consequence of those answers, not a choice made in the abstract.
The roles, before the headcount
These responsibilities may sit with one person in a small company and with separate specialists in a larger one:
- A CX lead, who owns the strategy, the budget conversation and the reporting to leadership.
- An insights analyst, who reads the data and the verbatims and ranks the findings, using a key driver analysis to separate the themes that move the numbers from the themes that are merely loud.
- Journey owners, one accountable person per key journey, usually inside the departments rather than the CX team.
- A voice of customer programme manager, who keeps surveys, response rates and close-the-loop routines healthy. What that programme involves end to end is a discipline of its own; the voice of the customer guide covers it in full.
Notice what is not on the list: a complaints handler, a survey administrator, a dashboard builder. Those tasks exist, but they are activities inside the four roles, not roles in themselves. Teams that hire for the activities end up doing only the activities.
How big should the team be?
Smaller than most org charts suggest:
- The first hire: one person senior enough to work with department heads, supported by tooling for the analytical workload. The role requires as much influence as analysis, so it is rarely a good first job for a junior profile.
- Scale-up: two to four people, typically the lead, an analyst and a programme manager.
- Enterprise: a hub of four to eight, plus journey owners in the departments as spokes.
Headcount alone says little. A small team with a clear mandate and access to decision-makers will usually achieve more than a larger reporting team with no route into delivery.
AI has changed the arithmetic here, but not in the way the headlines suggest. In Gartner's late-2025 survey, only 20% of customer service leaders reported any AI-driven headcount reduction, while 55% held staffing stable at higher volumes. The honest reading for CX teams: tooling that classifies open feedback automatically, the way a platform like Hello Customer does, lets one analyst cover what used to take a small team. It does not remove the need for the analyst, the mandate or the conversations with department heads. Machines read; people move organisations.
Where should the team report?
CX leaders report to CEOs, CMOs and COOs. Each line creates a natural bias: marketing towards brand and acquisition, operations towards cost and efficiency, and the CEO towards a company-wide view. None of these structures is automatically right.
Use a more practical test. Can the team put a finding on the agenda of another department, and does that department have capacity to respond? If the answer to both is yes, the reporting line matters less than the org-chart debates suggest.
Three traps that weaken a CX team
The complaints department. If the team spends its days solving individual cases, it has become an escalation desk. Individual cases belong with customer service; the CX team works on the patterns behind them.
Owning the score. A team judged only on NPS will start managing the number: survey timing, question phrasing, which customers get asked. Forrester's prediction for 2026 puts a figure on where that road ends: budget pressure will lure 15% of CX teams into a "death spiral" of metrics obsession, polishing real-time dashboards while their influence on the business shrinks. Judge the team on fixes shipped and their measured effect instead.
Measuring without a mandate. Findings that never make it into a roadmap do not improve the experience. Agree in advance how departments will reserve capacity for issues the CX work identifies.
The first ninety days
A new CX team, or a newly restructured one, earns its mandate faster with a deliberate opening sequence:
- Weeks 1 to 4: establish the baseline. Run a structured audit of the current customer experience instead of commissioning new dashboards. The audit produces the first ranked list of problems and, just as valuable, the first working relationships with the departments that own them.
- Weeks 5 to 8: ship one visible fix. Pick a finding that is cheap to fix and easy to measure. The point is not the fix itself; it is demonstrating the full loop from feedback to change to re-measurement.
- Weeks 9 to 13: formalise the operating rhythm. A monthly priorities review with department heads, one shared set of numbers, and a public record of what was fixed and what it did.
Teams that start with infrastructure projects spend their honeymoon period invisible. Teams that start with one closed loop have something to show when the first budget question arrives.
Frequently asked questions
Who should own customer experience?
Every department owns its part of the experience, the CX team owns the measurement and improvement system, and one executive sponsor owns the mandate. You need all three at once.
How big should a customer experience team be?
One senior person plus a platform to start, two to four in a scale-up, a hub of four to eight in an enterprise, with journey owners in the departments. Mandate matters more than headcount.
Should the CX team sit in marketing?
It can work, especially where the brand promise and the experience are managed together. Watch for drift toward acquisition topics, and apply the test above: can the team move a finding in operations or product, and does something happen?
What is a hub-and-spoke CX team?
A small central team (the hub) runs the tooling, analysis and standards, while named people in each department (the spokes) act on the findings. It combines one consistent view of the customer with execution close to the work.
When should you hire your first dedicated CX person?
When feedback is being collected but nobody has the time to act on it. That gap usually shows up in the churn numbers before it shows up on the management agenda.
A practical division of responsibility
The most workable arrangement is clear about the boundary: operating teams deliver the experience, a central CX capability maintains the listening and improvement system, and an executive sponsor protects the cross-functional mandate. Confusing those roles is what turns CX into either a reporting function or a complaints desk.
Four years of declining CX scores across entire markets say that most companies have not yet built that arrangement. The ones that do will not need to explain what the CX team is for.
If executive sponsorship is the missing piece, start with getting management on board with a voice of the customer programme.