Relationship of KM with other functions in an organization
After working in the KM arena for many years now, one thought has started puzzling me — “The relationship of KM function with other functions in an organization and the consequences of these relationships — in terms of the KM viewpoint & outlook, success etc.”
I have observed many different Indian IT organizations [I presume it must be similar in other countries also], that each organization has it’s own structure for KM within the organization. For example in one organization, KM reports into quality and is part of the quality function, In another organization KM reports in Education, Training & Research, In another it is heavily distributed and some parts report into Marketing & Sales, some into HR etc. In another one we have a separate KM function that reports directly to the COO.
I have observed the KM initiatives in all these above organizations from close quarters, through various interactions and in all of these cases, the results of KM and the road map, the view of KM, what KM is, is all different and very heavily influenced by the function/person KM reports into.
- KM being a cross-functional discipline, also is similar to an elephant being viewed by blind-folded persons and each person [function] having it’s own view/perception of the elephant [KM] depending on what part of the elephant they are seeing.
- At the same time, KM’s cross-disciplinary nature can create structural tensions within an organization if it is a separate function, with developing working relationships, alignment on directions, strategy, over stepping on other functions toes.. being just some of the issues..
- KM being a relatively new discipline and not very well understood by the stakeholders also contributes to this dilemma. For example, Quality as a function has been there for ages and is pretty well understood. You will very very rarely see quality reporting to say CIO or HR or Marketing or Learning/Training function..
- Also, KM itself is a journey within an organization and goes through various stages.. from repository/technical platforms [CIO function alignment] to communities [HR/Learning function alignment ] to reuse of knowledge [Quality function alignment] to deep integration within the line function [function head alignment] to complex change management & Innovation [COO/CEO alignment]
Surprising isn’t it? We are in the knowledge era and the position of KM function within the organization structure is neither well understood or defined….
I think every organization that is starting a KM journey needs to ponder over this in great depth and align KM function appropriately within it’s organizational structure
Wiki adoption – Think of a context first…
Many a times; just because the whole world is going the wiki way, organizations start a wiki initiative and put a wiki in there and say — let’s use it. Many a time it doesn’t work..
Every organization, team, function, or unit needs to first identify the context’s in which Wiki will be used and what needs it will satisfy. In short, you need to answer ‘Why do you want to use Wiki’; and generalities won’t do here. You need to be precise and identify the scenario’s , the context in which your team will use the wiki. Saying that we wil use wiki for ‘collaboration’ just won’t do. Ok.. collaboration for what?
Whatever be the context, say a place to list all the SoP [standard operating procedures] , glossary of terms, cheat sheets, place for sharing infrastructure details, contact details of team members, list of modules within a project and roles & responsibilities, release notes, installation procedures… etc etc..
If you identify even the basic 2-3 scenario’s, the contexts in which your wiki will be used, and then make them work… then wiki adoption will be easy..
Why Wikipedia is the biggest threat to Organizational Wiki Adoption
Strange as it may sound, I believe that Wikipedia is one of the biggest ‘threat’ or issue when rolling out a wiki initiative in an organization.
I was at KAMP — a KM unconference and asked the partcipants on how many used Wikipedia as a refence, as an example for introducing Wiki to people within an organization. Almost all raised their hands and agreed.
What’s wrong with that.. you may think.. well what’s happening here is that you are sending a subtle message to people that it is a Wikipedia equivalent that we are trying to build within an organization and people seem confused on why would you want to do that.
KM professionals need to stress the ‘underlying principles’ of Wikipedia more that wikipedia itself when trying to start a wiki initiative and clearly mention that we will be using these principles to use the power of wiki in our organizational context.
So my advice to people is.. beware when you use Wikipedia as an example of wiki..
This is the presentation i used to illustrate some key ponts we need to be aware of while rolling out a wiki initiative
leave a comment