Looking under the streetlamp for the keys
Stop looking in the convenient places, and do the hard work.
There is a funny story that goes something like this:
Coming home late one night, you notice a distraught-looking person who is clearly looking for something.
When you ask, "What have you lost?" He tells you he's dropped his keys and cannot get into his house without them.
You then ask where he dropped his keys, and he indicates "over there." The natural reply is, "So why look here."
"The light is better" under the streetlight.
I've come across this story in a variety of fashions, but the gist is that it doesn't do much good to look for a solution where the answers are obvious when the problem is really somewhere else.
Leandro Herrero's The Leader with Seven Faces makes reference to the story and uses an anecdote about knowledge management to illuminate it further. A KM leader admits that the hardest part of knowledge management is making the change happen amongst people. But, since that is so difficult, they didn't do that. Instead, they spent millions on a fancy IT system.
The other recent reference was more obscure, but came down to the same thing. In talking with a colleague about certification for Theory of Constraints, he raised the idea that while training and certification were certainly useful, most of TOC implementation has nothing to do with the technical aspects of TOC. It's about the people.
3 Comment(s)
Is it happenstance? The more we evaluate the performance (or lack thereof) of employees, the more the operative question remains the same -- " Are companies hiring employees with the right job fit?". The IT illustration of developing a system around employees is a cogent example -- would it be ultimately less expensive and more productive in the long term to hire employees who fit the needs of the organization rather than continuing to patch and bandaid operating and IT systems?
I like this line of questions:
* What's the business problem?
* What is the power of the change?
* How is the change going to remove / diminish the problem?
* What do we need to stop doing when we make the change?
* What new things do we need to start doing when we make the change?
I'll leave it to the readers to consider where most efforts stop in this line of questioning.





Here's a "manual" trackback: http://blogs.ittoolbox.com/km/dr-dan/archives/knowledge-management-is-easyif-12153