Knowledge Sharing and Transfer

A classic Knowledge Management problem for in-house teams is how to access tacit institutional knowledge from long-serving team members. 🤔 If you've worked in an in-house team that's been around for even a short while, you'll know that a significant amount of the inner workings of how the team operates and interacts with the business is stored in the heads of a few individuals. This knowledge can range from the weird and wonderful to super relevant and insightful context that can shine a light on bizarre deals and confusing decisions. Often, this knowledge is most useful for fast decision-making and continuity of operations. ⚙️ From a management perspective, you have to ask: what happens to this knowledge when these team members leave or retire? And how do we ensure other team members can operate effectively by having access to this information without constantly needing to consult their more experienced colleagues? 🤔 It’s crucial to proactively manage this risk and opportunity by systematically capturing and disseminating this knowledge across the team. You could consider the following for you team: Structured Knowledge Audits: Regularly conduct interviews or workshops with long-serving team members to document processes, insights, and decision-making criteria that are often not written down. These sessions should be structured to dig deep into the "why" behind certain practices, not just the "what" or "how." 📝 (Probably don't call them 'audits' and make sure your colleagues understand why you're doing them) Mentorship and Cross-Training: Encourage mentorship programs where senior team members actively share their knowledge with newer colleagues. Additionally, cross-training team members on different roles and responsibilities can ensure that knowledge is spread across the team, reducing dependency on any single individual. 👥 Centralizing Knowledge: Almost every KM topic comes back to this, but consider where and how you can centralize your documented knowledge so it is easily accessible. Start small and strategically, but start somewhere and with a commitment to maintaining what you've done. 📚 #LegalOps #KnowledgeManagement #Law #Legal #Business

In many AEC firms, specialized knowledge accumulates around a single person. They become the go-to expert, the one everyone relies on. Over time, that expertise becomes central to how work gets done. That was the context at Boulder Associates. They had a senior medical planner, Kate, who had developed a set of powerful tools to help support her project work. Naturally, she became the person everyone turned to for guidance. The opportunity was clear: how could that knowledge be shared more broadly so others could grow into it and contribute at a higher level? Todd Henderson, Director of Practice Improvement, started by breaking the work into smaller pieces. Each of her custom tools was assigned to another planner. Their job wasn’t just to use it, but to understand it deeply—at a “Kate-like level.” They interviewed her, studied how the tools worked, and then presented short internal “MED Talks” to their colleagues—explaining what the tool does, when to use it, where its limits are, and when to go deeper. There was one rule: Kate couldn’t present. Each presenter became the steward of a specific tool. Over time, a broader network of expertise has started taking shape—people connected to particular tools, confident in how they worked, and able to support others. And something else happened along the way. By teaching the tools, these planners didn’t just learn them—they internalized them. They became visible contributors. The “nextperts” emerged: people who could support the work, evolve it, and extend its reach. Meanwhile, Kate was able to step into a more elevated role—coaching, guiding, and continuing to advance the work. This is what modern learning organizations do well: create simple, intentional ways for knowledge to be shared, practiced, and carried forward by others. 📺 🎧 This clip comes from “Partnering with AI to Solve Knowledge Problems,” episode 7 of our Welcome to KM 3.0 series with the TRXL podcast. You can watch or listen here: https://lnkd.in/gBP3-JPa 📖 I also mentioned this story in “Overcoming the Unspoken Barriers That Keep AEC Experts From Sharing What They Know”, issue 16 of the Smarter by Design Newsletter. You can read it here: https://lnkd.in/gWB8vHTM #AEC #KnowledgeManagement #ModernLearningOrganizations

