Monday, March 26, 2012

Avoiding half-assed knowledge management flops « ResonanceBlog

Knowledge management is part of most social business initiatives. Equipping employees, partners, suppliers and customers with knowledge to smooth operations makes complete sense – from building FAQs and content for use by customer service agents, to crowdsourcing ‘how tos’ from customers. We all know intuitively that the gathering, sharing and distribution of knowledge is important.
The trouble is, we tend to stop there; hence a bunch of failed knowledge management initiatives throughout the 90s to today.
The fact is, an estimated 70% of workplace learning is informal. Just because you post something somewhere on a technology platform doesn’t mean anything is going to change – not when the knowledge isn’t used and supported by people telling stories, by trial and error, by inexperienced people watching more experienced people, by constant coaching, by developing new products and practices off the back of it.
When looking at the capture and dissemination of enterprise knowledge as part of a social business strategy, an intranet revamp, or an HR initiative, considering the unbudgeted, unplanned, uncaptured tacit knowledge is the missing piece of the puzzle that will mean the difference between success and failure. This typically means stretching out the responsibility of whoever is contributing a piece of knowledge – to ensure they’re also responsible for embedding it in the organisation beyond uploading a file.
The final missing piece is philosophy, vision and values – i.e. not just what you know, but the way you see the world. So many organisations try to take knowledge and working practices from other successful companies and emulate them. Look at how many have attempted to copy the Toyota Production System (TPS); yet somehow, it doesn’t work. Why? Because TPS is a philosophy. It’s a perspective, a way of seeing the world, a way of thinking about quality, processes and people; not just a set of techniques.



Avoiding half-assed knowledge management flops « ResonanceBlog

No comments:

Post a Comment