Train a customer effectively
Objective. Train using the explain - demonstrate - let the learner perform - check understanding - summarise next action loop, and deliver a 20-minute manager session plus a learner task and facilitator notes that produce a capable user, not an attendee.
A trained customer is one who can do the job without you, not one who watched you do it. This lesson gives you a repeatable training loop and has you build and rehearse a real 20-minute manager session on Time Champ, with a learner task and facilitator notes - so training produces a routine a manager will run next Monday, not a demo they forget by Friday.
See it in the demo
The customer problem
The default failure mode of software training is the tour: the trainer clicks through every screen, the room nods, and nobody can reproduce a single workflow afterwards. For Time Champ this is fatal because value comes from managers running routines - reviewing an exception, investigating an output change, acting on a signal. If the manager cannot independently open the right screen, read it in context and decide something, the deployment produces reports nobody acts on. Business impact: low adoption, no outcome, a weak renewal case. The cost of re-training a disengaged manager months later, after they have decided the tool is 'not for them', is far higher than training them properly once.
How Time Champ addresses it - the training loop
Use a five-step loop for every skill you teach. (1) Explain: the business reason and the one decision this screen supports - 'this is how you tell absent time apart from available hours before you chase utilisation'. (2) Demonstrate: do it once, slowly, narrating what you look at and why. (3) Let the learner perform: hand over the keyboard (or the demo account) and have them do it while you stay quiet. (4) Check understanding: ask them to interpret what they see and to name the mistake they could make - e.g. reading attendance % as if it answered the utilisation question. (5) Summarise the next action: 'next Monday you will do exactly this for your own team and log one follow-up'. The demo lab lets every learner perform safely on realistic data before touching live. Training without step 3 is a presentation, not training.
What to say / do - build the 20-minute manager session
Design a tight session around one routine, not the whole product. Example for a Work Output manager: minutes 0-3 explain why output attainment, not just utilisation, is the question that protects their SLA and cost; 3-8 demonstrate opening Work Output People, spotting the team whose cost per clean unit moved, and checking whether it is real or a standard/coverage artefact; 8-15 learner performs the same on the demo and talks you through it; 15-18 check understanding with two questions including an interpretation trap; 18-20 summarise the Monday action and where to log it. Write facilitator notes: the one business message, the exact click path, the interpretation trap to surface, the two check questions with model answers, and the learner take-home task. Keep scope ruthless - one routine done confidently beats five seen passively.
Checking understanding honestly
A nodding room is not evidence of understanding; a performed task and a correct interpretation are. Build checks that test judgement, not recall. Good check: 'This utilisation is 88% but attendance is 70% - which number answers which question, and which would you act on first?' Bad check: 'What colour is the exceptions tile?'. Surface the interpretation traps explicitly during training because they are exactly where managers go wrong unsupervised: attendance % and utilisation % answer different questions; a non-productive app label is not proof of no work; two teams are only comparable after aligning work type, complexity, period, tenure and quality. If a learner cannot navigate the trap in the room, they will fall into it in front of their own team, so re-teach before you move on.
Objections and honest limits
'Just send us a recording' - a recording trains nobody to perform; offer it as reference but insist on a live perform-and-check for the core routine. 'We don't have time for hands-on' - then cut scope, not the hands-on; teach one routine properly. 'Our managers are experienced, skip the basics' - experienced managers most often carry the interpretation errors, so keep the trap checks even if you speed the navigation. Honest limits: train only on what the product demonstrably does and the account is entitled to; if a manager asks about a capability you are unsure is in their entitlement, say 'let me confirm with product' rather than teaching a screen that may not be configured for them. Your job is a capable, correctly-calibrated user - not an impressed audience.
Interpretation check
Training is complete when the learner has performed the routine unaided and navigated the interpretation trap correctly - not when the trainer has finished demonstrating.
In the field
For KnackGlobal, the highest-value 20-minute session trains an RCM team lead to read output per FTE and cost per clean claim and to tell a real change from a coverage artefact - the exact literacy the sponsor needs to defend Time Champ against the incumbent internally.
Practical task
Build and rehearse a 20-minute manager session for one routine (Work Output attainment review or Time and Activity exception review). Deliver it to a peer acting as the manager, having them perform the routine on the demo. Hand over: a learner take-home task tied to their own team, and facilitator notes (business message, click path, interpretation trap, two check questions with model answers, Monday action).
Self-check
Which step of the training loop is most often skipped, and why does skipping it fail?
Letting the learner perform (step 3). Without it, training is a demonstration - the learner never builds the muscle memory or exposes their misunderstandings, so they cannot reproduce the routine alone.
Write a check-understanding question for a Time and Activity session that tests judgement, not recall.
For example: 'Utilisation reads 88% while attendance is 70% - which question does each answer, and which do you investigate first?' It forces the learner to separate the two measures rather than recite a label.
Why do you keep the interpretation-trap checks even for experienced managers?
Experienced managers are the most likely to carry confident but wrong interpretations (e.g. treating a non-productive label as proof of no work). The traps are where unsupervised errors happen, so they matter most for the people who think they already know.
A customer asks for a recording instead of a live session. What do you agree to?
Provide a recording as reference, but insist on a live perform-and-check for the core routine. A recording cannot verify the learner can perform or interpret correctly, which is the whole point of training.
Verified vs demo. The routines and screens taught are demo-shown. Whether a given manager's production account has the exact screens and data configured is entitlement-dependent - confirm with product before teaching a surface you are unsure is live for them.