Posted by Denham on April 05, 2002 at 09:43:17:

In Reply to: knowlege Management posted by Tashka on April 05, 2002 at 09:06:04:

Hi Tashka,

Your scenario gets at the distinction between information and knowledge. Let's assume the company had high quality descriptions of their procedures, they had all their tricks and tips captured, they had customer and supplier information in a CRM.... I believe there is still no knowledge. Let me explain.

Knowledge is emmergent, it requires relationships and 'Ba' (community), needs constant verification, group interpretation and cross validation to determine use, applicability, value and appropriatness. If the 'new' team had worked together before they will save time and need only absorb the context and build the external relationships to get to satisfactory knowledge exchanges. An entirely new team would also need time to build those internal relationships, trust and norms.

What the new team would be missing would be the tacit knowledge - the awareness, the situated knolwedge that comes from practice together, things that cannot be written down, feelings, warning sounds and guestures, agile responses based on past experience would need to be rebuilt. It takes time to make sense in any position and environment - this is all part of 'knowledge' and would have been lost at 12:01 when the previous people walked out.

What do you think?

---

Follow Ups:

---

Click Here to Post Follow Up in New Forums

    Knowledge Management Think Tank (New)

  

 Subject: 

Message: