Dear Swati,
While the end result of the activity is laudable, the means are not!
Your MD wants to implement the "Knowledge Management" practices in the company. Creating a knowledge repository is important; however, the knowledge has to be extracted from the heads of the employees, classified according to the subject(s), and then stored in an organized manner. However, knowledge management does not just end here. The stored knowledge has to be used as well. Therefore, someone has to go to each department, identify their needs, and explain how to utilize the knowledge.
To accomplish all this, your company needs to appoint a Knowledge Officer (KO). The KO also filters knowledge from simple information. The storage of tidbits of data is not the objective. Therefore, the KO needs to have the depth to distinguish between the two.
Some top-notch IT companies have a Chief Knowledge Officer (CKO) to whom many KOs report. Their duty is to constantly search for knowledge, store it in an organized manner, and then disseminate it to the relevant departments. You may refer to the following links for additional information:
- http://www.ipedr.com/vol12/45-C115.pdf
- https://jose.carambolamc.com/implementing-knowledge-management-within-an-it-company/
- https://www.infosys.com/newsroom/events/Documents/pragmatic-approach-knowledge-management.pdf
Your MD needs to revise his approach to implementing knowledge management practices in the company. The current method poses the following risks:
a) Any unwanted deduction from employees' salaries is always resented and can lead to disgruntlement or demotivation. The cost of demotivation could outweigh the impact of a 5% deduction.
b) What if Managers/HODs pass off ordinary information as "knowledge"? Is it not akin to "passing off ducks as swans"?
c) Whether intentionally or unintentionally, what if Managers/HODs pass on misinformation?
d) Knowledge management involves documenting successes or failures in an organized manner. To do this effectively, one needs good drafting skills. What if the document is poorly worded and not understood by the user?
For now, the information provided above should suffice. There are additional risks to consider. For further details, please feel free to contact me.
Thanks,
Dinesh Divekar