Train-the-Trainer in Contact Centres: Developing the Judgement Behind Coaching

In contact centres, experts, team leaders and managers are often expected to coach.

Their development tends to include familiar territory: giving feedback, handling difficult coaching conversations, addressing performance issues, setting objectives and structuring a coaching conversation.

There is a genuine need for this. Strong operational performance or extensive customer knowledge does not automatically develop the ability to coach somebody else.

But what else might coach development and train-the-trainer programmes need to build?

Before a coaching conversation begins, somebody has already made several decisions. They have noticed something, interpreted it, decided that it deserves attention and concluded that coaching is an appropriate response.

The quality of those decisions shapes what happens next.

1. Developing diagnostic judgement

An expert or team leader observes an interaction. Something did not work.

What exactly are they looking at?

A knowledge gap? A skill that has not yet developed? Something the advisor can do but did not do in this situation? An incorrect assumption? An organisational constraint? Lack of decision authority? Or an appropriate response to an unusually difficult situation?

Several explanations may also be true at the same time.

The capability lies in forming a working hypothesis before reaching for a coaching intervention.

What appears to explain the performance? What else could explain it? What would need to be explored with the advisor before deciding?

A well-conducted coaching conversation directed at the wrong problem may change very little. The same performance issue can then return, generating another conversation around something that was never primarily a coaching issue.

There is also an experience on the other side of that conversation. An advisor can repeatedly receive development around something that does not feel like the difficulty they are actually encountering. The conversation happens, actions are agreed, yet the situation they are struggling with remains.

Over time, that can affect whether coaching feels useful, and whether advisors feel they are developing at the pace of an environment that is changing around them. That is rarely something said out loud.

One way to develop diagnostic judgement is to give experts and team leaders the same interaction and ask them to form two or three plausible explanations before deciding what they would coach.

The discussion moves from “How would you coach this?” to “What makes you think coaching is the appropriate response, and what would you need to know first?”

2. Learning to observe without prematurely interpreting

Two team leaders listen to the same call.

One says:

“She lacks confidence.”

Another says:

“When the customer challenged the answer, she stopped asking questions and began repeating policy.”

The second is observable. The first is an interpretation.

Learning to distinguish observation → interpretation → hypothesis → exploration creates a very different coaching conversation.

There is another layer. Even observation involves selection.

Why did that particular moment attract attention?

Another listener might have noticed that the advisor could not find the relevant information quickly enough, that the customer introduced something important earlier in the conversation, or that the policy itself was difficult to explain.

Disciplined observation includes becoming curious about what we noticed, what we did not notice and why one observation became significant.

Interpretations also have a habit of travelling.

Once “lacks confidence” becomes the explanation, it can follow the advisor into later coaching and quality discussions. It can influence which situations they are considered ready for and how subsequent behaviour is interpreted.

It can also change what gets brought forward. If a difficult moment quickly becomes a conclusion about the person, there is less reason to volunteer the next one.

A more precise observation keeps the conversation closer to the work and keeps more possibilities open for longer.

Several experts or team leaders can practise this by listening to the same short interaction independently and comparing what each noticed before discussing what they think it means.

The differences themselves become useful development material.

3. Knowing what not to coach

One interaction might contain seven things that could have been done differently.

Which one deserves attention?

The largest gap on a quality form may not be the issue with the greatest developmental leverage. Something may be incidental. Something may already be improving. Something may belong to another system. Something may simply be better left alone.

In a contact centre, that choice has a very practical edge. Coaching capacity is finite. Choosing one issue means giving less attention to another.

So one useful development exercise is deliberately restrictive.

Take an interaction containing several legitimate improvement opportunities and allow the coach to choose only one.

Why this one? Why now? What would you leave alone? What would make you choose differently?

That is harder than working down from the lowest score on a quality form. It develops the selectivity required when there will always be more potential coaching points than useful coaching conversations.

4. Calibrating judgement, not merely scores

Calibration in contact centres often involves several evaluators assessing the same interaction and aligning their scoring standards.

But the reasoning behind those scores can also be calibrated.

Give three team leaders the same complex customer conversation.

What did each notice? What evidence did they use? What do they think the advisor was responding to? What would each choose to explore?

If their interpretations differ, agreement does not automatically have to be the objective.

There will be areas where consistency matters. There will also be situations where different interpretations are reasonable.

Perhaps one team leader noticed a missed customer cue. Another saw uncertainty about decision authority. A third interpreted the same behaviour as the advisor trying to manage an unusually difficult interaction.

Those differences do not remain inside the calibration room.

Similar interactions can lead to different coaching priorities, different messages and eventually different expectations across teams. From the advisor's perspective, development can begin to depend as much on who is listening as on what happened in the interaction.

Calibration offers an opportunity to make those differences visible before they quietly become different standards in practice.

Existing calibration sessions can simply run one question longer. Once the score is agreed, ask:

What would you actually do with what you have just seen, and why?

5. Interpreting signals in an AI-assisted environment

AI increasingly allows contact centres to examine far larger volumes of customer interactions and identify patterns that would previously have been difficult to see.

That gives experts, team leaders and managers more evidence.

It also creates a different problem: more signals competing for attention.

Suppose a system identifies recurring interruptions, unusual silence, repeated policy explanations or a behaviour associated with poorer outcomes.

Is that an observation? A recurring pattern? Evidence supporting a hypothesis? Or already something that deserves coaching attention?

Technology can surface far more possible signals than a team leader could ever investigate individually.

The question increasingly concerns what status to give them.

There is another risk if the distinction disappears. If a flagged behaviour moves directly into coaching, the understandable response is to avoid the behaviour that generates the flag. A pause may become something to shorten, an interruption something to eliminate, even where the context made it appropriate.

The signal improves. The interaction may not.

The team leader's role can narrow as well. Passing on what a system has identified is different from exercising judgement about what the evidence means. “The system flagged it” can gradually become the reason for the conversation.

The observation → interpretation → hypothesis → exploration sequence from earlier is useful here. An AI-generated signal enters the process as evidence to examine rather than as a conclusion about what the advisor needs to develop.

This can be practised directly. Present a technology-generated pattern and ask what can reasonably be concluded from it, what remains unknown and what would need to be explored before deciding whether any intervention is warranted.

6. Distinguishing advisor development from system feedback

Suppose five advisors repeatedly struggle at the same point in customer conversations.

Do we coach five advisors?

Or do we ask why five advisors are producing the same response?

Perhaps it is capability. But perhaps the policy is ambiguous, decision rights are unclear, the knowledge system makes the answer difficult to establish, customer expectations are being created elsewhere, or operational pressure is changing how advisors behave.

Recognising the pattern is only the beginning.

How much evidence is enough? When does a recurring coaching observation become feedback about process, policy, knowledge or decision rights? Where does that information go? And what happens when the team leader can see the constraint but has no authority to change it?

If the pattern remains inside individual coaching conversations, the operation keeps responding to the same signal one advisor at a time.

Team leaders experience something in that process too. They can see a recurring constraint, raise it and continue to encounter it. Eventually, staying within what they can influence directly becomes the more workable response.

That shift can be difficult to see. Coaching continues. Quality processes continue. The immediate work still gets done. Yet the distance between what team leaders are seeing and what travels further into the organisation can gradually widen.

Looking across coaching conversations creates another possibility. Recurring themes become information about where the work itself is becoming difficult.

Every repeated issue will have its own explanation. Repetition gives us a reason to examine where that explanation sits.

And once that happens, experts, team leaders and managers become more than coaches of individual performance.

They become sensors into the operating system.

Developing the judgement behind the intervention

None of this requires every coaching decision to become a lengthy investigation.

Contact centres rarely offer that luxury.

The point is that development can practise more than what happens once the coaching conversation begins.

Before that conversation, somebody has already decided what they saw, what they think it means, whether it deserves attention and where the issue appears to sit.

Advisors experience the consequences of those decisions in the development they receive, and in whether they feel they are growing. Experts and team leaders experience them in the situations they repeatedly encounter and in what happens to the information they raise.

Those judgements can themselves become part of development.

Perhaps that is the deeper opportunity for train-the-trainer development in contact centres: developing the ability to examine the judgement behind an intervention as carefully as the ability to conduct the conversation that follows.

Beyond Coaching Technique

Developing effective coaches involves more than strengthening their conversation skills. It also means developing how they observe performance, interpret what they see and decide where their intervention can create the greatest value.

Our Facilitation & Training Capability work supports trainers, coaches and subject-matter experts in developing these wider capabilities alongside their existing expertise.