By function
Operations teams
From the weekly report to the warehouse floor
Operations carries the widest spread of this catalogue: office workflows that want automating, data that wants trusting, and - where there is a site - the robots, cells and conveyors that people work alongside every shift.
1.The reporting week, automated
The situation
Every Monday someone assembles the same numbers from the same four systems into the same deck. It takes half a day, and it is wrong often enough that nobody fully trusts it.
In practice
Mapping the reporting workflow, automating the assembly, and putting checks on the data feeding it - so the half-day becomes minutes and the number is one someone will stand behind.
2.People and cobots on the same line
The situation
A collaborative robot is arriving on the line. The integrator trains two people on commissioning day, then leaves - and every shift after that inherits a machine nobody quite owns.
In practice
Operators train hands-on: starting, guiding and stopping the cobot, running the daily checks, recognising the conditions where it should not run, and escalating faults instead of improvising fixes.
3.Automation that survives peak
The situation
The automated storage and the conveyors run beautifully in the demo and adequately in November. Peak is when exceptions multiply and one unit down becomes a site problem.
In practice
Teams learn how the automation routes and queues work, how to handle the exceptions it reliably creates, how to keep throughput in degraded running, and how to prepare the site for peak rather than survive it.
4.A rollout the floor actually adopts
The situation
The last system rollout technically succeeded: deployed on time, adopted by almost nobody. The workarounds it was meant to replace are still running.
In practice
Planning the next rollout around the people whose work changes, equipping the group that decides whether it sticks, measuring adoption rather than deployment, and reading the early signals in week three instead of month six.
Start with the measurement, not the course list
The 7 courses cited above are a starting point. The assessment scores your teams across five dimensions and recommends training against the gaps it actually finds.