Common TNA Mistakes That Waste Budget
The same handful of mistakes account for most of the money wasted on Training Needs Analyses that should never have recommended training in the first place.
Starting from the answer, not the question
The single most expensive mistake is beginning a TNA with training already assumed as the outcome, and using the analysis to justify it rather than to test it. Every subsequent step of an analysis run this way is biased toward the predetermined conclusion, however rigorous it looks on paper.
Wishlist syndrome
Asking stakeholders what training they'd like, then packaging the answers as a needs analysis, reliably produces a wishlist rather than a diagnosis — people asked what training they want will describe training, because that's the question they were asked. It doesn't test whether training is the right answer at all.
No baseline, no way to prove it worked
Without a documented baseline of current performance, there's no way to demonstrate afterwards that an intervention actually closed the gap it was funded to close. This is usually discovered at the worst possible time — when a leader asks what the training achieved, and the honest answer is that nobody can say.
Treating every request as equally urgent
Without evidence-based prioritisation, budget tends to go to whoever asked loudest or most recently, rather than to the gap with the largest evidenced impact on performance. A TNA that doesn't rank findings by impact hasn't finished its job.
Skipping the evidence base
Interviews and stakeholder opinion are useful context but are not, on their own, evidence of a performance gap. Performance data, error rates, incident reports and structured observation are what turn a set of opinions into a defensible finding — and their absence is the single easiest thing for a sceptical reviewer to challenge.
Common questions on this topic.
Starting from the answer rather than the question — it doesn't just waste the cost of the analysis, it commits budget to an intervention that was never properly tested against the actual problem.
Often, yes — introducing a baseline or broadening the evidence base partway through is better than not doing it at all, though it's more efficient to build them in from the start.
Not always — a well-written wishlist can look like a rigorous needs analysis. The tell is whether the report could ever have concluded training wasn't needed; if that outcome was never possible, the process wasn't testing anything.
Want this thinking applied to your organisation?
Insight is useful. Applied insight changes outcomes. Let's talk about yours.