Why is KM Important?
Posted by Arjun ThomasThose of us already in the field are so caught up in meeting deadlines, creating drivers that ensure our existing KM initiatives don’t fall flat. We don’t stop to think “Why KM?”, at least that’s what I’ve found after talking to a number of people. Sure there were indicators that lead to the decision of implementing KM at the beginning; however no clear cut goals or objectives were established right at the start, and even if they were most of them were to intangible to track. In a number of cases existing information management practices were re badged. After all KM was a buzz word and everyone wanted to get on board as quickly as possible.
I see this trend continuing with companies that have started to adopt KM within their ranks. They often seem uncertain of benefits that KM can bring to the table, while they may know the answer to the “What” they don’t know the “How”.
Why am I telling you this? It’s because if you decide to implement a Knowledge Management program within your organization or project team you need to do it for the right reasons.
KM is not something new, and whether you know it or not you have been using it on a daily basis since you were young enough to count. In today’s corporate arena it takes the form of building a network of contacts, ensuring the information you have stays current, keeping an eye on SME’s ( Subject Matter Experts ) within the organization, and so on. Essentially ensuring you are well connected and “in the know”.
So back to the fundamental question, why is KM important?
In a project context, there is a lot of effort spent managing people, processes and churning out vast quantities of information. As a project manager (or a budding one) you need to start asking the question “How do I promote knowledge management within my team?” There are a multitude of benefits that you can take back from doing this, some of which I’ve listed in my previous post, and the rest we shall get into more detail in future ones.
Leveraging existing knowledge in terms of projects that have been done in the past and connecting your team with experts across the organization (and outside) automatically allows you to save time and deliver faster, better results.
In today’s world, with attrition levels being where they are there are often instances where initiatives lose direction and focus after key personnel leave the organization. For the true success of any KM initiative the agenda and focus should be independent of any single person. The vision should be at an organization level for it to have any chance of long term success, so ensure that you aren’t the only one driving this initiative within your team, rope in supporters (you will need them).
As the year draws to a close its time you plan ahead and start thinking of what you would like to accomplish. So, why do you think KM is important?
Hope you have a great new year, and see you soon!
Related posts:
Why is knowledge map important? | Project Management Tips says:
[...] critical to understand that if you are starting a KM initiative you first create a knowledge map, this will establish a platform upon with you could build your KM [...]
When do i start my KM initiative? | Project Management Tips says:
[...] week or so I have put up posts on subjects like Knowledge Mapping, Communication Strategies for KM, Why KM is important and Web 2.0. Knowledge Management is a vast subject and while it might be a little difficult to address all [...]
Graham Perry says:
Knowledge Management is critical where there are a number of contractors involved in delivery.
Phase 1 of the project comes along and is delivered.
A couple of contract Project Managers end their contract
Phase 2 comes along but much of the knowledge and experience gained in Phase 1 has left. This leads creates a risk to the project (knowledge risk) and increases timescales and costs due to the extra training effort.
As Arjun’s article says ‘KM is not new’. It is easy to implement (Word & Excel documents in its simplest form) but unfortunately it is often overlooked due to project delivery pressures.