The Contact Centre: Where Much of the Organisation Converges

On paradoxes, interpretation and agency

“When different parts of the organisation respond rationally to different versions of the work.”

Organisational change is often discussed through strategy, transformation programmes and technology. It also becomes visible in smaller ways: recurring decisions, unexpected performance patterns or situations that no longer quite fit the assumptions through which they are being interpreted.

Customer-facing work offers an unusually direct view into this.

The contact centre is one of the places where much of the organisation converges in practice. Policy, systems, measurement, management and individual judgement come together in the work and eventually have to survive contact with the customer. Where they fit together, there may be little to notice. Where they pull in different directions, the interaction can make the tension surprisingly visible.

The five situations in this article come from that environment. They are deliberately specific, but the underlying tensions can appear just as readily in sales, operations, management and other parts of an organisation.

The first challenge is recognising them. The second is deciding what to do once they have been recognised.

Work cannot continually stop to reconsider every process, measure or assumption through which it gets done. Something may therefore be noticed repeatedly without yet providing enough reason to act, or without sitting within the remit of the person noticing it. Later, changing circumstances can make the same observation newly relevant.

This creates a practical question at every level.

How do we become better at recognising when something that looks like a local performance problem may be telling us something more, without turning every exception into a reason to question the entire operating model?

The tensions in the five situations that follow are difficult because neither side can simply be removed. Control remains necessary while judgement becomes more important. Measurement remains necessary while some forms of value resist easy measurement. Efficiency matters while adaptation requires capacity that may initially look inefficient.

They are less choices between competing priorities than requirements that increasingly have to be held at the same time.

Control

An advisor is encouraged to take ownership of the customer’s situation. The case falls slightly outside the usual pattern, and the advisor can see a reasonable way forward. Before acting, they check with a manager. The manager confirms the same decision the advisor was considering. The customer gets the answer, but only after the decision has travelled upwards and back again.

Are we asking for greater autonomy while designing for greater control?

Autonomy and control increasingly coexist as requirements of the same work.

Greater judgement and local decision-making become important where circumstances cannot be fully specified in advance. At the same time, regulation and accountability create legitimate demands for standardisation and auditable decisions.

The tension appears when autonomy is expected as an outcome while the work system reduces control over method, decision or escalation. Responsibility can move closer to the work while authority remains elsewhere. Waiting for permission can then become a rational response to an environment that simultaneously asks for ownership.

The same tension exists between judgement and standardisation. Standards establish consistency and protect necessary boundaries. Their application to particular circumstances can still require interpretation. The capability therefore sits partly in recognising where the standard applies directly, where interpretation is required and where authority ends.

An organisation can increase its expectation of judgement while continuing to organise work around an inherited assumption that variation primarily represents inconsistency and should progressively be engineered out.

The paradox sits there. The work can require greater autonomy at precisely the moment its surrounding systems are becoming more capable of directing, monitoring and constraining how that autonomy is exercised.

Measurement

A customer contacts the centre with what appears to be a straightforward request. The advisor spends a little longer establishing what has happened and discovers a second issue that would otherwise have remained unresolved. The interaction takes longer. The customer does not need to contact the organisation again.

Are we making performance more visible while making some of its value harder to see?

Measurement creates organisational visibility. It allows dispersed activity to become comparable and provides a basis for accountability.

It also creates a selective field of visibility.

What is measured becomes easier to recognise. What sits outside the measure can become progressively harder to represent, even where it contributes materially to the outcome the measure is intended to support.

Measures are also reactive. Once attached to targets, evaluation or reward, they begin to influence the activity they describe. Performance adapts to its representation.

This creates a particular difficulty where value lies partly in judgement. Anticipation and well-timed intervention do not always leave an observable event behind. Their contribution can consist precisely in something that subsequently does not happen.

The organisation can improve its ability to measure performance while narrowing the field through which performance is understood.

The paradox is that increasing visibility within the measurement system can coexist with decreasing visibility of whatever the system has not learned to represent.

Efficiency

A contact-centre manager starts the day with staffing, demand and service levels already requiring attention. There are performance conversations to hold and another change being implemented. By the end of the day, each immediate issue has been dealt with. What has been harder to make room for is whether several of those issues are beginning to say the same thing.

Are we getting better at today’s work faster than we are learning what tomorrow’s work requires?

Efficiency concentrates resources on what produces value now. Learning requires some capacity to examine whether the assumptions behind current performance remain useful.

Those demands do not always move together.

Some apparently unused capacity performs an adaptive function. It allows investigation and interpretation. Adaptive capacity can look identical to waste before its purpose is known.

The same tension appears in organisational learning. Established routines tend to produce more certain and measurable returns than exploration. Successful practices therefore attract further use and investment. Their success becomes part of the evidence for continuing them.

Experience can strengthen an existing interpretation rather than revise it.

This creates the possibility of a competency trap. The organisation learns, improves and becomes more capable within a particular model. Increasing competence can deepen commitment to that model at the same time as the environment on which it was based begins to change.

