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.
Nesting was supposed to be the easy part.
The hardest work was done. Hiring was complete. Training had finished on schedule. New hires were finally close to the floor, close to real customers, close to becoming productive.
That was the expectation.
The reality looked different.
By the second week of nesting, senior agents were exhausted. Managers were stretched thin. Quality reviews lagged. Handle times crept up. Everyone was busy, and no one felt in control.
Jeff recognized the pattern immediately.
This was not a failure of effort.
It was a failure of design.
Nesting Multiplies Load, It Does Not Share It
Most experience centers treat nesting as a transition.
A short bridge between training and full production. A time to shadow, observe, and slowly take on work.
But nesting does not spread work evenly.
It concentrates it.
The most capable agents are pulled into support roles. Coaches spend more time preventing mistakes than developing skills. Managers intervene more often, but lead less. Every interaction takes longer, even when things go well.
Capacity shrinks while expectations remain unchanged.
Leadership Call Out
Nesting increases demand on your strongest people.
If you do not explicitly model that load, the system absorbs it through burnout and quality drift.
Quality Drifts Before Anyone Notices
The first signs were subtle.
Scripts were followed, but intent was missed. Policies were applied, but context was lost. Customers did not complain loudly. They disengaged quietly.
Quality scores did not immediately collapse.
They lagged.
By the time leadership saw the dip, the behavior had already spread. New hires were learning from overwhelmed coaches. Shortcuts became norms. Rework increased.
Jeff realized something uncomfortable.
Nesting does not just teach new hires how to work.
It teaches them what the system tolerates.
Operational Reality Check
Quality does not fail during nesting.
It drifts, slowly and invisibly, until it becomes the new baseline.
Coaching Becomes Reactive
Coaching plans existed.
They were thoughtful. Well intentioned. Built around development, not correction.
None of that survived the pace of nesting.
Coaching sessions turned into fire drills. Feedback focused on what went wrong, not why. Patterns were noticed late, if at all. Managers spent their time correcting errors instead of shaping behavior.
The system moved faster than the coaching loop could keep up.
Jeff saw the contradiction clearly.
They were investing heavily in onboarding, while quietly starving the very mechanism that made onboarding successful.
What Leaders Often Miss
Nesting consumes coaching capacity at the exact moment it is most needed.
Without protected coaching time, development becomes accidental.
Nesting Without Structure Is Just Exposure
The assumption had been simple.
Put new hires next to experienced people and learning will happen.
But exposure is not structure.
Without clear guardrails, nesting becomes inconsistent. Some agents receive great guidance. Others pick up habits based on who happens to be nearby. Quality depends more on proximity than design.
Jeff pushed the team to be honest.
Where were the explicit behaviors new hires were expected to master during nesting. How those behaviors were reinforced. How deviations were detected early. How coaches knew where to focus their limited time.
The answers were scattered.
Good intentions were everywhere.
Structure was not.
Leadership Call Out
Nesting without structure does not scale learning.
It scales variability.
The Fifth Rule of Running a Support Experience Center
Nesting is not a transition phase.
It is a pressure test of your entire system.
If staffing is tight, nesting exposes it.
If coaching is fragile, nesting breaks it.
If quality standards are unclear, nesting rewrites them.
Jeff did not try to make nesting easier.
He made it explicit.
Protected coaching capacity. Clear behavioral goals. Smaller classes. Slower release into production. Honest acceptance that experience would dip unless leadership planned for it.
The result was not perfection.
It was control.
And once the system was under control, Jeff could finally address the next gap.
Metrics.
Not dashboards.
Metrics that actually drove behavior.
When you are ready, we can move into Part 6, where numbers stop being informative and start being dangerous if they are not designed carefully.