The Most Expensive Phase Nobody Wants to Pay For

A manager contacts you with a request. His team is underperforming. Errors are up, productivity is down, and morale is suffering. He's watched it get worse over the past several months and he's reached a conclusion: his staff doesn't know how to do their jobs. He wants a continuing training program — something ongoing, something structured, something that will fix the problem.

Before agreeing to build anything, you do what you're supposed to do. You conduct an analysis.

You interview new staff members. You talk to experienced employees who have been doing the job for years. You sit down with the managers and supervisors who oversee the work every day. And across every group, the same answer keeps surfacing — not "we don't know how to do our jobs," but something entirely different: we don't have any personal time. We never have space to breathe, to reflect, to work on the things we know we need to improve. We are always rushed. We are always overworked.

And when you dig into the performance data, the picture becomes even clearer. The employees know their jobs. They know the processes, the expectations, and the standards. They are not performing poorly because of a knowledge gap or a skill deficit. They are performing poorly because there aren't enough of them to do the work.

The solution isn't a continuing training program. It's more staff.

As it turns out, the manager was already looking at a separate question — whether he needed to double his workforce. The analysis didn't just redirect the training request. It answered a business question he had been sitting on for months and gave him the data he needed to make the case for the hire.

That is what a proper needs analysis does. And it is the phase that almost nobody wants to pay for.

The Assumption That Breaks Everything

The single most common failure in instructional design isn't bad course design. It isn't poor narration or weak interactions or a Level 1 survey that asks the wrong questions. It is the assumption — made before a single question is asked — that the problem is a training problem.

This assumption is so deeply embedded in how organizations think about performance that it functions almost like a reflex. Something goes wrong. Someone underperforms. A process breaks down. And the immediate response, at every level of the organization, is: we need training.

It feels logical. Training is how you fix people who don't know things. If performance is the problem, knowledge must be the gap. Build the course, close the gap, fix the problem.

Except most performance problems aren't knowledge problems. They're system problems. Resource problems. Process problems. Management problems. Communication problems. Motivation problems. Environmental problems. And a training course — no matter how well designed — cannot fix a staffing shortage, a broken workflow, a tool that doesn't work, or a culture that doesn't support the behavior the organization says it wants.

The analysis phase exists to figure out which kind of problem you actually have before you commit time, money, and organizational attention to building a solution that may not address it.

What Analysis Actually Looks Like

A proper needs analysis isn't a formality. It isn't a checkbox before the real work begins. It is the real work — or at least the beginning of it.

It means talking to the people doing the job, not just the manager who commissioned the training. It means talking to new employees and experienced ones, because they experience the same environment differently and their answers will reveal things neither group could tell you alone. It means talking to supervisors and managers, who see patterns across the team that individuals can't. It means asking questions that don't assume training is the answer — questions about workload, about tools, about processes, about what people would need to perform better if a course were taken off the table entirely.

It means being willing to bring back an answer the customer didn't expect and didn't ask for. In the example above, that meant telling a manager that his staff didn't need more training — they needed more colleagues. That is not a comfortable conversation. It is also the only honest one.

Why It Gets Skipped

The analysis phase gets skipped for two reasons, and both of them are understandable even if neither of them is acceptable.

The first is stakeholder pressure. A manager who has already decided the problem is a training problem does not want to spend time and money on a process designed to question that conclusion. They want the course. They want it soon. And an L&D professional who pushes back on that request — who says "before we build anything, I need to understand what's actually causing the problem" — is going to face resistance. Every time.

The second is that analysis produces a document, not a deliverable. There is no course to click through at the end. No completion certificate. No polished module to show the executive team. There is a report, a recommendation, and sometimes the unwelcome news that training isn't the answer. That is a hard sell in organizations that measure L&D success by the number of courses produced and the hours of training completed.

But consider the alternative. A continuing training program designed to address a knowledge gap that doesn't exist. Weeks of development time. Hours of employee time. Budget spent. And at the end of it, the same staffing shortage, the same overworked team, the same declining performance — plus a completed course that demonstrably did nothing, because it was solving the wrong problem.

The analysis phase is not overhead. It is the thing that keeps you from building the wrong solution at full cost.

The Question Worth Asking Before Anything Else

Before the next training request turns into a course outline, ask one question: how do we know this is a training problem?

Not rhetorically. Ask it directly, with the expectation of a real answer supported by real evidence. If the answer is "because people are making mistakes," follow up. Are they making mistakes because they don't know what to do, or because the system makes it difficult to do what they know? If the answer is "because performance is down," push further. Is performance down because of a skill deficit, or because the team is understaffed, undertooled, or working in an environment that doesn't support the behavior the organization wants?

Those are not the same problem. And they do not have the same solution.

The analysis phase is how you find out which one you're actually dealing with. Skip it, and you're not saving time. You're spending it on the wrong thing.