Learn: Build Skill That Lasts

1. What this stage is for

Learn is where people build the knowledge, skill, judgment and ability to work alongside new technology that the defined future work requires. It sits after Prepare because the conditions for learning matter as much as the content: managers ready to coach, a sandbox to practise in, real templates to practise with. It sits before Apply because learning that never meets real work fades quickly. #52 · #2

This stage is not "deliver the training". A course is one possible tool. Many of the most effective forms of learning happen at work: a supervised first attempt, a worked example from last month's project, feedback on a real model, a debrief after a difficult pour. The test of this stage is simple: can people do the new work to the required standard, on a task they haven't seen before, without help? Satisfaction ratings, completions and attendance don't answer that question. LSC-MSR-03 · LSC-MSR-01 · IDE-DES-06

The good news is that the research on adult learning for technical work is unusually consistent, and the methods that work aren't expensive. The bad news is that the methods that work best often feel worse to learners, look worse in training, and score lower on satisfaction surveys. Most of this brief is about choosing what works over what feels good. LSC-PRC-05 · #19

2. What the evidence says

One way to read learning research is to ask where the typical person trained one way lands among people trained another way. If two methods are equally good, the typical learner lands in the middle: better than half of the comparison group. Strong methods move that typical learner well above the middle. LSC-EVD-02

A handful of principles carry most of the weight:

• Organize around whole, real tasks, from simple to complex, rather than topics. Programmes built this way, with the reasoning behind methods taught alongside, step-by-step information delivered when it's needed and drills reserved for routines that must become automatic, show some of the largest effects in technical training. LSC-DES-02 · IDE-DES-03
• Show before you ask. Novices learn more from studying worked examples than from solving problems unaided. LSC-CLT-01 · #59
• Practise from memory, with feedback. Retrieving something strengthens it more than reviewing it again. LSC-PRC-01 · #19 · #60
• Spread practice over weeks. Spaced refreshers beat one long session. LSC-PRC-02 · #3
• Match training to the job. For fixed procedures, practise in conditions that look like the work; for judgment, vary the practice. LSC-TRF-02 · LSC-TRF-07

Expect modest results from good design and smaller ones from complex procedures. A recent re-analysis of multimedia research found real effects that are smaller than first reported and shrinking over time. That's not a reason to give up on design; it's a reason not to promise "89% better retention" to anyone. IDE-MM-04 · LSC-EVD-02

3. Show, then fade

For anyone learning a task for the first time, use the sequence with the strongest evidence in technical training: a complete worked example, then partly completed tasks, then independent ones, with feedback at every step. For a BIM coordinator that might mean watching a senior colleague set up a federation and run a clash test, then finishing a half-built test, then running one alone on a live model. For a maintenance technician it might mean studying a completed isolation, then completing one with the last steps missing, then doing one from scratch under supervision. LSC-CLT-01 · LSC-TRF-06 · #59

Two refinements make the sequence work at work. First, start from what people already know. A short diagnostic task on day one tells you who can skip the early steps. Experienced people need problems and references rather than walkthroughs, and a direct conversation about where their old habits will clash with your way of working, such as drafting habits carried from 2D CAD into model-based work. LSC-CLT-02 · LSC-CLT-03

Second, use your own material. People learn faster from their organization's standards, templates and past projects than from generic examples, and the transfer to the job is shorter. For fixed procedures, the closer the training is to the real task, the better. Keep firm-specific workflow and standards training in-house; buy generic tool content only where it really is generic. #16 · LSC-TRF-02 · LSC-SFT-03

Teach the reasoning and deliver the steps when they're needed. The reasoning behind a code clause or an analysis method builds judgment and deserves teaching time. The click-by-click steps in a software tool change with every release and belong in a job aid inside the tool, not in anyone's memory. Teach complexity; look up specifics. LSC-DES-04 · #22

4. Practice that sticks

The single most reliable finding in learning research is that retrieval strengthens memory more than review. For technical work, retrieval doesn't mean a multiple-choice quiz. It means doing the task from memory: setting up the model, isolating the pump, completing the permit, pricing the change, then getting feedback on what was missed and trying again. Corrective feedback followed by another attempt is where much of the learning happens. LSC-PRC-01 · #19 · #60

Mix problem types when the skill is choosing which method applies. Troubleshooting a pump, diagnosing a model error or picking a contract clause all require recognizing which kind of problem you're facing. Practising one type at a time feels efficient but teaches people to apply a method without first deciding whether it fits. Interleaved practice teaches the decision. LSC-PRC-04 · LSC-TRF-07

