The Experience Center Operating Model

Why This Series Exists

Over more than two and a half decades in support and services leadership roles, I have learned what actually makes service organizations work, and what quietly causes them to fail. I started my career at sixteen in technical support. The tools, channels, and technology have changed dramatically since then, but the foundational elements have not. Pressure still distorts behavior. Metrics still shape decisions. And systems still teach people how to act, often without leaders realizing it. I touch on this evolution briefly in The Contact Center Is Gone, but the lessons began long before that.

The real shift for me came when I moved from individual contributor to first time leader. As an individual contributor, my world was narrow by necessity. I focused on my own performance, my metrics, my targets, and my incentives. Like many, I believed that hitting numbers meant success. That perspective changed when I met Tom Farrell, who introduced me to the business math behind service delivery, not as theory, but as reality. Service levels. Shrinkage. Capacity. Tradeoffs. His no nonsense approach, and his constant reminders that math is pure and time is shrinkage, became my undergraduate and advanced education in how service organizations actually function.

As my career progressed and I worked alongside other exceptional leaders, that foundation became what I consider my real graduate education, not in frameworks or certifications, but in lived experience. I learned how systems behave under pressure, how good intentions break down, and how leaders unintentionally create the outcomes they later try to fix. This operating model is not theoretical. It is built from experience, reinforced by education, and refined through failure.

In the pages that follow, you will meet Jeff. Jeff is fictional, but his situations are not. If his challenges feel familiar, it is because most leaders pass through the same moments, often without realizing what is happening until the system pushes back. This series exists to make those moments visible, to show where leaders commonly stumble, why those failures occur, and how to design experience centers that hold up when pressure, scale, and change arrive.

How modern support experience centers actually scale, across people, automation, governance, and culture.

This series documents what it really takes to run a support experience center at scale.
Not org charts. Not vendor decks. Not dashboards that create confidence without control.

These posts focus on the operating mechanics that determine whether experience holds under pressure, or quietly collapses.

How to Read This Series

Path 1: Read the story

Follow Jeff’s journey from Part 1 through Part 15 in order.

Path 2: Read the system

Start with the synthesis post and explore forward or backward as needed.

→ Start with Part 12: Running the System — What Actually Matters

Series Map

The Core Belief

Support experience centers do not fail because people make mistakes.

They fail because systems quietly teach people how to behave under pressure.

This series is about designing systems that behave correctly even when leaders are not in the room.

Running a support experience center is not about efficiency.

It is about judgment at scale.