Needs analysis has a timing problem.
By the time someone asks for training, the data that should have driven that request already existed — in your LMS, your performance reviews, your support tickets, your manager feedback. You just weren't watching it. So you start from scratch. You build surveys. You schedule SME interviews. You wait. And somewhere in that gap, the problem gets worse or the moment passes.
There's a better model. Call it continuous needs analysis.
The idea is simple: instead of treating needs analysis as a project that kicks off when someone asks for training, you treat it like a river. It's always running. The data is always flowing. And whenever you need to scope a new learning intervention, you don't start from scratch — you step into the river and pull out what's already there.
What the river is made of
You probably have more needs analysis data than you realize. It's just scattered:
LMS completion rates and assessment scores by role or team
Performance review themes and manager feedback
Help desk or support tickets (often a goldmine of skill gaps)
Employee survey results, especially "I don't feel prepared to..." responses
Exit interview data
Sales call recordings, customer complaints, QA flags
None of this was designed for needs analysis. But all of it points to learning gaps if you know how to read it.
Where AI comes in
The reason this has been impractical until now: synthesizing data across those sources used to take hours. You had to pull reports, cross-reference them, look for patterns, and write up a summary a stakeholder might actually read.
AI removes most of that friction.
If you can get your data into a document — even a rough paste of key figures and themes — a well-structured prompt can turn it into a draft needs analysis brief in minutes. Not perfect. But directional. Enough to walk into a stakeholder conversation and say: here's what the data already tells us.
Setting this up doesn't have to be a big project
Start small. Pick two or three data sources you can realistically pull from on a quarterly basis. Build a simple document template where you paste the highlights. Then use a prompt (see below) to synthesize it into a needs analysis brief.
You're not building a dashboard. You're building a habit — a lightweight system that means you're never starting from zero again.
Prompt of the Week
Use this when you have data from multiple sources and need to scope a learning need quickly.
You are an instructional design consultant helping me conduct a needs analysis.
I'm going to paste data from several sources. Your job is to:
1. Identify the top 3–5 learning or performance gaps suggested by this data
2. Note any patterns, urgency signals, or recurring themes
3. Flag anything that points to a non-training root cause
4. Summarize your findings as a brief needs analysis I can share with a stakeholder
Here is the data:
[paste your LMS reports, survey highlights, performance themes, support ticket patterns, etc.]
Audience: [role or team]
Context: [what's the business situation or pressure driving this?]
Adjust the output format to match how your organization talks about performance gaps. A two-paragraph summary works for some stakeholders. Others want a structured brief with recommended next steps.
The goal isn't a perfect system. It's to stop treating needs analysis like a fire drill and start treating it like part of how your team already works.
If you want help building a lightweight continuous needs analysis setup for your team, that's exactly the kind of thing we work through in an AI Readiness Audit. [Reply and I'll send you the details.]
Gus
P.S. — If this clicked, forward it to someone on your team who's tired of starting from scratch every time.