{"id":1784,"date":"2025-05-03T19:47:10","date_gmt":"2025-05-03T17:47:10","guid":{"rendered":"https:\/\/blog.eweibel.net\/?p=1784"},"modified":"2025-05-03T20:59:39","modified_gmt":"2025-05-03T18:59:39","slug":"knowledge-transfer-in-times-of-technology-change","status":"publish","type":"post","link":"https:\/\/blog.eweibel.net\/?p=1784","title":{"rendered":"Knowledge Transfer in Times of Technology Change"},"content":{"rendered":"\n

Let\u2019s face it: Technology changes in software development aren\u2019t rare events, they\u2019re practically the background noise of our industry. Especially in the evolving .NET world<\/a>, where frameworks, tools, and deployment models are constantly shifting, staying on top means more than just learning new tools or technologies. It means preserving, sharing, and actively managing knowledge before it walks out the door or gets buried in yesterday\u2019s code.<\/p>\n\n\n

\n
\"\"<\/a><\/figure>\n<\/div>\n\n\n

Because here\u2019s the kicker: Much of your team\u2019s know-how isn\u2019t in a shared wiki, it\u2019s in someone\u2019s head. And when that someone leaves or gets hit by the proverbial bus<\/a> (or just takes a vacation), the knowledge gap becomes painfully real. While tools like wikis do exist, they\u2019re often neglected due to time pressure or simple lack of prioritisation. \u201cWe\u2019ll document it later,\u201d they say and then, of course, never do.<\/p>\n\n\n\n

So, the big question is: How do we organise knowledge transfer in a way that makes technology transitions a source of innovation, not a sinkhole of lost expertise? This post highlights the key insights from my Executive MBA<\/a> thesis on knowledge management during technology change and offers practical guidance for leaders and software architects. I spoke with internal and external experts, and surveyed team leads at a Swiss software SME to gather hands-on perspectives.<\/p>\n\n\n\n

Beneath the Surface Problems: What Leaders Are Saying<\/h2>\n\n\n\n

Within teams, knowledge transfer tends to run reasonably well, thanks to meetings, mentoring, documentation (when it\u2019s maintained), and good old on-the-job training. But when it comes to sharing knowledge across teams? That\u2019s where things fall apart. Just 11% of team leads called cross-functional exchange \u201cgood.\u201d The remaining 89% flagged it as an area needing serious attention.<\/p>\n\n\n\n

Wikis are in place, that\u2019s the good news. The bad? Their content is often outdated, incomplete or simply not useful. Much of the real knowledge stays locked in the heads of a few seasoned developers. The main obstacles? No time, few structured formats for sharing, lack of motivation to write things down, and sometimes outright resistance to new tools and technologies.<\/p>\n\n\n\n

What drives people to share their knowledge anyway? Simple: Feeling appreciated and seeing that it actually helps someone. Recognition and visible impact, those are the magic ingredients.<\/p>\n\n\n\n

What Leaders Can Actually Do About It<\/h2>\n\n\n\n

First things first: Make knowledge management a strategic priority, not just a \u201cnice-to-have.\u201d Set specific knowledge goals and track progress. That could mean counting updated wiki pages, completed online courses or team certifications. What matters is that you measure what you want to improve.
Then, roll up your sleeves and implement targeted measures on the ground:<\/p>\n\n\n\n