Apprenticeship Knowledge Transfer Methods

Think about that one person on your team. The veteran superintendent. The master estimator. The senior PM. Four decades of “how we really get it done” live in their head. Tomorrow, they might hang up the hard hat and go fishing for good. Will that know-how leave with them? Too many construction firms respond with last-second panic. Panic is not a plan. Run this 3-Point Knowledge-Transfer Check this week: 1️⃣ Mentorship Who are your senior pros actively mentoring? Is there a clear right-hand apprentice soaking up their decision-making process? 2️⃣ Process Capture How are you recording their shortcuts, vendor insights, and “in-case-of-emergency” fixes? Is that wisdom turning into a living playbook or staying in someone’s head? 3️⃣ Strategic Hiring When you onboard new talent, do you pair them with veterans on purpose? Are you scouting coachable rising stars ready to inherit the baton? Ignore this and you’ll spend the next decade re-learning costly lessons your veteran could have explained over coffee. Bake that knowledge into your company’s DNA before the boat leaves the dock. #construction #bluecollar #trades #constructionlife #contractors #constructionbusinessowner The Contractor Consultants

I had another reminder this weekend that learning is learning, regardless of the developmental stage. This card was in my daughter’s latest Lovevery box. It was designed for parents of children around 4 years old. It illustrates the "gradual release of responsibility" model - learners progress through scaffolded stages of observing an expert model, practicing with support, then applying skills independently. Mastery comes from actively engaging as guidance fades. This approach reminds us that simply telling isn't enough for developing competence. We need learning and apprenticeship models ranging from highly directive techniques early on ("I do, you watch") to non-directive coaching as learners gain experience ("You do, I'll be here if needed"). For managers, trainers and mentors, intentionally structuring learning paths with this transparent progression enhances engagement and skill transfer. It aligns with theories like cognitive apprenticeship and Vygotsky's Zone of Proximal Development by meeting learners where they are. Whether upskilling a new manager or onboarding engineers to a complex coding stack, starting with modeling and scaffolding towards autonomy cultivates self-sufficiency. I was struck that this simple visual for parenting holds so many implications for the professional sphere as well. How have you applied these principles to workplace learning? How does this model show up in your organization? #coaching #learninganddevelopment #traininganddevelopment #workplacelearning

Your best consultant just rolled off the client engagement. So did everything they knew. Your client has the documentation. The training materials. The system running perfectly. What they don't have: the context that makes any of it work. Why the workaround exists for the legacy integration. Which stakeholder actually approves exceptions. What "urgent" means to their finance team vs their ops team. The invisible knowledge your consultant carried in their head. Three weeks later, your client hits an edge case. They dig through the docs. Find nothing. Email your team. Your junior consultant guesses. The client starts doubting they can run this without you. Your renewal conversation just got harder. Most PS firms treat handoffs like a documentation problem. Write better docs. Record more videos. Build bigger wikis. Then wonder why clients still can't operate independently. Knowledge transfer isn't a documentation problem. It's a relationship problem. Here's what actually works: 1️⃣ Identify the client champion in week 2, not week 10 → Most teams wait until the end to figure out who owns this after handoff → Flipped approach: Week 2, identify who's owning this long-term → Loop them into every decision, every trade-off discussion → They don't just learn what you built. They learn how you think. 2️⃣ Keep a living decision log → Not documentation of what you built → A running record of what you decided and why → "We chose async processing because their batch window closes at 2am" → Six months later, they understand the constraint without calling you 3️⃣ Shadow in reverse during the last two weeks → Typical handoff: Client shadows your consultant → Better handoff: Your consultant shadows the client → Client drives. Consultant observes and corrects only when necessary. → Handoff worked when the client stops needing corrections. 4️⃣ Schedule the "stupid questions" session → Two weeks after go-live, when you're officially done → "Bring every question that feels too basic to ask" → These reveal gaps in your knowledge transfer → Client asks them now instead of quietly struggling for months The PS firms with the best renewal rates don't just deliver solutions. They deliver clients who can own those solutions after they leave. ♻️ Share this with a PS leader rethinking how knowledge transfers 💬 What critical context almost didn't make it to your client's team? ➕ Follow me (Maxime Saporta) for more on building scalable Professional Services practices

