Don't fall into the trap of assumaing your knowledge all lies with the experts. There is a lot of tacit knowledge in the "long tail" of community members.
We know that not all Knowledge (in fact very little knowledge) is made explicit, and can be accessed through documents. We know there is a great richness of tacit knowledge in the organisation. We know that if we can "find the people who know", then we can access that tacit knowledge through asking them questions.
So we need a way to access tacit expertise.
One common approach to this is to build an "Expert locator". You think - "Who are the experts in the organisation? Can we make an index of the experts, so that people can find them, and ask them for advice?"
However Expertise is not always synonymous with Expert, and certainly Experience is not synonymous with Expert.
Consider the graph above - a plot of the years experience in an imaginary company. We see red bars and blue bars - the red bars are the Experts, who have 35, 32, 28, 27 and 25 years of experience - a total of 17 years. The blue bars are the other knowledge workers. They individually have fewer years of experience, but there are a lot of them, and their collective experience adds up to 1187 years of experience - 8 times more than the experts. So if you need an answer to a problem, and if you want to tap into the experience of others, where is that relevant experience likely to sit? 8 times out of 9 (in this example) it will sit it the Long Tail of experience, not in the Short Head of the Experts.
Does this happen in practice? Do we get answers from less experienced workers rather than from more experienced experts? I think in real life - where knowledge exists in context, where contexts vary widely, and where many staff see knowledge in many contexts, then this happens quite a lot. Here is a story from a real company.
"I had written a report on the success of a particular operation in my business in the USA, and I made this report because one of my managers asked me to do this to support a decision. I was able to document some of our information from the last 4 year to help this decision. This is was a significant thing for my team, but it turned out to be significant for other teams as well. I saw a question through the web system asking "what has been the success of this operation in the company?". This was a question from a team in Africa, and it was a close enough scenario to the scenario for which I had written my report. You feel the power - you feel the power of knowledge and the value that it might represent when you receive a response "Thank you very much for your reply, because this actually helped us to make a decision". It was an incredible experience to answer a question in the forum, with only 2 1/2 years experience in the company, and already being able to advice the whole world on the things we do and how we do it".The answer was in the Long Tail, the context was similar, the knowledge was transferred, and time and money were saved.
Here is another example showing that expertise doesn't always lie just with the experts.
So when you create your systems for tapping into tacit knowledge - your Expertise Locators or your "Ask a question" functionality - do not fall into the trap of involving only the few Company Experts.
So when you create your systems for tapping into tacit knowledge - your Expertise Locators or your "Ask a question" functionality - do not fall into the trap of involving only the few Company Experts.
No comments:
Post a Comment