A role-based Intelex training plan that sticks

Most Intelex training is organized by module, because that is how the demo was organized. A supervisor sits through incident management end to end, learns the parts they will never touch, and gets four minutes on the two things they must do on the day. Six weeks later they cannot find their task queue.
Organizing by role instead is not a philosophy, it is arithmetic. The session has a fixed length, each role has a short list of things a person must be able to do without help, and every extra screen shown on the day competes with that list for the only attention anyone will give it. This is also what an auditor looks for. ISO 45001:2018 separates clause 7.2 (competence) from clause 7.3 (awareness) for a reason, and CCOHS puts it plainly in its due diligence guidance: "The employer must provide the appropriate training and education to the workers so that they understand and carry out their work according to the established policies, practices, and procedures."
Why module-based training fails and role-based training does not
Module training teaches breadth to people who need depth on one path. A frontline reporter needs one path through one form. Showing them the review, investigation and closure stages tells them, accurately, that the system is complicated and mostly not for them.
Free
Read every article, in full.
- Every article on the site, start to finish
- Sources cited and linked on all of them
- New pieces on Intelex configuration and EHS practice
Would rather not sign up? Email me and I will send it over.