Training Needs Analysis: The Complete Guide for Defence & Public Sector
Everything you need to know about running a TNA that survives audit, finds the real gap, and gives leaders evidence they can act on — from first principles through to board reporting.
What a Training Needs Analysis actually is
A Training Needs Analysis is the structured process of testing whether a performance gap is genuinely a training gap, or whether it's being held back by something else entirely — unclear roles, weak governance, a structure working against the outcome, or expectations nobody actually agreed.
That last part matters more than most organisations treat it: a properly run TNA can, and sometimes should, conclude that training isn't the answer. If it can't reach that conclusion, it isn't a needs analysis — it's a justification exercise for a decision someone already made.
Why TNA matters more in Defence and regulated public sector
Outside regulated environments, a weak TNA wastes budget on training that doesn't work. Inside Defence and regulated public sector environments, it does that and creates an audit problem — because DSAT, set out in JSP 822, requires the analysis behind a training decision to be defensible, not just the training itself.
That's the real link between TNA and DSAT: DSAT's Analysis phase is where a TNA lives, and an audit will test whether the capability requirement was genuinely established before design and development work began.
The TNA process, step by step
A defensible TNA moves through five stages: establishing the capability requirement, gathering evidence on current performance against it, testing whether the gap is genuinely a training gap, prioritising findings by evidenced impact, and reporting in a form leaders can act on.
Each stage produces something the next stage depends on. Skip the evidence-gathering stage and jump to recommendations, and there's nothing defensible underpinning the report — just opinion dressed up as analysis.
TNA vs skills gap analysis
The two get used interchangeably, but they answer different questions. A skills gap analysis maps what skills a person or role has against what a role requires. A TNA asks the broader and more important question first: is a skills gap even what's causing the performance problem, or is something structural getting in the way.
Run a skills gap analysis before that question is answered, and you risk mapping gaps against a requirement that was never the real constraint. See the dedicated article for the full distinction and when each tool is the right one.
Where TNAs go wrong — and what it costs
The same handful of mistakes account for most of the wasted budget: starting from an assumed answer, treating stakeholder wishlists as evidence, skipping the baseline so nobody can prove impact afterwards, and treating every request as equally urgent regardless of evidenced impact.
None of these are complicated to avoid. They're avoided by discipline — insisting on evidence before recommendation — not by a more sophisticated methodology. The dedicated article on this walks through each one with what it actually costs.
Presenting findings so leaders act on them
A TNA that never gets acted on has usually failed at the reporting stage, not the analysis stage — buried in methodology when the board needed a decision, or silent on cost of inaction when that's exactly what would have moved budget. Presenting findings well is a distinct skill from running the analysis, and it's covered in full in the dedicated article.
What a defensible TNA looks like in practice
The NATO and Royal Navy Training Modernisation case study is the clearest example on this site: a DSAT-compliant TNA pinpointed the specific points in the training pipeline where learners were being set up to fail, rather than recommending a wholesale redesign — lifting pass rates by 17% and cutting failures by 20%.
The Senior Information Officer Rapid TNA case study makes the companion point: run properly, as a decision framework rather than a process to endure, a TNA accelerates good decisions instead of delaying them. The constraint in that engagement wasn't methodology — it was unclear requirements, resolved quickly once the right questions were asked.
Common questions on this topic.
It's the right starting point whenever training is being considered as part of the solution — its job is precisely to test that assumption before budget is committed, rather than to confirm a decision already made.
DSAT's Analysis phase is effectively where a TNA lives — see the DSAT Explained article for the full methodology, and this guide for how to run the analysis itself so it holds up to audit.
This guide is the comprehensive reference — process, common failure modes, board reporting and DSAT alignment in one place. The Best Practice article and the other pieces linked below go deeper on specific parts of that process.
Many organisations can run one in-house with the right structure and discipline. External support tends to add most value where independence, evidence rigour or DSAT-specific experience is the limiting factor, not where the process itself is unfamiliar.
Want this thinking applied to your organisation?
Insight is useful. Applied insight changes outcomes. Let's talk about yours.