Expect the best methods to feel worse. Practising from memory, spacing sessions and mixing problem types all lower performance during training while improving retention and transfer. Learners left to themselves will choose rereading and massed practice, because those feel fluent. Build retrieval and spacing into the programme rather than leaving them to choice, and warn learners and managers in advance that the dip in practice scores is a good sign. LSC-PRC-05 · LSC-PRC-06

Let people make errors safely. Training in which learners are encouraged to make mistakes and learn from them, in a sandbox model, a test controller or a mock tender, improves transfer to new situations. Debrief after the work, not just after the course: a short, structured debrief after a real task turns experience into learning. LSC-TRF-05 · #44 · SOP-TRN-02

Years on the job are not the same as deliberate practice. An experienced person can repeat the same habits for decades without feedback that would improve them. Engineer practice deliberately: target the specific weaknesses, give fast feedback and raise the difficulty. This matters most for senior staff learning new tools, who often keep inefficient strategies because their results still look fine. LSC-EXP-01 · LSC-EXP-02 · LSC-SFT-01

5. Judgment, decisions and AI

Much of what matters in construction, engineering and operations is judgment: deciding whether a crack is benign, whether a schedule is believable, whether to stop work. Judgment is learned by making decisions with feedback. Authentic decision simulations with structured debriefs are one of the few ways to give people that practice before the real stakes arrive. Make the decisive information salient rather than making the scene realistic, pair every game or simulation with a debrief, and add short reflection pauses during play. #61 · GL-01 · GL-05 · GL-08

Rehearse decisions under time pressure, not only with time to spare, and raise the pressure in steps. Practise short, structured call-outs for situations where information has to move quickly between people. Trust gut feel only where the cues are valid and learnable: expert intuition is reliable in familiar situations with regular feedback, and unreliable in new ones. CS-01 · CS-02 · CS-07 · CS-04

AI has changed what learning has to cover. Build universal AI fluency before specialist tracks, teach data literacy before advanced AI use, and teach human-AI collaboration rather than prompt entry alone. Most important, make AI failure detection a practised skill: train people to find planted errors in AI output, recompute numbers outside the model and check every citation. #58 · #41 · #43 · #45 · PRM-LRN-02

Guard AI tutors carefully. In a field experiment, students who practised with an unrestricted AI assistant did better while using it and worse than others once it was taken away; a guarded tutor that gave hints and checked steps, rather than answers, avoided most of the harm. Step-level feedback is what makes tutoring work. Check proficiency periodically with the AI switched off, and protect the early-career practice that used to come from routine work AI now absorbs. LSC-MOD-03 · LSC-MOD-04 · PRM-LRN-01 · #54

6. Formats, technology and myths

Choose the format by the task, not the trend. Use VR where real practice is dangerous or impossible: confined spaces, fall protection, crane familiarization, a building that doesn't exist yet. Across studies with real-world outcomes, VR worked about as well as conventional training, with a small edge for physical tasks. It's poor value for knowledge content such as standards, and in construction safety the evidence for fewer incidents is still thin. LSC-MOD-01 · IDE-MM-09 · IDE-AEC-01

Treat microlearning as a format, not a method. Short modules suit spaced refreshers and job aids; they don't suit complex judgment, and the "eight-second attention span" used to sell them is folklore. Gamification has small, conditional effects: prefer challenge, narrative and choice to points and leaderboards, and let the outcome be the score. LSC-MOD-02 · LSC-MOD-05 · GL-12

Get the multimedia basics right, because they're cheap: cut decoration and background music, put labels on the diagram rather than in a legend, break complex material into learner-paced pieces, never paste the narration onto the slide, and caption everything. Use on-screen presenters only when their gestures add information. IDE-MM-01 · IDE-MM-02 · IDE-MM-03 · IDE-MM-06 · IDE-MM-07 · IDE-MM-08

Retire the myths. "Learning styles" don't improve learning when matched. "Rewires the brain" is true of all learning, including bad learning, and proves nothing. "Only 10% of training transfers", "the 10,000-hour rule" and generational learning labels have no sound basis. Andragogy's maxims (explain why, use real problems, respect experience) are good practice, but not science, and newcomers still need structure. LSC-MYTH-01 · LSC-MYTH-02 · LSC-TRF-01 · LSC-EXP-03 · LSC-AGE-01 · LSC-EVD-01