An organisation can become increasingly competent at a declining model.

There need be no failure to learn for this to happen. Learning itself can reinforce the path already taken. Efficiency can reduce the capacity available to question it, while successful execution continues to provide evidence that the path works.

The paradox is that improving today’s performance can strengthen the very conditions that make tomorrow’s change harder to recognise.

Remit

A team leader notices that the same type of customer situation keeps returning. Each case can be resolved, so each one is. Over time it becomes familiar operationally: something to handle and close. Further up, the same pattern may eventually appear as increased contact, cost or declining performance against a measure.

Are those closest to change also those with the least remit to interpret what it means?

Operational proximity and organisational authority provide different forms of visibility.

Those closest to the work encounter variation in its contextual form. Their responsibility is commonly organised around delivery within the existing operating model. Wider interpretation may sit beyond the formal remit through which their performance is understood.

Broader authority tends to sit further from the events through which change first becomes visible.

Information therefore has to travel.

In doing so, it is selected and transformed. Narrative becomes category, category becomes indicator, and indicator becomes a claim about performance.

That translation is necessary. It allows dispersed activity to be compared and finite attention directed towards what appears significant. Something is also lost in that translation.

A recurring operational pattern may consequently be widely known without becoming recognised as a question about the operating model. Local responsibility encourages resolution. Senior responsibility requires abstraction. Between the two sits the problem of deciding when repeated local evidence has acquired wider meaning.

The resulting gap concerns more than communication. It concerns legitimacy and remit. Proximity does not automatically confer authority to make a strategic claim, while authority does not guarantee access to the contextual evidence from which that claim might emerge.

An organisation can encounter something eventually as a strategic surprise even where its component signals were widely known.

The paradox sits between proximity and authority: those best placed to see that something is changing may not be those expected to decide what that change means.

Development

An experienced advisor is identified as needing development in an aspect of customer handling. During coaching, the same advisor demonstrates that they can perform it well. They understand the principle and reapply it successfully. Back in normal work, the behaviour remains inconsistent.

Are we developing one version of the role while the organisation teaches another?

Formal development is one source of learning inside an organisation. The work itself is another.

The operating environment functions as a curriculum. Metrics, systems, decision rights and managerial responses repeatedly communicate which behaviours are viable, valued and safe.

Formal development can increase a capability without determining how consistently that capability appears in practice.

This distinction separates capability acquisition from capability use. Ability, motivation and opportunity make different contributions to performance. Transfer depends partly on whether the work provides the conditions in which newly developed capability can be exercised and reinforced.

The tension becomes sharper as roles require greater judgement. Development may encourage interpretation and ownership while the operating environment continues to reward adherence or permission-seeking.

The organisation is then teaching through two curricula.

Formal development may say: take ownership. The workflow may teach: escalate.

Development may say: understand before solving. The measure may teach: keep the interaction short.

Development may say: use judgement. The quality process may teach: deviation requires explanation.

Nobody needs to be contradicting the development deliberately. The operating curriculum simply has the advantage of repetition. It is encountered every day, under real conditions, attached to actual measures and consequences.

The paradox is that an organisation can successfully develop the capabilities it says it needs while simultaneously maintaining conditions that teach when those capabilities should remain unused.

The resulting performance gap may therefore contain different questions. Capability may still need to be built. Existing capability may require stronger transfer. The capability may already be present while the conditions surrounding its use point behaviour elsewhere.

Development can reveal which of those explanations is becoming more plausible.

Different Versions of the Work

None of these paradoxes depends on an organisation standing still. They can persist while substantial change is taking place.

What often moves at a different speed are the assumptions underneath the work.

Control can still reflect one understanding of the role while development is preparing for another. Measurement can make one form of performance increasingly visible while changing customer behaviour makes another more consequential. Efficiency can strengthen established routines while reducing the capacity through which their continued relevance is questioned. Operational evidence can be widely available while the remit to interpret its wider meaning sits elsewhere.

Different parts of the organisation can therefore be responding rationally to different versions of the work.

Each may make sense on its own. The tension becomes visible when they have to operate together.

When the Response Becomes the Diagnosis

A performance problem comes into a meeting with a proposed response: more coaching, tighter control, a process change, greater efficiency.

Before moving to the action, might it be worth making the explanation visible?

What would have to be true for this to be the right response?

If advisors are escalating too much and the proposed response is confidence coaching, what evidence says confidence is producing the escalation?

If handling times are increasing and the proposed response is greater efficiency, what evidence says the additional time represents waste?

If development has worked but the behaviour remains inconsistent, what evidence says further reinforcement is the constraint?

You still need to act. The additional step is to make the interpretation behind the action discussable.

Then there is what happens when the problem returns.

A recurring problem often produces more of the original response. More coaching. Tighter control. Another process change.

Recurrence can tell you something else.

If we have acted on this explanation and the pattern remains, what explanation have we been preserving?

