The pattern
Ask an L&D manager why the last digital training programme quietly bled out, and the answer is almost never about production capacity. It is about a steering group that never got convinced, a subject matter expert who felt it was not right, a works council asking questions nobody had an answer to.
The money was there. The need was there. What was missing was support, and it drained away in exactly the phase where nobody thought anything was at stake: the concept phase.
Documents convince nobody
A concept usually gets delivered as a document. Learning objectives, audience analysis, module structure, assessment strategy. Expert, complete, and entirely unfit for the purpose it is being used for.
Because what actually happens in that meeting is that people have to imagine something that does not exist yet. Anyone with experience of e-learning does that on the basis of what they saw before, and that was usually a dull module they had to click through. Fighting off that association is the whole job, and a text document does not fight it.
There is something else. A forty-page blueprint gets read by practically nobody. People look at the summary, at the timeline and at the figure. The content decisions the entire programme rests on go through untested, and come back at the moment the material exists and changing it has become expensive.
The three sceptics
In practically every organisation the same three roles can hold a programme up, and each has a different reason.
The subject matter expert fears it will end up superficial. They have twenty years of experience and have watched their trade flattened into four bullet points before. Their objection is not to digital learning but to the loss of nuance.
The supervisor on the floor mostly sees time their crew does not have. They count in hours not spent on production and do not believe it will deliver anything.
Employee representation looks at the records: who sees which results, what happens to scores, can any of this be used against somebody.
All three have a point, and all three can be won over, but not with a document that never addresses their particular worry.
What does work
What turns the discussion around is something tangible: a clickable preview of one module, built with their installation, their terminology and a situation they recognise.
That changes the conversation fundamentally. Nobody is talking about what it could become any more; they are talking about what is in front of them. The expert points out what is wrong on the content, which is valuable input, and you get it early instead of late. The supervisor sees it takes ten minutes rather than half a day. The works council sees which data is captured and which is not.
The important part is that this happens early, not at the end. A preview on day two costs little and can still change everything. That same preview after eight weeks of building is no longer a preview but a delivery, and steering is expensive by then.
The practical consequence: in every programme, set aside budget and time explicitly for something tangible before the final decision. Not as a nice extra, but as the instrument that gets you through the phase where most projects run aground.
The concept phase is one of the places training programmes come unstuck. The others, and how to avoid them, are in the guide on setting up or renewing a corporate academy. What we build is on the solutions page, and involving your own subject matter experts is covered under expert knowledge.