Stop calling it continuous improvement if lessons keep disappearing. Real improvement depends on shared lessons. Knowledge is created every day. But too much of it disappears. Knowledge Management is Part 7 of 8 In building a Culture of Continuous Improvement. This is how improvement becomes repeatable. Not heroic memory. Not lucky timing. Not hallway conversations. Captured lessons. Shared methods. Easy access. Here is where many organizations struggle: → Lessons stay inside one team → Good fixes are hard to find → Experience leaves with employees So what happens next: → Teams solve the same problem twice → New people start from zero → Improvement stays slow and uneven Here is what strong organizations do differently: → They document lessons after key projects → They make knowledge easy to search → They share practices across teams *** 1️⃣ Systematize lessons learned Experience alone is not enough. It only helps when it is captured. → Hold post-project reviews every time → Write down what worked and failed → Store lessons in one place Then make it useful: → Sort lessons by topic → Use clear and simple language → Link lessons to daily training So teams can apply them fast: → Fewer repeated mistakes → Faster onboarding → Better decisions every day Ask this: How many recent projects left useful lessons behind? *** 2️⃣ Share best practices across teams One team learning is not enough. The whole organization should benefit. → Build one shared practice library → Schedule cross-team learning sessions → Track where ideas get reused Make sharing normal: → Show examples that worked → Invite teams to teach others → Recognize teams that share openly So knowledge can travel: → Good ideas spread faster → Teams avoid starting over → Improvement scales across departments Ask this: Can one team use another team’s solution today? *** 3️⃣ Preserve collective wisdom Organizational memory is a real asset. It should not walk out the door. → Use knowledge transfer in offboarding → Capture expert methods before they leave → Keep standards as living documents Then strengthen the system: → Update documents often → Surface hidden tribal knowledge → Make ownership clear So wisdom stays in the business: → Less dependence on a few experts → More stability during change → Stronger long-term capability Ask this: What knowledge would vanish if key people left? *** A strong example comes from NASA. After the Challenger disaster, NASA built a lessons learned system. It captured and shared knowledge at scale. The result: → Thousands of lessons stored → Better access to past learning → Fewer repeated mistakes Because improvement should not depend on memory. When knowledge is captured and shared, learning becomes part of the system. That is how improvement lasts. *** 🔖 Save this post for later. ♻️ Share to help others build a better CI culture. ➕ Follow Sergio D’Amico for more on continuous improvement.

Believe it or not, one conversation is still tickling the back of my brain from November at Connected Claims USA... We're facing a critical inflection point in insurance: a mass exodus of expertise just as our workforce becomes more distributed than ever. Those invaluable "coffee machine moments" where junior adjusters learned from veterans? The overheard conversations that taught us unwritten rules of claims handling? They're vanishing in our hybrid world. But here's what excites me: innovative carriers aren't choosing between remote work and knowledge transfer – they're reimagining both. I'm seeing: - AI-powered mentorship platforms matching veterans with newcomers across time zones - Virtual reality simulations recreating complex claims scenarios - Digital "listening posts" where institutional knowledge is captured and shared - Hybrid collaboration spaces designed specifically for knowledge transfer The most successful organizations understand that technology alone isn't the answer. It's about creating intentional moments for connection, whether virtual or physical. From my conversations with industry leaders, the winners this year won't be those who simply throw technology at the problem. Success will come to organizations that thoughtfully design environments that preserve our industry's collaborative essence while embracing modern workforce demands. What innovative approaches is your organization using to bridge the knowledge-sharing gap in this evolving landscape? Share your wins (or challenges) below! #InsuranceInnovation #KnowledgeTransfer #InsurTech

When participants are to apply what they have learned, it is not enough for them to simply acquire knowledge in training. Because knowing is not the same as doing. Learning how to do something involves extracting rules from the process. Factual knowledge can help, because it shows us where to find promising alternative courses of action. Communicate such declarative knowledge (knowing that) so that the helpful facts leave deep marks in the memory and are thus easily recalled and also retained for a long time. The way to accomplish this is to have trainees work with the content themselves. So, dispense with long lectures and give preference to modules that are active, personally relevant to the trainees, and have some emotional color or content! However, laying the basis for long-term retention of facts is only the first step. In order to make factual knowledge applicable, it must be proceduralized – that is, “knowing that” must become “knowing how.” And that requires learning by doing. In practical exercises and experimentation, trainees automatically extract the rules covering each step in making an action successful in all its complexity. Our brain is a pro in extracting rules. All we have to do is give it the opportunity to play around and fine-tune the rules based on practice, reflection, and experience. For effective learning in the context of mastering how to do something, it is necessary to combine all four learning modes (reflection, theory, exercises/experimentation, and practical experience). Let us not be influenced by time pressures or by our own preferences for theory-laden training, which turns our trainees into knowers, but not into doers. Let’s stick to the rule of thumb for transfer-effective training: schedule at least 30 % of the training time for active practice! #maketransferhappen

