Knowledge Management Schools?

 "Would you tell me please, which way I ought to go from here?"
"That depends a good deal on where you want to get to," said the cat.
"I don't much care where," said Alice.
"Then it doesn't matter which way you go," said the cat.

This quote from Lewis Carroll's Alice's Adventures in Wonderland sums up knowledge management for me - it's a frustrating discipline!  It's frustrating because as a discipline it seems to be directionless.  It's frustrating because some practitioners claim almost anything to be managing knowledge.  I often liken these practitioners to Lewis Carroll's Humpty Dumpty who said in a rather scornful tone, "When I use a word it means just what I choose it to mean - neither more nor less."  It is precisely a lack of shared understanding and common meaning that causes so many problems. 

So what's the solution?  One way of solving this problem might be to position oneself in a ‘school of knowledge management'.  But what are the schools?  Yesterday I came across an article by Professor Michael Earl which answers this question.  It's titled ‘Knowledge management strategies: towards a taxonomy', and was published in the Journal of Management Information.  Despite being published in 2001 it's well worth a read.

Earl says knowledge management approaches can be positioned into three primary schools - the technocratic, economic, and behavioural.  Each of these schools has distinct attributes, philosophies, focuses and units of analysis.  I don't agree his attribute and philosophy rows, which I think should be reversed.  My take, which is otherwise true to his article, reverses the attribute and philosophy rows and substitutes the term attribute for approach.  It is shown in the table below. 

School

Technocratic

Technocratic

Technocratic

Economic

Behavioural

Behavioural

Behavioural

Philosophy

Systems

Cartographic

Engineering

Commercial

Organisational

Spatial

Strategic

Approach

Codification

Connectivity

Capability

Commercialisation

Collaboration

Contactivity

Consciousness

Focus

Technology

Maps

Processes

Income

Networks

Space

Mindsets

Aim

Bases

Directories

Flows

Assets

Pooling

Exchange

Capabilities

Unit

Domain

Enterprise

Activity

Know How

Communities

Place

Business

Earl does not privilege one school or attribute over another, nor does he say they are mutually exclusive, but he does say one is dominate.  I won't paraphrase what he says because I do think you should read the article for yourself (I haven't linked to it because of copyright).  That said I think the table is reasonably self explanatory. 

I can position myself without too much qualification.  My primary school is the behavioural school, but I have elements of technocratic thinking.  I subscribe to the organisational and spatial philosophies, but like the cartographic philosophy with its connectivity approach and mapping focus.

For me this taxonomy goes some way to solving the direction and meaning problems.  Understanding which school, philosophy and approach you belong to matters - it determines your world view.  Which school do you belong to?  How might this taxonomy be improved?

Regards, Graham



categories:

Re: Knowledge Management Schools?

Hi Graham, we met during the KM Singapore. Hopefully, you'll still remember. Interestingly, we have read the same article which I also mentioned in my blog.

Re: Knowledge Management Schools?

Hullo Mathias.

I do remember you but I didn't realise you had a blog - very interesting.  I've added you to my RSS feed.

Regards Graham

Re: Knowledge Management Schools?

That's a pretty interesting model there Graham.

I think I might be on the organisational frame myself, although I may be drifting into a couple of others.

Re: Knowledge Management Schools?

Thanks for your comment Craig - I'm glad you at least find the model interesting. Personally I find it useful. In the coming weeks I intend to refine it a bit, and perhaps show it as a diagram.

Best Regards Graham

Re: Knowledge Management Schools?

Well,

What is of particular interest is this;

I am delving into the world of scrum and xp.  The way these folks like to articulate software reqirements is as <a href="http://en.wikipedia.org/wiki/User_story">user stories</a>.

The experienced and talented business analysts (from more traditional project processes) are more used to using models like Use-cases and UML. They tend to have an object view of the system.  For them it is all about identifying boundaries and relationships.

User stories strike me as a fundamentally different model.  OO clearly seems to be from the technocratic school and user stories seem to be from the behavioural.

Which is a better way to articulate software requirements?

The main goal is to ensure alignment between business and technology.  The challenge in implementation is linking the operational to the strategic.

Any thoughts?

Re: Knowledge Management Schools?

Hi Craig,

Thats's an interesting page of links - thank you.

I am not well qualified to answer your question.  I've built a few databases in my time, and I write addins for EXCEL.  I never elicit requirements through use-case or similar approaches.  I've always sat with the end-user and asked them to tell me what they want and how they envisage it might be used.  I then ask them to explain how it is different to what they have now, and get them to show me.  This approach essentially elicits an unstructured narrative, which I have to then decipher.

I find beginning with a "unstructured" behavioural approach emerges requirements that otherwise may not be apparent.   It also involves the end-user from the start, and alllows me to assess their technical competence.  

All that said I haven't built anything that might be called substantial, so I don't really have a comparison base!

Regards Graham

Re: Knowledge Management Schools?

Yes

That's the right approach for gathering.  The problems I am referring to are when you put an intermediate person between the customer and the developer.

That intermediate role is the business analyst in some projects and the product other in other 'agile' ones.

The way they frame their requirements adds a layer of structure and context.  I guess that worldview shapes the context and then shapes the requirements.

It's probably no issue if the customer, analyst and developer are all from the same school.

When they are from different schools - and in particular when there is a radical change of schools along that value chain - that's where things will get scary/hard/complex.

I'll keep reading and see what you expose with your further analysis and writings.

Re: Knowledge Management Schools?

Ah now I better understand your question! I can't answer it just yet, but intuitively I think you have nailed it - when there is alignment there is no problem, but misalignment opens the potential for misunderstanding.

Regards Graham