Training Needs Analysis Template (With Filled Example)
A training needs analysis (TNA) is the document that separates a founder who's about to build a program someone will actually pay for from one who's about to build a program based on a guess about what a business needs. The discipline itself comes from established L&D practice, but a founder-grade version can be run as a structured interview with a real buyer — five sections, each with the specific question that surfaces the information a curriculum, a price, and a pilot pitch all depend on.
Quick Answer: A founder-grade training needs analysis captures five things directly from an L&D buyer: the business outcome currently at risk, the specific skill gap behind it, the exact learner audience, real delivery constraints, and how success will be measured — run as a structured conversation, not a form the buyer fills out alone.
The Template Itself, Ready to Copy
Training Needs Analysis: [Company/Team Name]
1. Business Outcome at Risk
- What business metric or outcome is currently underperforming: [specific, quantified if possible]
- How long has this been a problem: [timeframe]
- What's the cost of not fixing it: [turnover, missed targets, escalations, etc.]
2. Skill Gap Behind the Outcome
- What specific skill or capability is missing: [named precisely, not a general competency]
- How was this gap identified: [manager observation, performance data, employee feedback]
- Has anything been tried already: [prior training, informal coaching, and why it didn't fully close the gap]
3. Learner Audience
- Who exactly needs this training: [role, level, team, number of people]
- What's their current skill/experience level: [baseline]
- Any relevant context: [tenure, prior training history, team dynamics]
4. Delivery Constraints
- Available time: [hours per week/month realistically available for training]
- Format preference or constraint: [live, async, in-person, remote, hybrid]
- Timeline: [when does this need to start, and why]
- Budget signal: [any indication of budget range, even rough]
5. Success Measures
- Primary metric: [what will be checked to know if the training worked]
- Measurement timing: [immediately after, 30/60/90 days out]
- Who reviews the result: [named person or role]
- What happens based on the result: [scale up, adjust, discontinue]
Field-by-Field Explanation With the Question to Ask
For the business outcome section, ask directly: "What's happening on your team right now that made you start thinking about training?" This question anchors the entire conversation in a real, felt business problem rather than an abstract competency gap — a buyer who answers with a specific number (a turnover rate, a missed target, a frequency of escalations) has given you something you can eventually measure against; a buyer who answers only in generalities may not yet have a fully formed reason to actually fund this.
For the skill gap section, ask: "What have you noticed people doing, or not doing, that connects to that outcome?" Push for specific, observable behavior rather than an abstract skill label — "managers avoid giving direct feedback" is observable and trainable; "poor communication" is too vague to design a curriculum against confidently.
For the learner audience section, ask: "Exactly who would be in this training, and what's true about them today?" Get precise on headcount, role, and current experience level — a program designed for complete beginners looks very different from one designed for people who've had some prior training and need to close a specific remaining gap.
For the delivery constraints section, ask: "Realistically, how much time can people actually give this, and what format works for your team?" This question often surfaces the real operational constraint that shapes everything else — a team that can genuinely spare only thirty minutes a week needs a fundamentally different program design than one with a full day available for an intensive workshop.
For the success measures section, ask: "What would you look at ninety days from now to know this worked?" This is the question most likely to be skipped in an informal conversation, and it's the one that turns a training engagement from a one-off delivery into evidence you can use to sell the next pilot — see validating a corporate training program for how this measurement plan feeds directly into your pilot's go/no-go evidence.
Filled Example: A Sales-Onboarding Training Need
Training Needs Analysis: Northbridge Software, Sales Team
1. Business Outcome at Risk — New sales hires are taking an average of five months to hit full quota, compared to a three-month target the VP of Sales has set. This has been a problem for roughly a year, since the team doubled in size. Cost: an estimated $40,000 in lost pipeline per rep during the extended ramp period, across eight new hires this year.
2. Skill Gap Behind the Outcome — New reps struggle specifically with objection handling on pricing pushback in the first 60 days, identified through the sales manager's call-review notes and confirmed by two new reps in informal conversation. A generic onboarding deck covers product knowledge well but has no dedicated objection-handling practice component; new reps currently learn this only by trial and error on live calls.
3. Learner Audience — All new sales hires going forward, currently onboarding at a rate of two to three per quarter. Most come in with 1–3 years of general sales experience but no experience with Northbridge's specific product or pricing model.
4. Delivery Constraints — New reps have roughly two hours per week available during their first eight weeks, on top of existing onboarding. Format needs to be remote-friendly, since two of the last three hires were remote. Timeline: needs to launch with the next new-hire cohort starting in six weeks. Budget signal: the VP mentioned a willingness to spend "a few thousand dollars" per cohort if it demonstrably shortens ramp time.
5. Success Measures — Primary metric: average time to first full-quota month for the next cohort, compared against the current five-month baseline. Measured at the 90-day and 150-day marks for each new hire in the pilot cohort. Reviewed by the VP of Sales directly. If ramp time drops meaningfully, the program continues and expands to future cohorts; if not, the VP wants a debrief on what didn't work before continuing.
Adaptation Notes: Using the TNA as a Discovery Interview Guide
This template works as a structured live conversation with a buyer, not a form to email and wait on — running it live lets you ask natural follow-up questions when an answer is vague, which is where the most useful, specific detail usually surfaces. Take notes during the conversation rather than asking the buyer to fill out the document themselves; buyers are often too close to the problem to articulate it in the structured way this template requires, and your job as the interviewer is to extract and organize that structure from a more natural conversation.
Treat a TNA that produces vague, hard-to-pin-down answers across multiple sections as a signal worth taking seriously — it may mean the buyer hasn't yet fully diagnosed their own problem, which makes them a weaker candidate for an immediate pilot regardless of their enthusiasm, and a stronger candidate for a follow-up conversation once they've had time to think it through further.
Key Takeaways
- Anchor every training needs analysis in a real, felt business outcome first. A buyer with a specific, quantified problem is a stronger pilot candidate than one who wants training in the abstract.
- Push past competency labels to specific, observable behavior. "Poor communication" isn't trainable; "avoids giving direct feedback in performance conversations" is.
- Delivery constraints often determine the entire program design. Ask about realistic time availability before designing anything.
- The success-measures section is the one most often skipped — and the one that matters most. It's what turns a training delivery into evidence for your next sale.
- Run this as a live conversation, not a form. Vague answers deserve a follow-up question, not a blank field left as-is.
- A TNA with consistently vague answers is itself useful information. It may point to a buyer who isn't yet ready for a real pilot commitment.
Frequently Asked Questions
How long should a training needs analysis conversation take?
Thirty to forty-five minutes is usually enough to work through all five sections with a genuinely engaged buyer, though complex or unclear situations may need a follow-up conversation — treat the first session as a starting draft you can refine rather than expecting a complete, precise picture in a single pass.
What if the buyer doesn't know the answer to the skill-gap or success-measures questions?
That's valuable information, not a dead end — a buyer who's identified a real outcome problem but hasn't yet diagnosed the specific skill gap behind it, or hasn't thought about how they'd measure success, may need a short discovery period (talking to their own team) before they're ready to commit to a pilot, which is worth surfacing explicitly rather than plowing ahead with your own guess.
Should I share this template with the buyer in advance?
It can help to share a lighter version in advance so they come prepared with real numbers, but the most valuable detail usually comes from live follow-up questions during the conversation itself — don't rely on a buyer filling out the full template alone without your involvement, since that tends to produce shallower, more generic answers.
How is this different from a general customer discovery interview?
The core discipline of asking about specifics rather than hypotheticals is shared with general customer research, but a TNA is more structured and outcome-anchored specifically because it needs to produce inputs a curriculum, price, and pilot design can be built directly from, not just general validation signal.