A new competency opens
The course moved into its second HRD Corp competency: CT02 — Conduct Training Needs Analysis. The module cover carries a quote from psychologist Philip J. Runkel that frames everything: "Action comes about if and only if we find a discrepancy between what we are experiencing and what we want to experience." No discrepancy, no action. No gap, no training. The learning outcomes: define TNA, explain its rationale, describe TNA at the three levels, and apply TNA methods. But the trainer opened with a sharper question: why did you send Faiz for training? The honest answer in most companies — "sebab I rasa dia perlukan" — because I feel he needs it. Her verdict: tak boleh main rasa-rasa. "Kalau rasa-rasa, agak-agak, ni semua bukan saintifik punya approach." Plenty of organisations send people to training with no tool behind the decision. This module is the tool.
Competency: three things that must arrive together
Before you can find a gap, you need the thing you are measuring: competency — the knowledge, skills and attitude of an individual to perform adequately in a job to the standard expected in the workplace. The trainer's stress was on together — "mesti datang together." Her friend's dark-humour illustration: you are wheeled into the operating theatre and the surgeon arrives with only two fingers. All the knowledge in the world, and you would still crawl off the table. Knowledge without skills is a lecture; skills without attitude is a liability; the competent professional has all three. And the follow-through that leads straight to TNA: how do I know you have the knowledge? Test. The skills? Test. The attitude? Test. "So to test, I need a tool." That tool-shaped hole in most training decisions is exactly what a needs analysis fills.
The definition, and the standard problem
Training Needs Analysis is a systematic process of identifying the gap between actual and desired level of performance and its related training needs. The workbook's picture: standard or preferred performance at 90%, present actual performance at 75% — the shaded band between them is the gap, and the gap is the training need. It is Carl Rogers' real self and ideal self from this morning, translated into industry percentages. But the definition hides a prerequisite the trainer hammered: to measure a person, you must know the standard you are measuring against. Construction has defined competency levels; a playground installation has safety criteria per age group; a production line can define its standard as 100% reject-free. "Kalau tak ada, kena buat lah" — if no standard exists, your first job is to write one, because without it every assessment is rasa-rasa wearing a clipboard.
Training solution or non-training solution
The most commercially honest part of the module: not every gap is a training gap. Ask what is missing. "Adakah dia missing the knowledge, ataupun the skills, ataupun the attitude? Kalau dia missing ini sahaja, barulah saya boleh design training." If the problem is the machine — no training needed. The environment — no training. The process too long, or a missing step — no training; fix the process. "Because you are not dealing with the root cause of the performance problem." Training exists to change the person, because the person performs. Send someone to a course to fix an infrastructure problem and the only output is, in her word, noise. The six-point rationale for TNA in the workbook wraps this up: determine the gap, identify root causes of poor performance, determine whether there is a training requirement at all, identify the content and scope of training, provide baseline data, and gain participant and organisational support.
Case Study
the complaint that wasn't a training problem
I ran the training/non-training filter over a real Mana Mana pain point: guest complaints about slow check-ins at one property, which had already produced the classic reflex — "the front desk needs customer-service training." First, the standard. We had never written one. Drafting it took an afternoon: check-in completed within eight minutes of guest arrival, deposit explained correctly, 90% of guests rating arrival experience four stars or better. Without that, the complaint was unmeasurable mood. Then the gap analysis, KSA plus everything-else. Knowledge: do staff know the check-in flow? Tested with five scenario questions — yes, near perfect. Skills: can they execute? Observed — yes, when the system cooperates. Attitude: were they unwilling? No — they were apologising to guests while waiting for the property-management system to load. The bottleneck was a PMS that takes ninety seconds per booking lookup on the property's aging PC, plus an ID-scan step that duplicates what the booking platform already collected. Conclusion: an 80% non-training problem (replace the terminal, remove the duplicate step) with a 20% training component (the deposit explanation genuinely varied by staff member). The reflex answer would have bought a customer-service workshop for a hardware problem — and afterwards the complaints would have continued, with the added insult that "we already trained them." Runkel's discrepancy was real; the cause was not where the reflex pointed. That is the entire argument for doing the analysis before designing anything.
Reflections
CT02 connects backwards beautifully: the whistle cartoon said delivery isn't learning; Rogers said training closes a gap; ADDIE said analyse first. TNA is where all three become procedure. The sentence I am keeping from today: no standard, no measurement; no measurement, no gap; no gap, no training — just rasa-rasa and a budget line that cannot defend itself.