Conversations and the emergence of unsuspected knowledge

A large part of companies’ knowledge is not available for all for the only reason people are not conscious of the importance of some details of their experience and that, since others don’t know what these people know, they don’t think of asking them anything…

Hence the importance of not organising knowledge capture on the only base of “forms people have to fill” and pay attention to what can capture conversations which are the only way to make emerge “what we don’t know people know and they dont measure the importance”.

That reminds of this famous Donald Rumsfeld’s sentence. It made me laugh at this time, but perharps it has more sense than I though (even if he didn’t did it in purpose…)

There are known knowns. These are things we know that we know.

There are known unknowns. That is to say, there are things that we know we don’t know.

But there are also unknown unknowns. There are things we don’t know we don’t know.

Capturing knowledge is a permanent activity

Capturing knowlegde was often a failure since it was considered as a task by itself and not an “on the flow” activity.

People were asked to take tame to give information, which didn’t work the reasons everybody knwos. What counts is organizing a real time information capture, that’s to say integrated in people’s day to day job in order to make it painless.

The first track that has to be explored is to shift existing flows to tools that make capitalisation, sharing and reuse possible. No additional workload for individual but a gain at the organization scale, as I already said here.

At a first glance, it’s seems to fit perfectly for exchanges about day to day best pratices.

.

Sharing knowledge is not a task but a way of working

I just saw this interesting post on this topic,  thanks to Martin Roulleaux-Dugage. The difference between traditional KM and its “2.0″ evolution is that it’s not a task anymore but a way of doing things, a on-the-flow activity.

Take time to classify, fill in forms, stock is real burden that often lead KM projects to fail. In the other hand, in just a few clics, classify, share an information as soon as it’s identified, write a quick note about it, quickly identify related documents and people who would be able to help me with my daily problemactics is rather a way of working. It’s not a task that need me to book some time, it’s an ever ongoing on the flow activity which is not its own purpose anymore but is linked to my daily problems solving.

This reminds me of my usual answer when I’m asked how much time it will take to a group to share knowledge within its members, how much time it will take to stimulate the group. The waited answer is often about hours, half days… My answer is the following : it won’t take a lot a time but it will take often a little time. But if there’s a business need behind, it will be painless. Minutes here, seconds there, on the flow, not hours spend when doing otherwise is impossible, when it’s impossible to wriggle and when job is botched up done reluctantly.