Training needs analysis: a practical guide for HR teams

A training needs analysis (TNA) is a structured review of where people's current knowledge, skills and behaviors fall short of what the organization needs, and of whether training is the right way to close that gap. It looks at three levels, the organization, the role and the individual, and ends with a prioritized list of learning needs that leaders have agreed to fund.

Done well, a TNA keeps the training budget focused on problems that training can actually solve. This guide covers the three levels of analysis, the main data-collection methods and how they compare, a seven-step process you can follow, and how to prioritize needs and write the TNA report.

What is a training needs analysis?

A training needs analysis answers three questions in order. What does the organization need people to be able to do? What can they do today? And where the two differ, is training the right response, or would something else, such as clearer processes, better tools or a hiring decision, work better?

That third question is what separates a TNA from a list of course requests. Not every performance problem is a skills problem. A sales team may miss targets because pricing is uncompetitive, not because the team lacks negotiation skills. A TNA that skips this question can send people on courses that do not address the real cause.

Where the idea comes from

The classic model comes from McGehee and Thayer's Training in Business and Industry (1961), which described needs analysis at three levels: the organization, the operations or tasks people perform, and the individual. Most later models, including the approach in this guide, still follow that structure. Salas, Tannenbaum, Kraiger and Smith-Jentsch's (2012) review of training research also places needs analysis at the start of designing effective training, before decisions about content or delivery.

Training needs analysis or learning needs analysis?

You will also see the term learning needs analysis (LNA). The CIPD draws a useful distinction: an LNA is an ongoing process that connects learning to performance gaps and business strategy, while a TNA is often a review of the need for a specific training activity. In practice many organizations use the terms interchangeably. What matters more is that the analysis is tied to real business priorities and repeated, not filed once a year and forgotten.

Why it matters now

Skill requirements are changing quickly. In the World Economic Forum's Future of Jobs Report 2025, employers expected 39% of workers' core skills to change by 2030. In Saudi Arabia, the Human Capability Development Program under Vision 2030 places lifelong learning and readiness for the future labour market among its priorities. Both point to the same practical need: knowing which skills to build first, for whom, and why.

The three levels: organization, role and individual

Each level answers a different question, and each needs different data. The CIPD recommends looking at the levels together rather than in isolation, because a need that appears at one level often explains a need at another.

Organization-level analysis

Start with the strategy. If the organization is entering a new market, digitizing a process or preparing for a regulatory change, ask what people will need to do differently and which teams are affected. This level also checks the conditions for training to work: whether managers will release people, whether there is budget, and whether the work environment will support new behaviors once people return from training.

Role-level analysis

For each priority role, define what competent performance looks like. A competency framework or a well-written job description is a good starting point. Break the role into its main tasks, then list the knowledge and skills each task requires and the level needed. Talk to managers and strong performers, because written job descriptions often lag behind how the work is actually done.

Individual-level analysis

Finally, compare each person's current level with the role profile. This is where measurement quality matters most. If current levels come only from self-ratings or a manager's general impression, the gaps you find may say more about confidence than about capability. For a detailed, person-by-person method, see our guide to skills gap analysis.

Methods for collecting training needs data

No single method gives a complete picture. The CIPD suggests combining several, for example existing performance data, surveys, interviews and observation, so that each method covers the blind spots of another.

Choosing the right mix

As a rule of thumb, use performance data and interviews to decide where to look, and tests or work samples to measure how big the gap is. Surveys help you understand priorities and build support, but treat self-reported needs as one input, not the final answer. People can be confident in skills they have not fully mastered, and modest about strengths they underrate.

For technical and job-specific skills, a short, competency-based test gives you a baseline you can compare across teams and repeat after training, which turns the TNA from a list of opinions into evidence.

How to conduct a training needs analysis in 7 steps

This process works for a single department or a whole organization. Scale the depth to the size of the decision.

1. Agree the business goals and scope. Meet the sponsoring leaders and write down which goals the TNA supports, which teams and roles are in scope, the budget range and the deadline. A clear scope stops the analysis from growing into a wish list.
2. Define the required capabilities for each role. Using the competency framework, job descriptions and input from managers, set out the skills each in-scope role needs and the proficiency level expected. Keep it to the skills that matter most for performance.
3. Choose your data-collection methods. Pick two or three methods from the table above that fit the skills in question: tests for measurable technical skills, 360 feedback for leadership behaviors, interviews for context.
4. Measure current capability. Run the tests, surveys and interviews. Explain to employees why you are collecting the data, how it will be used and who will see individual results. People take part more openly when the purpose is development, not judgment.
5. Analyze the gaps and their causes. Compare current levels with required levels by person, team and role. For each significant gap, ask whether the cause is skills, or something else, such as unclear expectations, missing tools or workload.
6. Prioritize the needs. Rank the gaps by business impact, urgency and the number of people affected (see the next section). Decide which needs to address now, which to schedule later and which to solve without training.
7. Recommend solutions and agree how to measure success. For each priority, recommend the learning approach, the audience, timing and cost, and how you will check progress, for example by repeating the same test after training.