The question that should start every L&D conversation
Most requests arrive as a solution — we need a leadership programme. One question, asked early, turns that into something you can actually solve.
A department head asks for a communication skills course. A regional manager wants resilience training. A director has seen a competitor announce an AI academy and would like one too. Each request arrives already shaped as a solution, and the fastest way to disappoint everyone is to deliver exactly what was asked for.
The question that changes the conversation is this one: what capability, if we built it, would move this number?
It does three things at once. It forces a number into the room, so the work has a target. It shifts the discussion from content to capability, which is where the design decisions actually live. And it exposes, quickly and without confrontation, the cases where training is not the answer at all.
Four reasons a person does not perform
Only one of them is a training problem. They may not know how — that is capability, and it is yours. They may know how but be unable to, because the process, the system or the staffing prevents it. They may know how and be able to, but have no reason to, because nothing measures or rewards it. Or they may be actively discouraged, because the behaviour costs them time, conflict or a target.
Training a person out of a process problem is expensive, slow, and it does not work. It also quietly damages the credibility of the next programme you run.
Asking it without sounding obstructive
The risk is real: a business partner who answers every request with a diagnostic question starts to feel like an obstacle. The way around it is to bring the question with a commitment attached. Not can you justify this, but give me the number you are trying to move and two weeks, and I will come back with a design that targets it.
Two weeks is usually enough. Interviews with six or eight people close to the work, a look at whatever performance data already exists, and a short observation if the behaviour is observable. You are not building a research programme. You are finding out which of the four reasons you are actually dealing with.
What you get back
- A scope that is smaller and sharper than the original request, and therefore cheaper and faster to deliver.
- A named business owner who has agreed in advance what success looks like.
- A defensible answer for the cases where the honest recommendation is do not train — fix the process.
- A measurement design that exists before the programme rather than after it.
None of this requires a new framework or a bigger budget. It requires asking one question before agreeing to anything, and being willing to hear an answer that means less work for your team this quarter and considerably more credibility next year.