Building Training From Your Procedures

The contradiction tends to surface at the worst possible moment. A new hire follows what the training told them, an experienced colleague corrects them from the written procedure, and both are quoting something the company itself published. Neither person is wrong, which is exactly why the problem persists: there is no single source anyone can go and correct. Deriving the training from the documentation removes the possibility, and it costs less than maintaining the two of them separately.

Why the order matters this much

Training built alongside documentation begins drifting immediately. Six months later the procedure says one thing and the course says another, nobody can say which is current, and the organization concludes that documentation does not work. What failed was the sequence.

Training built from the procedures cannot drift, because there is one source. Change the procedure and the consequence for the training is visible and traceable. That single property is worth more than any amount of instructional polish.

Curriculum first, materials second

Curriculum development is the shape of the whole thing: which subjects, in what order, at what depth, for which roles, and what is deliberately excluded. Materials are what sits inside it. Most programs are built the wrong way round - someone starts making slides and the curriculum is whatever the slides turn out to cover.

Build the shape from the needs analysis. For each role, the sequence of capabilities in the order they can actually be learned, which is rarely the order the process runs in. People usually need the common path fluently before the exceptions make any sense.

Design a learning path, not a course

A course is an event. A learning path is a route from first day to independent competence, and it is what stops new hires learning by observation alone.

1. Day one to week one

   Orientation and the single most common task, done under supervision, and nothing else. Most onboarding fails by front-loading everything.

2. Weeks two to four

   The rest of the common path, with the procedures as the reference. This is where the job aids earn their place.

3. Month two onward

   Exceptions, escalations and the judgement calls, introduced as they arise rather than taught in the abstract.

4. The checkpoint

   A defined point at which somebody establishes the person can perform the work unaided, and says so. Without it, nobody is ever formally competent and everybody keeps checking.

Choose the medium after the need, never before

A great deal of material that becomes eLearning would work better as a one-page job aid. A great deal that becomes a workshop would work better as a four-minute recorded walkthrough. The medium usually gets chosen first, because of what a department already owns or a licence somebody bought.

The rough guide we use runs as follows. Knowledge that must be recalled: brief instruction plus practice. Knowledge that must be looked up: a job aid, never a course. A skill that must be performed: practice with feedback, which means a human. Judgement: discussion of real cases, which means a facilitated session. A system click-path: a screen recording, which costs almost nothing and updates easily.

Job aids are the highest-value thing you will produce

One page, at the desk, covering the task as performed under time pressure. They are unglamorous, they take an afternoon, and they get used more than everything else combined. Build them from the procedures and they stay correct.

If you only do one thing from this article, do this.

Assessment that means something

A multiple-choice quiz establishes that someone can recognize a correct answer in the twenty minutes after being told it. That is not what you needed to know.

Assess by observing the task, against the requirement written as a task in the needs analysis. It takes longer and it tells you something true. For most operational work, one supervisor watching one real transaction is worth more than any amount of scoring.

Deliver it, then hand it over

The arrangement that sticks: we run the first cohort, your trainers run the second with us in the room, the third is yours entirely. Train-the-trainer as a standalone workshop, with no live delivery attached, tends not to transfer - facilitation is a skill and skills need practice with feedback, which is the same principle the rest of this article is about.

Then expect to go back

Some weeks after delivery, look at what people are actually doing. Where practice has diverged from the training, establish whether the training was wrong or the adoption was incomplete, because those need opposite responses. Where people found a better way, the procedure changes and the training follows - which is the whole point of having one source.