CX = EX = Ops: The One System Behind All Three
Most CX initiatives fail because they're aimed at the wrong layer. I know because I ran one.
I was hired as Manager of Client Experience. Over three years, I transitioned into spending most of my time on operations problems. That wasn't a detour. It was the insight.
The First Discovery: EX Is Upstream of CX
When I stepped into the CX role, I did what CX managers do. I ran satisfaction surveys. I mapped client touchpoints. I analyzed where the friction was and designed programs to reduce it.
The results were marginal. Same complaints, slightly different phrasing on the survey.
The problem wasn't the programs. It was where I was looking. NPS and CSAT are trailing indicators. By the time a score lands in your dashboard, the cause of that score is weeks or months in the past. Heskett, Sasser, and Schlesinger documented this in their 1994 Harvard Business Review research, the “Service-Profit Chain”, showing that employee satisfaction and operational capability are the upstream drivers of customer loyalty, not the customer-facing layer on top.
So I stopped looking at the client-facing layer and started looking upstream.
The upstream variable was the employee experience. How employees felt about their work, their tools, their clarity of role — that showed up directly in client interactions. A new technician who'd completed two weeks of onboarding but left overwhelmed and under-prepared was handling client tickets, still relying on constant hand-holding for the first 90 days on the job. An account manager with no structured onboarding was re-asking questions clients had already answered. The client didn't know any of that. They just knew the service felt inconsistent.
The employee experience was the customer experience, separated by a few weeks of lag.
That realization changed what I worked on.
The Second Discovery: EX Problems Are Operational Problems
Once I started digging into employee experience, the pattern became clear fast.
Why were technicians inconsistent? There was some structure, but not enough, and the program leaned too heavily on shadow-based training — a new hire followed a senior technician and absorbed whatever that person happened to teach, delivered however they happened to deliver it. The speed and quality of what someone learned depended too much on who they were paired with, not on any consistent standard.
Why were account managers slow to build client relationships? They went through the same two-week onboarding as the support technicians — most of which wasn't relevant to their role. What they were missing wasn't more time with generic content. It was role-specific knowledge: their clients, the internal operations supporting those accounts, and how the two connected. They were expected to manage a portfolio before they understood the system they were operating inside.
Why were the same client issues recurring? Because we were resolving tickets, not problems. The same client could open the same issue six times and each ticket was treated as a new incident. Nobody was asking why the same issue kept coming back.
These weren't morale problems. They weren't people problems. They were operational problems — missing structure, missing process, missing standards. The employee experience was bad because the operations were bad.
From that point forward, I stopped thinking of my role as CX and started thinking of it as operations. The mandate didn't change. The work did.
Gallup's 2024 meta-analysis of 183,000 business units found that teams in the top quartile of employee engagement outperform the bottom quartile by 10% on customer loyalty. Gallup frames this as an engagement problem. It's an operations problem. Give people clear training, structured processes, and defined standards and the engagement follows. The engagement isn't the lever — it's the output.
Operational Infrastructure, Not CX Programming
Structured, testable training replaced shadow-based onboarding.
We rebuilt it from the ground up. Week one became foundational: company-wide context, culture, core processes. Week two became role-specific: the tools, workflows, and knowledge each function actually needed. One-hour sessions became 30-minute sessions or video modules. The content became standardized, so what a new hire learned didn't depend on who happened to train them that week.
The downstream effect: faster time to productive client interaction. The client experience in the first 90 days improved because new employees knew what they were doing before they were talking to clients.
For the Account Manager function specifically, the design was different. The two-week onboarding stayed, but we refocused it: it covered the critical day-to-day essentials they needed to function from day one. What came after was new — a structured 90-day training program that took them beyond basic orientation and built the depth the role actually required. Client knowledge, internal operations, how the business worked around them and their accounts. The goal was an AM who was genuinely ready to build client relationships, not just technically employed in the role.
Problem management workflows addressed recurring failures.
The previous approach: every ticket was a new incident. Resolve it, close it, move on.
The result was that the same clients were filing the same issues repeatedly. Each time, the team resolved it at the ticket level. Nobody asked why the problem kept coming back.
We built a workflow that flagged recurring patterns, escalated them to root-cause analysis, and tracked resolution at the problem level. The goal: stop solving the same problem twelve times and solve it once.
Explicit accountability frameworks replaced informal standards.
“Good” had never been formally defined. Technicians understood roughly what was expected, but expectations weren't documented, measured, or consistently applied. Which meant the quality of the client experience depended on which specific person the client reached on any given day.
We defined the standards: response time targets, resolution quality metrics, and escalation thresholds. We made them visible. Performance variance across the team started to close. Not because the high performers slowed down, but because the median performers finally had a specific target.
The Counterfactual
I can't point to a clean before/after CSAT number and say “this is what the operational work did.”
What I can point to is what happened when the operational infrastructure stopped being prioritized.
Leadership eventually shifted direction — toward client-facing improvements, new programs, surface-level changes. The operational work underneath didn't get the same attention. Some of what had been built eroded. The training rigor slipped. The problem management process lost its champion.
Churn followed.
Not immediately. These things move on a lag. But the correlation was there. The clients who stayed while the operational infrastructure was healthy started leaving when it wasn't. The accounts that had benefited from consistent, competent service started experiencing the inconsistency again.
That's not a scientific proof. But it's the clearest validation I have: when the operations were sound, the experience was sound. When the operations eroded, so did the experience — before anyone touched a single client-facing process.
What This Means for How You Staff Experience
Most organizations hire for experience: a CX coordinator, an EX specialist, a Director of Employee Engagement.
I'm not arguing against those roles. I'm arguing that they fail when they're separated from operational authority.
The experience, client and employee alike, is what happens when the operations work. You don't need a dedicated CX professional to improve client satisfaction. You need operators who understand that the quality of the system is the quality of the experience.
The Three-Question Diagnostic
Before launching a CX initiative, three questions surface whether you're treating symptoms or root causes.
Are your people genuinely ready before they're client-facing? Not just technically employed in the role — actually ready. Do they know your clients, your processes, and how the business operates around them? If not, the client is absorbing the cost of their learning curve.
Are you solving problems once, or solving the same problems repeatedly? If the same issues keep surfacing (different clients, different conversations, same root cause), you're not fixing things. You're managing them. That's an operational gap, not a communication one.
Does the quality of a client's experience depend on who they happen to work with? If your best person and your median person produce noticeably different outcomes, your system isn't doing its job. Consistency is an operational output, not a talent one.
If any of these have an uncomfortable answer, the client-facing playbook isn't the place to start.
NPS is the score. Operations is the game.
FAQ
Isn't this just saying “operations matter”? Everyone knows that.
Everyone knows it. Few act on it. The CX budget goes to a new tool, a redesigned touchpoint, a customer success hire. The onboarding process stays broken. The repeat ticket problem goes unaddressed. The performance variance stays wide. What I'm describing isn't a new idea — it's a consistent failure to follow through on an idea most leaders would claim to already believe.
How long does it take to see CX improvements from operational changes?
Faster than most leaders expect. Onboarding changes show up within the first new-hire cohort — typically 60–90 days. Problem management improvements follow within two to three months as recurring patterns decline. The results are usually visible before the next quarterly review.
How do you make the case for operational investment when leadership wants CX improvements?
Lead with the connection. Show your onboarding timeline next to your first-90-days CSAT. Show your repeat ticket rate and what it costs in support hours. Operational investment is CX investment — the mechanism is indirect, the outcome is direct.
Sources:
Heskett, J.L., Jones, T.O., Loveman, G.W., Sasser, W.E., & Schlesinger, L.A. (1994). Putting the Service-Profit Chain to Work. Harvard Business Review.
Gallup. (2024). State of the Global Workplace: The Employee Engagement Meta-Analysis, 11th Edition. Analysis of 183,000 business units and 3.3 million employees.