The intervention may have been appropriate. The capability gap may have been real. The control may have been necessary. Something else may now be visible precisely because the first intervention worked.

The next question is where that recurrence can go.

A team leader who has resolved the same customer situation seven times may not yet be able to show that it represents a strategic problem. There may still be value in looking across the cases.

It may be enough to say:

We have resolved this seven times. I don’t know whether it means anything beyond these cases, but the recurrence is now worth comparing.

That gives recurrence a route beyond repeated resolution without requiring every exception to be escalated.

When the issue does reach a management meeting, another conversation about “challenging our assumptions” may still leave the underlying interpretation untouched.

It may be more useful to look at what the meeting actually does.

Does the same dashboard define the problem? Do the existing categories determine which explanation is available?

Can somebody question the explanation without already having an alternative solution?

Can the meeting finish with something that needs to be understood, rather than only something that needs to be done?

Time in the diary is not enough. The question is whether anything can happen in that time that could change how the problem is understood.

There is an accountability question here too.

Actions normally acquire owners very quickly.

Who owns the diagnosis?

More precisely: when the action has been completed and the pattern returns, who is responsible for asking whether the explanation that produced the action still holds?

That is accountability for the interpretation as well as the action.

Attention Moves

Recognising a pattern does not mean that the person closest to it can act on it, or that the organisation is ready to consider what it might mean.

Organisations do not reconsider everything all the time. That would be impossible.

Attention moves.

A question that has little organisational traction today can become highly relevant six months later. The underlying observation may barely have changed. What has changed is the context around it.

A shift in performance can alter what attracts attention. A strategic priority can make an old observation newly relevant. Sometimes an opening appears because a different question has begun to be asked.

The issue has not necessarily become more true.

The context has become more receptive to what the issue might mean.

This changes what attentiveness can mean when nothing can be changed immediately.

We tend to associate agency with action.

I saw something, therefore I should do something.

But agency sometimes consists of continuing to notice.

There may be no compelling case for intervention yet. The observation may sit outside somebody’s remit, or the existing approach may still be working perfectly well. The useful capability is retaining enough attention to recognise the observation again when the context changes.

An issue does not acquire wider attention simply because somebody has noticed it. Someone still has to judge whether it has significance beyond the immediate situation, whether to raise it and whether the context is receptive.

That is issue selling.

The phrase sounds slightly more political than the phenomenon needs to be. Sometimes it is simply a manager saying:

We’ve been seeing this for a while. I wasn’t sure it meant very much on its own, but given what we’re now seeing, I think it’s worth looking at again.

Timing is part of the judgement.

An observation raised repeatedly when there is little capacity or reason to engage with it can begin to feel futile. If that experience repeats, the conclusion may gradually shift from this is not the moment towards there is no point raising this.

Those are very different conclusions.

The first preserves agency. The second can contribute to learned pessimism: previous experience begins to shape expectations about whether future action is likely to make any difference.

Knowing What to Do With What You Notice

This brings development back into the picture at a different level.

An organisation can deliberately develop the capacity to notice what the work is revealing. Noticing alone is insufficient.

The underlying reflexes include separating an observation from the first explanation attached to it, recognising when something is worth retaining rather than immediately pursuing, and noticing when circumstances have changed enough to reopen it.

Those are developable capabilities.

Coaching and development can provide opportunities to work with them, particularly when reflection is based on actual situations rather than abstract cases. The work itself provides the material: what was noticed, what interpretation followed, what happened when the issue was raised, and what changed afterwards.

This also gives agency a more practical meaning.

Someone can become better at judging what is within their influence now, what needs to be retained, and when a changing context creates another opportunity to act.

A team leader can question the explanation attached to a recurring problem. Someone in L&D can notice when development is beginning to reflect an older version of the work. A sales manager can recognise that a process still works while the conditions around its success are beginning to change.

None of that requires authority to redesign the organisation.

It requires enough attentiveness to recognise when an explanation no longer quite fits, enough judgement not to treat every discrepancy as significant, and enough awareness of context to recognise when something previously observed has become worth raising again.

What Deserves Another Look

Customer-facing work will continue to produce local problems that need local answers. Most will be exactly that.

Some will repeat. Some will stop fitting the explanation previously attached to them. Others will acquire different significance as the work around them changes.

Not every one of them can be investigated. Nor does everyone who notices something have the authority to change what produces it.

There is still considerable room between noticing something and changing the organisation.

That space can contain comparison and questioning. It can also contain memory, judgement and timing.

Those capabilities can be developed deliberately. They can also be practised without waiting for a formal effort to develop them.

The five paradoxes are therefore less a list of problems to solve than places where it may be worth paying attention.

What they eventually reveal depends partly on whether somebody is still paying attention when the context changes.

Explore Leadership & People Development

The questions explored here rarely lead to the same response in every context. Our work with leaders starts by examining what is actually shaping performance, where a recurring pattern sits, and what can realistically be changed. Leadership mentoring, performance development and other pathways then provide different ways of turning that understanding into practical work.