What about Knowledge Management?

Although I said that the previous post would be my last argument about integration… well, I couldn’t resist! : )) In fact, I think it is still missing a link from all this discussion and the main focused topic in this blog: Knowledge Management.

Is integration important for KM? No doubt about that!!! In this sense, we can think of:

• knowledge integration, as in different pieces of knowledge merging together in one big whole that is useful for someone;
• the integration of processes and enabling technology to serve the purposes of KM inside an organization;
• the integration of people in communities of practice to allow purposeful collaboration within or across organizations.

All these three examples are very relevant for KM to be effective. In this way, you can also imagine that all the discussions we made so far (starting here) are of course also applicable in this scenario. Let us see how:

1) When should a KM system be integrated in the processes underlying an organization?
A new KM system should be integrated when the members of the organization feel a need for support to achieve certain goals (both in terms of organizational strategic goals, and its members’ individual objectives). If the system in this case is already available (e.g. Lottus Notes, KEEx -- click in 'Soluzione'), an analysis should be made in order to find out ‘how’ this system may be configured, in a way that it is not intrusive and, instead, naturally adjust to people’s practices. A similar analysis is needed even if the system is not yet available. In this case, the system should preferably be built on top of existing technology already in use in the organization so that the members are already familiar with the interfaces and/or methods applied. This can make a big difference in achieving acceptance.

2) How should this system be integrated into the current processes?
The integration of this new system should result in advantages to the organizational members. So, based on my previous argument on how integration should occur, the system should maximize the positive points of the process while minimizing its flaws. On the other hand, in accommodating the system, the process should cover the important needs that are not covered in the system functionalities, besides allowing organizational members to make use of the system in its full potential. We can thus conclude that, besides the initial analysis of requirements, mentioned in 1), this also requires a careful design on how system and processes should be ajusted.

Ok, after this small example in the KM field, I am now completely satisfied! Wait… no… actually, not completely… I still need your comments! : )) So, I’m waiting, guys…

Kind regards,
Renata