Why We Refuse to Start With a Course

"Just send us your communication module. We'll run it for the whole team."

A learning lead at a pharma client asked us for exactly that. It was a reasonable request, and we said no. Not because we lacked a module, but because we had no idea yet what was actually broken. Sending a course before diagnosing the problem is like a doctor writing a prescription before the patient has described the symptom. This post is about diagnostic-led training: why the diagnosis has to come first, what most programmes skip, and what changes when you get the order right.

Most training solves a problem nobody defined

The default sequence in corporate learning is backwards. Someone senses a gap, a course is chosen or bought, the course is delivered, completion is recorded. The problem the course was meant to solve is never actually stated, so nobody can tell afterwards whether it was solved.

This is not a small inefficiency. It is the reason so much training feels busy and changes nothing. When you start with a solution, you spend the whole programme hoping it happens to fit. When you start with a diagnosis, you already know what you are fixing before you design a single session.

Organisations rarely know what they're actually short of

This is not a failing of any one company. It is the norm.

In a McKinsey Global Survey (fielded in 2019), fewer than half of respondents said their organisations had a clear sense of their current skills, and only 41 percent had a clear understanding of which roles were likely to be disrupted. More recently, McKinsey's HR Monitor 2026 found that HR functions tend to overestimate both how much training employees actually do and how much employees value it, with a meaningful share of employees reporting no training participation at all.

Read those together and the picture is uncomfortable: organisations often cannot see their real skill gaps clearly, yet buy solutions for them anyway. The gap between what leaders think is happening and what is happening on the ground is exactly where a diagnostic earns its place.

What a diagnostic actually does

A diagnostic is not a survey asking people how confident they feel. Self-reported confidence is one of the least reliable signals in learning.

A useful diagnostic looks at real behaviour and real output. For communication, that means reviewing actual emails, listening to actual calls, watching how an instruction moves from one team to the next and where it degrades. It means a structured baseline: not "the team needs help with communication," but "escalations cluster at the handover between support and engineering, and the trigger is ambiguous written updates under time pressure." One of those is a vague brief. The other is a design specification.

The point is precision. You cannot fix a metric you have not located.

Why off-the-shelf so often disappoints

Off-the-shelf training is not bad because it is generic. It is disappointing because it assumes the diagnosis instead of doing it.

A ready-made module is built for an average organisation that does not exist. It may cover the right topic while missing the specific behaviour that is actually costing you money. Two BFSI clients can both say "our managers need to communicate better" and need completely different interventions: one has a written-clarity problem in customer correspondence, the other has managers who avoid difficult conversations entirely. The same course cannot fix both, and neither client learns which problem they had until someone looks.

What changes when diagnosis comes first

When you diagnose before you design, three things shift.

• You can state, before the programme begins, what metric it should move, so success is defined rather than assumed.

• You stop paying to train behaviours that were never the problem.

• You can prove impact afterwards, because you have a baseline to measure against.

That last point matters most to anyone who has to justify the spend. Without a baseline taken up front, "it went well" is the strongest claim you can make. With one, you can show what changed.

The question worth sitting with

Most L&D budgets are spent on solutions. Very little is spent on understanding the problem the solution is meant to address.

So the question for anyone about to sign off a programme this year: do you know precisely which behaviour is costing you money, and how you will prove it moved? If the honest answer is not yet, the programme is not the first thing to buy. The diagnosis is.