A certificate is not capability.
Most training is judged on the wrong day — the day it ends. Everyone is engaged, the slides looked good, the certificates are printed. But the real test is three weeks later, when someone is standing in front of the actual equipment with an actual decision to make. If nothing changed on the job, the training did not work — regardless of how the session felt.
The goal is not attendance. It is behaviour: can the team now do something they could not do before, on their own, when it matters?
Why most training fades by the next week.
Trained, then forgotten
A day is filled and faded by the next week because nothing in the workflow requires the new skill.
Theory, not the job
Generic slides that do not match the equipment, systems, or decisions the team actually faces.
No room to practise
Knowledge without hands-on application never becomes capability — you cannot learn to inspect by watching.
Skill locked in one person
When the one who attended leaves, the capability leaves with them, because it was never designed to transfer.
What actually makes it transfer.
Training that survives the session is built differently from the start. Three things make the difference:
Real material
Built from actual project work and case findings — the faults, panels, and reports the team will really encounter — not textbook examples.
Hands-on practice
People work with real methods and instruments during the session, so the first time they apply a skill is not on a live site under pressure.
Designed to transfer
Structured so the team can apply, repeat, and pass it on — capability that stays with the organisation, not just the individual.
The measure of good training is not what people know when they walk out. It is what they can still do, unaided, a month later.
Theory and practical are two different purchases.
A one-day theory session and a two-day practical are not the same thing priced differently — they do different jobs. Theory builds the mental model: what to look for and why. Practical builds the hands: doing it, being corrected, and doing it again. Most teams need both, in that order. Buying only the theory day and expecting capability is the most common way training disappoints.
How to tell before you book.
Before committing to any provider, ask:
- Is the material built from real work in our field, or generic courseware?
- How much of the time is hands-on versus slides?
- Who is teaching — someone who does the work, or a full-time trainer?
- What will our people be able to do afterwards that they cannot do now?
- How does the capability stay with the team if that person leaves?
- Is there a certificate of completion, and is it honest about what it is — evidence of practical capability, not a substitute for formal Level 1 or Level 2 certification?
AMKA’s view
Training is worth paying for when it changes what the team can do on Monday. We build from real AMKA project cases, keep it hands-on, and design it to transfer — and if a workshop is not the right answer for what you actually need, we will say so.