Editor’s Note

This article is part of The Experience Center Operating Model, a series exploring what it actually takes to run a modern support experience center at scale, across people, automation, governance, and culture.

You will meet Jeff throughout this series. Jeff is a fictional character, but his situations are not. If he feels familiar, it is because most leaders pass through the same moments, face the same pressures, and make the same mistakes, often without realizing what is happening until the system pushes back.

If you arrived at this page by chance or through search, I recommend starting at the main series page to understand why this work exists and how the parts connect.

→ Visit The Experience Center Operating Model

Jeff had reached the point most leaders never do.

The tools were solid.
The workflows were documented.
Automation was governed.
Metrics drove action.
Coaching changed behavior.
Quality produced intelligence.

On paper, the system worked.

And yet, results still varied.

Not wildly. Not catastrophically. But enough that Jeff could see a pattern the dashboards could not explain. Two teams with the same tools, same processes, same metrics produced different outcomes.

The difference was not skill.

It was culture.

That was the eleventh lesson Jeff learned about running a support experience center.

Culture is not a value statement. It is the behavior the system rewards under pressure.


Culture Shows Up When No One Is Watching

Jeff stopped asking people what the culture was.

He started watching what happened when things broke.

Did teams hide issues or surface them early.
Did managers protect metrics or protect customers.
Did agents escalate uncertainty or guess and move on.
Did leaders reward speed, or judgment.

The answers were never found in posters or onboarding decks.

They were found in micro decisions made every day.

Culture was not what leadership said mattered.

It was what the system made safe.

Leadership Call Out
Culture is revealed by what people do when the rules are inconvenient.
Not when they are easy.


Incentives Shape Behavior More Than Intent

Jeff traced most cultural drift back to incentives.

What got promoted.
What got praised.
What got ignored.
What got quietly punished.

Managers who protected service levels at all costs were celebrated. Managers who slowed things down to protect quality were questioned. Agents who escalated early were seen as inefficient. Agents who “handled it themselves” were praised, even when it caused rework later.

None of this was intentional.

But the message was clear.

Speed mattered more than judgment.

Once Jeff saw it, he could not unsee it.

Operational Reality Check
You do not get the culture you intend.
You get the culture your incentives produce.


AI Amplifies Culture, It Does Not Create It

Automation made this unavoidable.

Where culture valued transparency, AI became a safety net. People flagged bad suggestions. They questioned outputs. They improved the system.

Where culture valued appearance, AI became a shield. People trusted outputs without scrutiny. Errors moved faster. Accountability blurred.

The technology behaved the same.

The culture determined whether it helped or harmed.

Jeff realized something critical.

AI did not introduce new cultural risk.

It amplified the existing one.

Leadership Call Out
AI will not fix a weak culture.
It will scale it.


Leaders Are the Primary Cultural Interface

Jeff initially assumed culture lived with HR.

He was wrong.

Culture lived with leaders who made tradeoffs in real time.

When leaders bypassed governance to move faster, others followed.
When leaders tolerated exceptions without review, norms shifted.
When leaders ignored weak signals, people learned to stay quiet.

Every shortcut taken at the top echoed through the system.

Jeff made the hardest change of all.

He slowed himself down.

He modeled escalation instead of improvisation.
He asked for rationale instead of results.
He rewarded people who stopped the line.

Not performatively.

Consistently.

What Leaders Often Miss
Culture does not cascade from strategy decks.
It propagates from leadership behavior under stress.


Culture Must Be Designed Like Any Other System

Once Jeff reframed culture as a system, everything changed.

Culture had inputs.
Signals.
Reinforcements.
Failure modes.

It could be shaped.

They made cultural expectations explicit inside workflows. Escalation was documented. Safe stops were rewarded. Quality overrides were normalized. Coaching reinforced judgment, not just speed.

Culture stopped being implicit.

It became operational.

Operational Reality Check
If culture is not designed,
it will be designed by pressure.


The Eleventh Rule of Running a Support Experience Center

Culture is the final constraint.

You can fix staffing.
You can design workflows.
You can govern automation.
You can instrument the system.

But culture determines how all of it behaves when conditions are imperfect.

Jeff stopped asking how to scale tools.

He asked how to scale judgment.

And once culture became intentional, the experience center reached its most stable form.

Not because nothing went wrong.

But because when it did, the system responded the right way.


Jeff finally understood the system in full.

Staffing was not capacity.
Onboarding was not growth.
Metrics were not control.
Automation was not leverage.
Governance was not approval.
Culture bound it all together.

Each part only worked when it reinforced the others.

And that was the problem.

Most leaders encountered these lessons one at a time, years apart, usually in response to failure. They fixed symptoms without ever seeing the system they were operating inside.

Jeff realized something important.

The real value of this journey was not any single insight.

It was seeing how they connected.

Before moving forward, Jeff stopped.

Not to add another tool.
Not to launch another initiative.
Not to redesign again.

He stepped back to review what the system had taught him.

Because if others were going to run this experience center well, they needed more than stories.

They needed clarity.


When you are ready, we move into Part 12, a synthesis of Parts 1 to 11 with the main learning points and the concrete actions leaders can execute immediately.


I use AI for editing, so if you see what looks like AI, it just might be. You can visit my AI Prompt Article or the Professional GPT Playbook to put AI to work for you.