Sunday, February 25, 2007

What Tacit Knowledge?

Knowledge Managers say they're after "tacit knowledge" for that matter they have formed "spaces for stories to be told and listened to".
I have always looked at Knowledge Management from the "why would I share knowledge for free" point of view. However, even when I do want to share knowledge, I find out that it isn't so easy.
Saying that I have a story to tell means - I hope - that I know how to get something done. It does not mean that I have a story to tell. Moreover, it does not mean that I am aware to the fact that I have a story to tell.
How would I know that I have tacit knowledge to share?
If it is tacit, I have probably never discussed it with no one. It is not on emails, not on the notes I am writing myself - not explicitly, that's for sure. It is somewhere else and it probably pops-up whenever I need it. Since I don't communicate it, I am not aware to its importance. It fully pops-up up only when I am asked questions like "how do you know this" and "how do you do that".
Well, to expose this tacit knowledge, all the Knowledge Manager has to do is to ask me to carry out some task. But wait, ain't I getting paid for carrying out such tasks in the first place? I am (hopefully...), so I'd replace the previous credo with "... to expose this tacit knowledge, all my manager has to do is to keep asking me to carry out my job".
This way, the job keeps getting done, and no one has to wonder what am I hiding when I reply with "What Tacit Knowledge?".

No comments: