This is the third in a series on the Golden Thread and your systems. If you haven’t read Where the Golden Thread Breaks Most Often or Strategy Is a System, Not a Statement, it’s worth starting there.
We’ve established that the Golden Thread breaks when what leaders say, what systems reward, what managers enforce, and what employees can actually do fall out of alignment. We’ve established that strategy isn’t a statement but a system. Now let’s get specific about what that system actually is, why it’s so hard to change, and what it looks like to build one that actually delivers the experience you say you want.
Because here’s the thing: you already have a system. Every organization does. The question isn’t whether you have one; it’s whether yours was designed intentionally or whether it evolved by default. And if it’s the latter, it’s already working against you.
What We Mean by “System” (And What We Don’t)
Before we go further, let’s be precise because this is where most conversations go off track. When I say “system,” I don’t mean technology. I mean the operating reality of the business, i.e., the set of structures and mechanisms that shape how work gets done and how decisions get made every day.
Your system includes:
- Policies and processes
- Metrics and incentives
- Decision rights and governance
- Workflows and hand-offs across functions
- Resource allocation and prioritization
It’s the environment your employees operate within. And whether you designed it intentionally or not, it’s already producing outcomes, consistently.
System vs. Culture: Not the Same Thing
This is where leaders get tripped up. They talk about “culture” and diagnose a culture problem when the real issue is the “system.” The interventions that follow don’t actually fix anything.
Here’s the distinction:
- Culture is what people believe, value, and feel
- System is what people are required, enabled, and rewarded to do
Culture shapes intent, while the system shapes behavior. They are deeply related (especially given that culture = core values + behaviors), but when the two are misaligned, the system wins. Every time. (You did build the system through the lens of your core values, right?)
You can say “put the customer first” all day long, but if your metrics reward speed over quality, your processes create friction, your approvals slow everything down, and your leaders prioritize cost reduction over experience investment, then employees will follow the system, not the culture. Not because they don’t care but because the system defines reality.
The diagnostic question: Where is your system working against the experience you say you want to deliver? That’s the question that leads to real change. “How do we create a more customer-centric culture?” is the wrong starting point.
The Five Forces That Shape Every Experience
Experience isn’t created at the brand level. It’s produced at the interaction level, i.e., thousands of micro-decisions made across the organization, every day. Those decisions are shaped by five forces. Get these right, and the experience follows. Leave them misaligned, and no amount of training, journey mapping, or engagement investment will close the gap.
1. What gets measured
If teams are measured on speed, they’ll rush. If they’re measured on cost, they’ll cut. And if experience is on the scorecard but cost is what actually drives decisions, cost wins. Every time. Your metrics are a map of your real priorities, not the ones on the slide but the ones people navigate by every day.
2. What gets rewarded (and punished)
People don’t do what you say you value; they do what they believe will advance or protect their careers. If doing right by the customer creates internal risk, e.g., a missed metric, a conversation with a manager, a performance flag, then it won’t happen consistently. Reward systems are a direct expression of what the organization actually values, regardless of what’s written on the wall.
3. How decisions get made
When tradeoffs show up – and they always do – who decides? Is the decision centralized or pushed to the front line? Is there a clear principle that guides judgment, or does every exception require escalation? If employees have to guess, the experience will be inconsistent. Clarity here isn’t a nice-to-have; it’s actually the difference between empowerment and hesitation.
4. How work actually flows
This is where most strategies quietly die: cross-functional hand-offs, siloed systems, conflicting priorities, and the processes that were designed for internal convenience rather than for customer outcomes. Customers don’t experience your org chart; they experience the flow of work across it – and, more often, the friction where that flow breaks down.
5. What leaders actually prioritize
They don’t prioritize what they say in town halls but what they fund, attend to, question, and tolerate. Organizations align to leadership behavior faster than to any strategy document, values framework, or all-hands message. Leaders are the system’s most powerful signal, and most don’t realize how closely they’re being read.
When these five forces are aligned, the experience feels intentional, consistent, and human. When they’re not, the employee caught between them has to make a choice. That choice, made thousands of times a day, is the experience your customers actually receive.
Why Most Companies Don’t Fix This
There are certainly a lot of reasons this choice is forced upon employees, but the big reason when it comes to experience management work is that companies focus on the visible layers, like journey maps, voice of the customer programs, training programs, CX certifications, and employee engagement efforts. Those are all important but not sufficient.
They are used to improve the experience without changing the system that produces it. That’s like redesigning the output without touching the engine. You’ll get short-term gains, isolated wins, and a persistent sense that something still isn’t working – because it isn’t.
Real change requires going deeper than the experience itself. It requires looking at the machinery underneath it.
What It Takes to Build Systems That Deliver the Experience
The previous articles in this series covered defining the experience and aligning strategy to outcomes:
Where the Golden Thread Breaks Most Often and Strategy Is a System, Not a Statement
What follows are the three system-level moves that most organizations skip and that make the difference between a strategy that looks good on paper and one that actually produces results.
1. Redesign Decision Rights
Clarity beats control. Always. So it’s time to define what decisions can be made at the frontline without approval, what requires escalation (and why), and what principles guide judgment (especially in ambiguous moments). Then back it up, visibly and consistently. If employees are “empowered” but then second-guessed every time they act on it, you’ve built hesitation, not empowerment.
Diagnostic question: When a frontline employee has to make a call in a difficult customer moment, do they know, without asking, what they’re authorized to do? If not, the system (not the employee) is creating inconsistency.
2. Fix the Work, Not Just the Moment
Stop optimizing isolated touchpoints. That’s pointless. Customers don’t experience touchpoints; they experience the flow between them. That means mapping where work breaks across functions, identifying friction caused by internal complexity rather than customer needs, and redesigning processes end-to-end. Service blueprinting is your friend here. (Get to the heart of the matter, the root of the problem.) The goal isn’t a better interaction at one point in the journey; it’s a journey that holds together.
Diagnostic question: Where in your customer journey does the experience degrade, and is that degradation caused by something the customer did or something your internal hand-offs created?
3. Build Accountability Into the System
If experience is everyone’s job, it’s no one’s job. That’s not a cliché; it’s an organizational design problem. Establish clear ownership across the journey, establishing governance that connects employee experience, customer experience, and operational performance, and creating regular reviews that focus on decisions and tradeoffs, not just on data. And most importantly, hold leaders accountable for alignment, not just for outcomes. Outcomes are what the system produces; alignment is what the system is.
Diagnostic question: Who in your organization is accountable when the customer experience breaks down at a cross-functional seam? If the answer is unclear or contested, that’s your next design problem.
In Closing
You already have a system. Every company does. The question isn’t whether you have one but whether it’s designed intentionally or it evolved by default because of a series of decisions that made sense individually but created misalignment collectively.
Most fall into the second category. While most leaders know that, they just don’t know where to start.
Start with the five forces. Audit what you measure, what you reward, how decisions get made, where work breaks down, and what your own behavior signals to the organization. That’s your system, made visible. And that’s where the experience is actually built – not in the brand promise, not in the training room, not in the journey map. In the system.
Fix the system. Fix the experience. Fix the outcomes.
Your systems are perfectly designed to get the results that you are getting. ~ Stephen R. Covey
Want this thinking applied inside your organization?
Image courtesy of Erinada Valpurgieva on Unsplash