Design for the pace of the learner, not stereotypes about age. Older trainees tend to take longer in training, yet age is essentially unrelated to job performance. Offer controllable pace, replayable demonstrations and extra practice to everyone who needs them, without stigma, but don't promise they close the gap: a 2022 meta-analysis found pacing and teaching approach didn't change age differences as expected. Diagnose prior knowledge and confidence instead of assuming, and don't mistake speed for competence. LSC-AGE-02 · LSC-AGE-04

7. By team: what learning looks like

The principles are the same across teams; what changes is what "a whole, real task" looks like and where practice can safely happen. LSC-DES-02 · LSC-DES-03

Technology and digital teams

For software and digital tools, teach workflows across tools, not isolated products, and teach the strategy behind them, not just the commands. People who learn the buttons without the strategy keep slow methods for years, because their results still look acceptable. Train with your own standards and templates, put the click-steps into job aids inside the tool, and give people a sandbox where errors cost nothing. For AI tools, teach people to brief the tool, give it sources and check its output, and practise finding planted errors. #20 · LSC-SFT-01 · #16 · #44 · PRM-LRN-02

Design and engineering teams

For engineers and designers, much of what matters is judgment and verification. Build verification habits into analysis and AI training: hand checks, mesh-sensitivity checks and load-path sanity checks, and the same scepticism toward any AI output. Graduates learn mostly from coworkers, so prepare the people they sit beside, and match development to career stage: early-career engineers need feedback and graded responsibility, principals need enough of the new tools to judge the work they sign. LSC-SFT-04 · LSC-MNT-03 · LSC-AGE-03 · DQ-AI-03

Construction and field teams

On site, the best learning happens close to the work: a worked example from this project, a supervised first task, a debrief after the pour. Retire read-and-sign as proof of competence, and use error-based scenarios for the situations crews rarely meet. Refresh skills by how fast they decay, and remember that training sticks when the workplace backs it, which means foremen and superintendents who expect the new way. SOP-TRN-01 · SOP-TRN-03 · SOP-TRN-04 · SOP-TRN-05

Plants and maintenance

For technicians, combine operational technology, data and troubleshooting in the same programme, using vendor-neutral credentials and apprenticeships where they exist. Fault-finding is a judgment skill, so vary and mix the practice: the same fault every time teaches recognition of one fault, not the skill of telling faults apart. Use VR or simulators for the hazardous tasks nobody can practise on a live unit. DM-WRK-04 · DM-WRK-05 · LSC-PRC-04 · LSC-MOD-01

Safety, emergency and crisis roles

For roles that act under pressure, practise under pressure, raising it in steps; practise the call-outs; and run exercises with unscripted injects followed by structured debriefs. Pre-brief people before stressful simulations and give them a way out, because frightened learners remember the fear, not the lesson. Practise in scenarios rather than annual click-through modules, and reward reporting rather than only avoiding mistakes. CS-01 · CS-07 · CS-09 · NIST-LRN-01 · NIST-LRN-02

Common mistakes

• Building to satisfaction scores. The methods that work best often score lower. LSC-PRC-05 · LSC-MSR-01
• One programme for everyone. Veterans and newcomers need different things. LSC-CLT-02
• Generic content for a specific job. Your own templates teach faster. #16 · LSC-TRF-02
• Leaving practice to choice. People pick rereading because it feels fluent. LSC-PRC-06
• Long gaps before first use. Learning that isn't used soon fades. LSC-TRF-03 · #2

8. Handing it on

Learn hands Apply a group of people who have practised the new work, from memory, on tasks like the real ones, with feedback, spread over weeks. Before you hand on, check three things. Has each person shown they can do a representative task without help? Do their supervisors know what they practised and what to give them next? And is there a refresher plan that carries into the first weeks of real work? LSC-MSR-03 · LSC-TRF-04 · LSC-PRC-02

Pair the training with a live project quickly. Skills that aren't used within days or weeks of learning start to fade, and the first real use is where most of the remaining learning happens. Interdisciplinary cohorts help here: when engineers, coordinators, site staff and finance learn a new workflow together, they also learn each other's hand-offs. #2 · #47 · LSC-TRF-03

For small organizations, none of this needs a learning platform. A worked example from your own files, a half-finished version for the learner to complete, a check against your own standard and three short refreshers in the calendar will outperform most purchased courses. #17 · #16 · LSC-CLT-01

The checklist. Build on whole, real tasks. Diagnose prior knowledge and run two tracks. Show, then fade. Practise from memory with feedback and another attempt. Space refreshers at about one, three and eight weeks. Mix problem types for judgment. Expect the best methods to feel harder. Let people err safely. Simulate decisions and debrief them. Guard AI tutors and test with AI off. Choose formats by task, and retire the myths. Then go to Apply.