The difference in one paragraph
Training changes what people know. Enablement changes how a piece of work is done. If your tools are approved and set up for the work, someone owns adoption and the results are measured, then a skills gap is the remaining problem and training will close it. If any of those are missing, training teaches people to use something that does not yet fit their work, and usage fades within weeks.
How the symptoms map to a result
The tool asks about seven symptoms, each pointing to a different kind of fix:
- People do not know how to use the tools. A skills gap: training fixes this well.
- Tools are not configured, connected or approved for the work. Setup work. A course cannot make a tool ready for the job.
- Workflows have not been redesigned. AI is bolted onto the old process, or used ad hoc. The work needs redesigning with the people who do it.
- No internal owner. Without one, use fades after launch.
- No measurement. Without a baseline, nobody can tell whether anything changed.
- Usage rose, then fell. Usually a sign the tool did not fit the work.
- Leaders are unconvinced or have not decided what AI is for. Everything else waits on this.
The rules are simple and applied in order. Any leadership symptom gives leadership decision needed first. Otherwise, any of the five enablement symptoms gives enablement pilot needed. If only the skills symptom is ticked, training is enough. If nothing is ticked, the tool suggests measuring one workflow before buying either.
When training really is enough
It is worth saying plainly: sometimes it is. A team with approved, well-configured tools, clear usage rules, an owner and a measure of the work does not need an enablement engagement. It needs people who know how to use the tools well, and a good course, vendor training or an internal champion will provide that. Recommending enablement in that situation would be selling more than is needed.
Illustrative example
Illustrative example, not a client engagement. A finance operations team was given AI licences and a half-day course. Three months later, the L&D director ticks three symptoms: people still do not know how to use the tools well, the month-end workflows have not changed, and nobody owns adoption.
The result is enablement pilot needed. The tool adds two notes: build the training into the pilot, using the redesigned month-end workflow as the material rather than running another separate course; and name the internal owner before the pilot starts, because that is the one thing an outside party cannot supply.
Assumptions and limitations
This is a rule of thumb from your own ticks, not an assessment of your organisation. It does not evaluate particular courses or providers, and it cannot tell whether a symptom is widespread or confined to one team. If different teams would tick different boxes, run it once per team. Where several symptoms are borderline, read the reasons rather than relying on the headline result.
What to do next
If the result is an enablement pilot, check the prerequisites with the readiness self-assessment, then see AI enablement for how a pilot runs. If training is enough and you want the skills to stay in-house, the AI champions and train-the-trainer programme builds internal trainers. To find out whether training changed the work, use the adoption measurement worksheet.
If the result is a leadership decision, that conversation comes first. It is a different engagement, run through my leadership practice at dipankar.org.