We often talk about technical debt in software teams, but have you ever considered 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗱𝗲𝗯𝘁? 👀 It’s the hidden cost of undocumented or inaccessible know-how in a growing company. In my experience, teams feel this pain daily, even if they don't have a name for it. 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗗𝗲𝗯𝘁? Knowledge debt is the backlog of important information that hasn’t been documented or shared widely. At first, a little tribal knowledge might seem harmless—everyone just asks Alice for deployment steps or Bob for tricky client questions. But that ends when Alice is on vacation or Bob leaves. Just like technical debt, knowledge debt accumulates "interest." Every time we postpone writing a how-to guide or skip recording the "why" behind a decision, we create knowledge debt by borrowing against future productivity. Rushing a project without docs is like a short term hack in code—it works for now but leaves everyone struggling later. 𝗧𝗵𝗲 𝗜𝗺𝗽𝗮𝗰𝘁 𝗼𝗳 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗗𝗲𝗯𝘁 ❌ 𝗪𝗮𝘀𝘁𝗲𝗱 𝘁𝗶𝗺𝗲 𝘀𝗲𝗮𝗿𝗰𝗵𝗶𝗻𝗴: We lose around 1.8 hours a day searching for info—nearly a full day per week even for a small team! ❌ 𝗢𝗻𝗯𝗼𝗮𝗿𝗱𝗶𝗻𝗴 𝗰𝘂𝗿𝘃𝗲: Relying on “ask Joe” for information slows down onboarding, estimated to cost companies millions in lost productivity. ❌ 𝗗𝗲𝗹𝗮𝘆𝗲𝗱 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀: When information is hard to find, decisions come to a stall. 68% of companies face project delays from missing info. ❌ 𝗥𝗲𝗶𝗻𝘃𝗲𝗻𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝘄𝗵𝗲𝗲𝗹: Nearly 59% of R&D and product teams later discover the expertise or project they recreated already existed within their company. ❌ 𝗙𝗿𝘂𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝗰𝗵𝘂𝗿𝗻: 81% of employees feel frustrated when they can’t access the info needed to do their jobs, which can erode morale and push talent to leave. 𝗧𝘂𝗿𝗻𝗶𝗻𝗴 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗗𝗲𝗯𝘁 𝗶𝗻𝘁𝗼 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗖𝗮𝗽𝗶𝘁𝗮𝗹 ✅ 𝗖𝘂𝗹𝘁𝗶𝘃𝗮𝘁𝗲 𝗮 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗰𝘂𝗹𝘁𝘂𝗿𝗲: Use internal wikis or docs and lead by example—record key decisions and insights. ✅ 𝗕𝗿𝗲𝗮𝗸 𝗱𝗼𝘄𝗻 𝘀𝗶𝗹𝗼𝘀: Host brownbag sessions, circulate newsletters, and rotate team members across projects to share knowledge. ✅ 𝗠𝗲𝗻𝘁𝗼𝗿𝘀𝗵𝗶𝗽: Pair newcomers with veterans to transfer implicit undocumented knowledge. ✅ 𝗧𝗿𝗲𝗮𝘁 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗮𝘀 𝗮𝗻 𝗮𝘀𝘀𝗲𝘁: Designate “knowledge champions” or host Documentation Days to regularly “pay down” your debt. This pays off not only with the team, but also with the coming of AI agents who can utilize this knowledge to reliably and accurately get things done. ✅ 𝗠𝗮𝗸𝗲 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝘀𝗲𝗮𝗿𝗰𝗵𝗮𝗯𝗹𝗲: Invest in tools that unify scattered information. Paying off knowledge debt turns a liability into an asset. When your team's know-how is documented and accessible, you build 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗖𝗮𝗽𝗶𝘁𝗮𝗹! New hires get up to speed faster, teams feel unblocked to do their best work, and learnings compound across projects.

Imagine calling training a success when no one uses it on the job. Have you? Most people do not fail the training. They fail to apply it. About 85% of training never gets used on the job. Not because the content was bad. Not because the learner was not engaged. Because learning and doing are two very different things. We have built entire Learning & Development systems around consumption. Videos. Workshops. Courses. Certifications. But knowing something is not the same as doing it. The real gap is not knowledge. It is transfer. Here are 5 ways to actually close it. 1️⃣ Replace content with reps: Stop adding more modules. Build in deliberate practice. Repetition under real conditions is what creates retention. 2️⃣ Make managers part of the design: If a manager does not reinforce it, it dies. Loop them in before the training, not after. 3️⃣ Create accountability structures: Peer check-ins. Follow-up commitments. Application goals. Without accountability, good intentions evaporate. 4️⃣ Shrink the time between learning and doing: The longer the gap, the more fades. Give learners a chance to apply within 48 hours of any session. 5️⃣ Measure behavior, not completion: Finishing a course proves nothing. What changed on the job? That is the only number worth tracking. Active learning feels productive. Active practice is what actually changes performance. Your learners do not need more content. They need more reps. AI makes this matter even more. When information is everywhere and content is easier than ever to generate, the real advantage is not access to knowledge. It is the ability to apply it. Statistic source: The Institute for Transfer Effectiveness ——— ✦ ——— More on AI for Workforce Transformation → Janet Perez

🚀 Why Can’t We Wait 30 Years to Learn a Lesson? I was looking at my motorcycle's front brake lever the other day. Notice the cut near the end? That’s not a defect — it’s a design choice. 👉 In case of a crash, only the tip breaks off. The rider can still brake or accelerate. 👉 It’s a safety notch — a lesson learned from decades of motorcycle accidents. But here’s the catch: It took the industry 20–30 years to standardize this simple idea. Why so long? - In the 1960s–70s, riders kept losing levers in crashes, but every OEM solved it in isolation. - A racer in Japan might benefit from the notch, while a European manufacturer was still “re-discovering” the same problem years later. - There was no global lessons learned system, no instant sharing. - Regulators didn’t demand it. Customers didn’t ask. - So the same failure kept repeating — like students making the same exam mistake year after year — until finally, in the late 80s–90s, it became a standard. ⏩ Fast forward to today: We cannot afford this kind of delay. In Project Management & Product Development, the speed of learning is now as critical as the speed of innovation: - Project Timelines & Risk: Every repeated failure is added risk. If a welding defect in one program isn’t shared quickly, entire launches can slip. - Knowledge Transfer: Gate reviews (Stage-Gate, V-Model, Agile PI planning) aren’t just approvals — they’re transfer points for lessons learned. - Preventing Repeat Failures: A defect in one EV battery project must instantly update DFMEA libraries so future programs don’t repeat it. - Cross-Functional Impact: Lessons must flow to design (specs), manufacturing (PFMEA), suppliers (APQP), and program managers (risk logs). - Continuous Improvement: Every project isn’t just delivery — it’s an upgrade to the company’s collective memory. 💡 The real question is no longer: “Did we fix it?” But: “How fast did we spread the lesson so it never repeats?” 🔥 Designing products is important. But designing the learning system around products is what creates resilience. #QualityManagement #ProjectManagement #LessonsLearned #ContinuousImprovement #Leadership

High-quality code makes your work short-lived. Poorly written code ensures the company will always need your help. 😜 Funny — yet many people still follow this mindset. Here’s the hard truth: Across my career, from freshers to senior leaders, I’ve seen professionals who deliberately complicate work, avoid documentation, refuse to share knowledge, and quietly build a dependency around themselves. It’s not incompetence — it’s strategy. A strategy that slows teams down, breeds silos, and creates a dangerous single point of failure. And while it may offer short-term “job security,” it kills long-term team health, innovation, and trust. For leaders, these situations are the most challenging because the person often looks productive on the surface. But behind the scenes, the team becomes fragile, and delivery risks multiply. In engineering, we avoid single points of failure in systems. We should avoid them in people too. 💡 Hard-Hitting Tips for Leaders to Fix This 1️⃣ Make knowledge sharing non-negotiable Mandate documentation, code reviews, and walkthroughs. If knowledge lives only in someone’s head, that’s a risk — not a strength. 2️⃣ Remove dependency incentives Reward collaboration, not silo-building. Make team outcomes matter more than individual heroics. 3️⃣ Rotate responsibilities Let others touch the “critical” areas. If someone resists, that’s a red flag — not loyalty. 4️⃣ Build a culture where transparency is expected Open communication, shared ownership, and regular alignments reduce the power of hidden information. 5️⃣ Address the behaviour early Silence is approval. The longer you let it grow, the harder it becomes to fix. 6️⃣ Make it safe for others to speak Often the team knows who the blocker is — but they need psychological safety to raise concerns. 7️⃣ Lead by example Leaders who share knowledge freely create teams that do the same. Healthy teams grow when knowledge flows. Strong leaders rise when they dismantle silos. And real progress happens only when success is shared — not hoarded. #Leadership #TeamWork #EngineeringCulture #TechLeadership #TeamDynamics #OrgCulture #KnowledgeSharing #GrowthMindset #PeopleManagement #LeadershipTips #CriticalResource #SoftwareEngineering #MunnaPrawin #BUMI #SmartLife

Training doesn’t transfer... People transfer...under conditions we create We’ve spent decades studying transfer Meta-analyses, Models, Post-course surveys Yet variability on the floor persists A peer-reviewed study (Wisshak et al., 2024) finally shifts the lens... not to learners, not to managers...but to trainers’ professional knowledge of transfer itself. Based on a cross-sectional sample of 339 trainers and grounded in established transfer research, the finding is simple and uncomfortable... Most trainers are never trained in how transfer actually works as a system. 🚨 The 3-part system Transfer knowledge is not generic good facilitation... It has three separable components 1️⃣ Learner conditions Do people leave with confidence, intent, and clarity to apply, not just knowledge? 2️⃣ Training design Was practice realistic, spaced, feedback-rich, and tied to real operating constraints? 3️⃣ Work environment Are supervisors aligned? Is there time to apply? Is use expected, noticed, and reinforced? 🔎 Micro Case Study A site retrains on a revised Lock-Out, Tag-Out process. The content is sound. But the next shift is short-staffed. Supervisors prioritise throughput. The system teaches people what really matters. Question for Leaders... Where have you seen technically sound training still fail on the floor, and why?

Your most experienced lawyer just gave notice. Suddenly, nobody knows where anything is. The panic that follows: "Where did she keep the template agreements?" "How do we handle IP assignments for contractors?" "What was our position on that regulatory issue?" "Who has the login for the trademark filing system?" This scenario happens at every company. Senior legal talent leaves, and institutional knowledge walks out the door with them. The real cost: junior lawyers spending weeks recreating work that already existed, making mistakes that were already solved, and reinventing processes that were already optimized. Most legal teams store knowledge in three places: -- Individual lawyers' heads -- Email threads from 2019 -- Folders buried in shared drives When knowledge is trapped in people instead of systems, every departure is a crisis. Here's how winning legal teams prevent this: → Document standard processes and decision trees → Create searchable templates and clause libraries → Maintain decision logs for recurring issues → Build internal playbooks for common scenarios → Record the "why" behind policies, not just the "what" The goal: any lawyer should be able to handle any issue with access to the right information. Knowledge management feels like busy work when you're overwhelmed. But losing a key team member without proper documentation feels much worse. Start small: document one process this week. Your future self (and your team) will thank you. How does your legal team capture and share institutional knowledge? What happens when someone leaves?

I’ve been reflecting on how much time I am investing in my #ProfessionalDevelopment, and how to best support our #LearningCulture within Prosci, especially with tight budgets and resource constraints. Here are some of the low to no-cost, highest-ROI strategies ideas I’ve found to be effective. I’d love to hear what’s been working for you! 🎯 Create a learning plan with very clear objectives. I personally love using our individual change #ADKAR framework for this. AWARENESS (recognize the need for improvement - why does this matter?); DESIRE (your individual dedication and motivation to do the learning - why does this matter for me?); KNOWLEDGE (specifics on how you will gain the skill, e.g., training, peer learning); ABILITY (plan for practice - how will you demonstrate and apply new knowledge?); and REINFORCEMENT (ensure sustainability - what steps will you take to maintain results?). 🔗 Partner up internally. Can your finance team teach project managers how to measure ROI? Could marketing help HR with engagement strategies? These internal "barter" arrangements often unlock surprising value. ☕ Encourage knowledge-sharing. Create spaces where teams can share challenges and solutions. Not only does this build skills, but it also strengthens cross-team relationships that improve execution. Whether through internal online forums, lunch-and-learns, or mentoring, the more people share what they know, the more it multiplies. ✋ Tap into your organization’s experience. The person who led a similar project three years ago could be your best resource today - no budget needed. I'd encourage you to be a bit #vulnerable and ask for support where you know you don't have all the answers. 🤖 Leverage free AI tools. AI can accelerate learning and can offer immense value when used creatively. AI tools like language models (e.g., ChatGPT) can provide instant answers to questions, explanations of complex concepts, or help with brainstorming ideas. Want to create a personalized learning plan on a new #skill or #competency? It's brilliant. ⏲️ Make time. I know this one can be tough, but I’m committed to creating time for learning—whether it’s blocking out "learning hours" in my calendar, dedicating time during team meetings, or making weekend chores more productive by listening to a #LinkedInLearning course at the same time as I weed the garden. It's a small investment that pays dividends over time. #ResourceOptimization #KnowledgeSharing #AILearning #CapabilityDevelopment

In discussing modern team dynamics with a client this week, four major knowledge problems emerged: uncertainty, complexity, ambiguity, and equivocality. These intersect in ways that can stymie teams: Uncertainty: The unpredictability or lack of information Complexity: The interplay of numerous components makes situations hard to decipher. Ambiguity: Multiple interpretations of information affecting decision-making. Equivocality: Conflicting interpretations leading to team confusion. It is easy to gloss over these terms without profoundly understanding them, leading to surface-level interpretations and weak solutions. To address these challenges: FOSTER TEACHING & MENTORSHIP: PRINCIPLE: Never assume everyone knows what you know at the level you know. TIP: Promote knowledge sharing through workshops, sharing sessions, or mentorships. PROMOTE CURIOSITY & CONTINUOUS LEARNING: PRINCIPLE: Never assume you know all there is to know. TIP: Maintain a continuous learning attitude. Encourage questions like, “I am unsure, what are your thoughts?” ENCOURAGE DEEP UNDERSTANDING & CRITICAL THINKING: PRINCIPLE: Never confuse knowing with understanding. TIP: Ensure teams delve deeply into topics, using case studies or role-playing tools to cement knowledge. Implementing these strategies ensures thorough knowledge accumulation and understanding, elevating team performance. ONWARD!