Begin: understand the basics
Start with the plain-language introduction and the first task. No need to navigate the whole OS.
Start here →Learn a little. See it work. Try it yourself. Get useful feedback.
This approach draws on research into worked examples, learner-paced segments and retrieval practice. Shorter screens reduce competing material; they do not replace meaningful practice. Read the evidence and its limits.
Start with the plain-language introduction and the first task. No need to navigate the whole OS.
Start here →Follow the lessons that fit your role. Use examples and help when you need them.
Find your role →Choose a real record together, explain your decision and trace the evidence. Your team owns the review.
Use the team kit →Space sessions around the team’s work. The best interval depends on what people need to remember and for how long; there is no universal “perfect” lesson length.
This first version provides self-paced practice and facilitator materials. A future team programme can add reviewed project assignments, mentor feedback and delayed skill checks. Shared enrolment, manager dashboards and formal credentials would need a separate learning system and an agreed assessment process.
A learner has passed the tutorial’s practice tasks and knowledge checks. It does not establish workplace competence or approve an engineering project. Progress is saved in their browser and can be downloaded for discussion.