INCLUDE_DATA
Organizations are growing quickly. mergers, acquisitions and attrition are just some of the challenges to overcome when trying to maintain a knowledgeable workforce.
Companies battle everyday to maximize the capture of tacit and explicit knowledge from their employees and have come up with a number of ways to do so. Collaboration tools, knowledge maps , communities of practice, content management tools, after-action reviews and lessons learned sessions are just some of the methods organizations have devised to counter knowledge attrition.
No single approach however is enough to ensure that knowledge is retained, a mix and match of approaches is required. Though the bottom line is this, unless an organization’s culture is geared towards sharing knowledge, creating systems and processes to enable the sharing of knowledge is a moot point.
These approaches can be followed within the a project as well and become essential tools you , as a project manager, can use to your advantage in running a successful project.
The After-Action review : This is a strategy that has been adopted from the military. Often after an engagement the team will sit down together and go over what occurred, analyzing strengths and weakness. This is an excellent feedback mechanism to promote learning within the team. On a large scale, trends and patterns can be observed by comparing multiple groups, allowing best practices and lessons learned to be replicated across teams.
Communities of Practice: Is one of the simplest ways of connecting people who need knowledge with the groups that have it. Communities of practice are an excellent way to collect and disseminate information to a large audience. In order to maximize the use of a CoP a careful balance of leadership and freedom needs to be given to the community to promote sharing of ideas and knowledge, as a lack of leadership or direction could seriously damage the usefulness of the CoP in the long run.
Expert Directories : Another great way to tap into the tacit knowledge that exists in the organization - the expert directories is a method by which people can interact directly with people considered Subject Matter Experts ( SME’s ) . This however requires voluntary participation by the experts as it requires them to devote time from their busy schedules to address questions that do not benefit them directly.
Information Repositories : The simplest method of extracting and storing explicit information is the information repository. In its most basic form is a large folder with information stored in some sort of a structure. Advanced information repositories or content management systems use meta-tags and taxonomy structures to organize information for the end user in such a way as to provide the maximum value. By creating processes around the system, organization can ensure that all explicit information find’s a place somewhere in the application. It also acts as a medium for the transition of tacit knowledge to explicit.
These are just some of the methods that you could use to promote knowledge sharing and transfer in your organization or project. Keep in mind however that true knowledge retention is a daunting task and unless you have a clear approach mapped out it could lead to some serious complications.
If you enjoyed this post, make sure you subscribe to my RSS feed!
WP Cumulus Flash tag cloud by Roy Tanck requires Flash Player 9 or better.
7 Responses for "Knowledge in Projects"
You’ve missed the two most valuable KM processes; the ones that can make a radical difference to project delivery. These are the Peer Assist and the Project Knowledge Management Plan.
The reason that they can make so much difference, is that they are applied as part of front-end loading, when a little extra knowledge can make a big difference.
See here
http://www.nickmilton.com/2009/06/there-is-killer-application-in.html
and here
http://www.knoco.com/knowledge-management-plans.htm
for more detail
Arjun,
I would take your bottom-line statement a small step further - unless learning and improvement is explicitly built into work processes so as to essentially be unavoidable, the collection and sharing of knowledge is a moot point. I know that’s harsh, but its pragmatic. It takes time, so if it’s not important enough to build in time for, it just doesn’t happen. The weakest link of all is typically in bringing lessons learned forward into planning.
A resource pointer: For those interested specifically in the After Action Review, our team has researched its origins and effective translation to corporate environments. The site contains a collection of articles on this topic (most available as downloads). http://www.signetconsulting.com/action_items/further_reading.php.
Nick,
Thanks for the comment, and the links
Arjun
Appreciate the comment Charles and while I do understand where you are coming from the need to convert everything into processes should be looked at a little carefully as a lot of people will end up doing this for the sake of “doing” it.
I have to say, I agree with Charles. Even if people end up doing things for the sake of doing them, at least they get done! And providing you quality control the processes, then useful stuff will emerge. What in fact you find over time, is that at first people do these activities because they are required to, but then they pick up on the value, and begin to do them because the beleive in them. That’s if you ensure the processes deliver value, of course.
If these processes are not mandated and unavoidable, then they are effectively optional. And which project has time for optional activity? They are stretched enough delivering what’s vital, without worrying about what’s optional.
Hi Arjun,
I would not say a CoP is a KM tool for projecs.
In a project one will bring together people with different expertise, with the goal of achieving a specific target. They will use their expertise to build their specific piece of the solution.
In a CoP one will bring together people with the same expertise (the practice), with the goal of learning from each other and exchanging their expertise.
Marnix,
I agree the CoP is not something that sits within a project. However it is a way to share Knowledge in a project. They use existing CoP’s to connect with users outside their project and also contribute to it from knowledge they’ve gained from within.
Arjun
Leave a reply