KM would be less confusing if it were not for the English Language

Here’s another post from the archives (corrected for some inaccuracy) which makes the case that much of the confusion around Knowledge Management may be due to an uncharacteristic deficiency in the English Language. 

Lost in TranslationKnowledge Management has always been in a state of confusion. There is no established understanding of the term; instead there are conflicting fields vying for the label. Library science, Artificial Intelligence, lesson-learning, Knowledge-centered support; on a good day, these can be seen as clusters within a distribution or characters within a crowd, while on a bad day they can be combatants in a turf war, with IT vendors on each side adding to the noise and smoke.

Why the confusion? Largely, I would suggest , because of a strange deficiency in the English language.

In English, unlike many other languages, we have only one verb for “Knowing” and only one noun for “Knowledge”. 
Other languages have at least two words; one of which means “intimate knowledge, acquaintance, knowledge as capability, know-how”, the other means “knowledge of facts, rote knowledge, know-what”. Connaitre and Savoir in French, Kennen and Wissen in Germany (and also Können), Kunne and Vite in Norwegian, and so on. Vestiges remain in English dialect (“Do you ken?”) but mostly the distinction between the two in English has gone.

Between these two words there is a world of difference. Someone might say  “I know Paris” (“Jeg er kjent med Paris”),  while another might say “I know the capital of France” (“Jeg vet hovedstaden i Frankrike“). The second person might be useful in a very easy pub quiz, but the first is the person you want as a guide to the best restaurants, hotels and sights.

It is the first type of knowledge that gives power and creates an economy. That is the Know-How knowledge, that deals with acquaintance and capability; that directs action and delivers business result. Knowledge Management focused on Know-How looks at improving the competence of the organisation by giving people access to the knowledge they need to make the correct decisions.

The second type of knowledge, the Know-What knowledge is close to Information, and managing “Know-What” gets very close to content management, to Information Management, or to Business Intelligence.  It is the marshalling of facts. In Dutch, Wetenskap refers to science and scholarship, while Kennis refers to acquaintance and acomplishment.

It is “Connaisance” and “Kennis” that gives Power, and Knowledge Management is often translated in a way that makes this clear (Gestion de Connaisance, Kennismanagement). We have no such distinction in English.

Two meanings in one word

English usually has so many words, reflecting subtle variations in meaning. With the word “Knowledge”, however, we have two meanings hidden in the one word; and as an outworking, we have two views of Knowledge Management. We have on the one hand a meaning that carries connotations of power, economy and capability, and on the other a discipline that all too often focuses on organizing information.  One looks at know-how; knowledge as capability. The other looks at know-what; knowledge as facts. The differences between the two are lost in translation, as we struggle over how to manage one word, with two meanings.

If we could have KnowHow management and KnowWhat Management, Gestion de Connaisance and Gestion de Savoir, Kennenmanagement and Wissensmanagement, then the turf war would subside, with the Storytellers and the learners-from-experience working under one heading, and the content organisers, librarians and SharePoint technicians working under the other, and both sides working profitably together.

My own life in Knowledge Management has always been in the service of the first word – Know-How, as that is where I see the value, but I really wish we had the two words and therefore the two disciplines!

It would make life so much less confusing. 

View Original Source (nickmilton.com) Here.

Leave a Reply

Your email address will not be published. Required fields are marked *

Shared by: Nick Milton

Tags: ,