The easiest way to understand a training needs analysis (TNA) is to watch one happen. So here is a single case from start to finish. The company is an illustrative broadband provider with a service centre in Guwahati. Forty agents handle calls and chats from customers across the north-east. The operations head walks into the HR office and says: “First-contact resolution has dropped. Customers are calling back. Please arrange a customer-handling workshop for the whole team.”

The request already contains a solution. A TNA is the discipline of not accepting it until the evidence is in.

Step 1: turn the complaint into a measurable gap

“Dropped” needs a number. The reporting system shows first-contact resolution (FCR) at 62% against a target of 75%. So there is a 13-point gap. That is the performance problem. Only now do we ask what is behind it, and whether any of it is a gap in knowledge or skill, since training cures nothing else.

Textbooks describe TNA at three levels: the organisation (what does the business need, and what is it changing?), the task (what must be done well in this job?), and the person (who cannot do it, and why?). In a real exercise you move between them, but this case happens to begin at the organisation level, because the business has launched two new plan types this quarter.

Step 2: find out why customers call back

The HR partner asks quality analysts to listen to a sample of 200 recent calls and tag each one. Of the 200, 48 are repeat contacts on an issue already handled once. That is 24%, which fits with an FCR problem. The analysts then code the reason for the repeat in each of the 48.

Reason for repeat callCountShare of 48
Agent gave wrong information on new plan changes2144%
Process not completed (ticket left open, callback not scheduled)1429%
System or billing error outside the agent’s control817%
Customer unhappy with tone, so called again to escalate510%

21 + 14 + 8 + 5 = 48, so the coding is complete. (Percentages are rounded, so they add to 100 only roughly.)

Step 3: sort causes into “training will fix it” and “it will not”

This is the step people skip, and it is the one that protects the training budget. Go row by row.

Wrong information on new plans. A knowledge gap. Strongly a training matter, though probably a short product update and a quick reference card, not a workshop on empathy. The agents are not bad at customer handling; they were not briefed well on a launch.

Process not completed. Ask first: do they know the steps, or do they skip them? An observation session shows that agents know the process but the ticket screen needs seven clicks to schedule a callback, and under call-handling-time pressure they drop it. That is a tool and incentive problem. A course would be wasted.

System and billing errors. Nothing to do with the agents; send to IT and finance with the evidence.

Tone. Five calls from forty agents suggests it is concentrated in a few people. Coaching those individuals, using call recordings, is better than a team-wide programme.

Step 4: check whether everyone needs it

The 21 wrong-information calls, when traced to agents, come from 11 of the 40. Seven of those 11 joined within the last four months, before the plan documentation was updated, and the other four were on leave during the launch briefing. So the audience for the product update is not “the whole team”. It is those who missed the briefing; everyone else can take a quick refresher at most. Cutting 40 down to 11 changes the cost and also the message: nobody is told that the whole team is deficient.

Step 5: write the plan and say how you will know it worked

  • Product update session (90 minutes) plus a one-page plan comparison for the 11 agents, with a short knowledge check afterwards.
  • Process fix: ask the tools team to cut the callback scheduling to two clicks. Not a training item, but recorded in the TNA report so it does not vanish.
  • Individual call coaching for the handful of agents named in tone-related repeats.
  • Measure: repeat contacts coded “wrong information” in the next 200-call sample, and FCR after six weeks.

If, after six weeks, wrong-information repeats have fallen from 21 to near single digits but FCR has moved only a few points, that is not a failure of the training. It says the remaining gap lives in the process and the system, which is exactly what the analysis predicted.

What this example shows about the method

The ops head asked for a workshop and got a product update for eleven people, a process fix, and some coaching. Nobody sat through a day of training they did not need. And a TNA is allowed to conclude that the right answer is “not training”. In practice, a good share of requests end that way, which is why the analysis is cheaper than it looks.

Figures and names in the examples are illustrative.

Leave a Reply

Trending