Joined a new team but not getting proper KT (Knowledge Transfer)? Don’t wait passively. Take initiative and make your KT period more valuable, faster, and more efficient. Here are 9 practical things that actually work: 1) Lower the barrier Create a “2-week no-judgment question zone.” Ask even the dumbest questions early. Clearing social anxiety speeds up learning. 2) Request micro-sessions Instead of vague 1-hour KT calls, ask for 15-minute single-topic sprints. Busy teammates are more likely to say yes. 3) Document as you go Offer to clean up or update messy team docs. This gives you a natural reason to ask questions while adding immediate value. 4) Record the screen During ad hoc help, ask: “Mind if I record this?” You’ll build your own learning library and avoid asking the same thing twice. 5) Follow the “Validate, don’t ask” rule Instead of: “How does this work?” Say: “I think it works like this — is that right?” It’s easier for others to correct than explain from scratch. 6) Find the recent hire Talk to someone who joined 6–12 months ago. They still remember the struggle and usually have the best survival notes. 7) Shadow silently Ask to “ride along” on a task. They don’t need to teach actively — you simply observe, take notes, and learn the workflow. 8) Use the 30-minute limit If you’re stuck, try for 30 minutes max, then flag it. Don’t lose an entire day just trying to be polite. 9) Frame it as speed Tell your lead: “I want to become productive faster, but this is currently my bottleneck.” Now it sounds like a performance goal, not a complaint. The best KT often comes from the learner’s initiative, not the trainer’s availability. What’s one KT strategy that helped you ramp up faster in a new team? #CareerGrowth #LearningAtWork #KnowledgeTransfer #Productivity #NewJob #WorkplaceTips #ProfessionalGrowth #LinkedInTips

We are already seeing evidence that AI is fundamentally changing entry-level jobs. It’s automating the routine tasks—but it’s also forcing a critical question: How do we build the next generation of leaders when their traditional training ground is shifting? For years, I’ve advocated for reviving the lost art of apprenticeship. Historically, junior employees learned the ropes by doing the "scaffolding" work—research, data cleanup, and early drafting. With GenAI absorbing these tasks, that default learning mechanism is gone. In a new piece, my colleagues Sandra Durth, Dana Maor, and Sophie Underwood highlight that in an AI-enabled workplace, we can no longer rely on learning by osmosis. Instead, we must intentionally design work to be developmental. This requires adapting modern apprenticeship for the agentic age: 1️⃣ Shift to "Cognitive Apprenticeship": Senior leaders must make their thinking visible. It’s no longer about showing how to do a task, but modeling how to frame the right questions, challenge AI outputs, and navigate ambiguity. 2️⃣ Accelerate Exposure: Don't just give junior talent the "leftovers" of automated workflows. Use the time freed up by AI to pair them with senior experts on complex, real-world problems earlier in their careers. 3️⃣ Embrace Co-learning: Apprenticeship is no longer strictly top-down. With everyone learning to navigate AI simultaneously, the obligation to teach and learn must be shared across all levels. The transition to an AI-enabled workplace won't automatically create better leaders. That requires deliberate design and a commitment to continuous apprenticeship. How is your organization adapting its early-career development? 👇 🔗 Read the new insights on early-career talent: https://lnkd.in/dMAC9WFc 🔗 Revisit our piece on the art of apprenticeship: https://lnkd.in/e8krGFZx #FutureOfWork #Apprenticeship #LeadershipDevelopment #GenerativeAI #TalentStrategy #McKinsey

Cognitive Apprenticeship was built around one move: make the expert's invisible thinking visible. AI's most interesting property is that you can force it to do exactly that — on demand, at length, every time. The apprenticeship move and the AI move are the same move. For thirty years, Articulation was the framework's hardest step. Schoenfeld had to coax mathematicians to think aloud. Palincsar trained teachers in the predict-question-clarify-summarize cycle. The heuristic and control strategies of experts were mostly tacit. Now AI articulates by default — flawed, fluent, and recorded. That changes the economics of the framework. Modeling and Articulation, which used to be the labour bottleneck, are now cheap. Coaching is more available than ever. The two moves that do not get cheaper — Reflection and Exploration — are now where the educator's craft concentrates. AI may make expert thinking visible and may serve as a dedicated Articulation partner, but the learner must do the noticing — the comparison between their reasoning and an expert's, and the decision about what to change next time. Try this week: ask AI to think aloud through a domain task you would normally model yourself. Give students the transcript and ask them to find three places where a practitioner would have reasoned differently. Auditing is itself expert practice. AI's confident wrongness is excellent material. What would your students notice that the model missed? — P.S. Sketchnote of the 6 methods + handbook PDF (with the AI-transcript audit protocol) in the first comment. Follow daily on Pedagogy + AI: https://lnkd.in/dreyd5UT #PedagogyAndAI #LearningDesign #AIInEducation #InternationalSchools