Number of views (2881)
*The views, opinions and positions expressed within these posts are those of the author alone and do not represent those of Seavus Group.
We accept no liability for any errors, omissions or representations.
The copyright of this content belongs to the Seavus Group and any liability with regards to infringement of intellectual property rights remains with them.
1/13/2009 11:09 AM
Nice post and one I entirely agree with. Mapping knowledge in an organisation can b very enlightening. Take a look at this link http://www.durantlaw.info/Visualisations for some real examples.
1/14/2009 6:09 AM
Appreciate the comment and the examples.
When do i start my KM initiative? | Proj
1/14/2009 12:14 PM
[...] the past 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 [...]
1/16/2009 9:15 AM
One of the drawbacks that I am experiencing in applying knowledge maps within a project is primarily coming from looking at knowledge as a stock, as maps fail in representing knowledge flows and relationships.
But representing only flows and relations (like the ones Graham represents) does not orient/help a project to act on reducing knowledge gaps.
1/16/2009 12:13 PM
I do understand the draw backs of applying knowledge maps to projects when you look at knowledge as a stock.
While Flows and relationships do not help you directly reduce knowledge gaps they do provide you with information that can help you do so.
As I'm sure you know there is no formula you can apply to get the results you want. Each approach only gives you information that you need to put together in a manner you see fit.
1/16/2009 5:58 PM
Excellent article. Knowledge maps have several applications and can be very useful in project management as well as in strategic planning. Knowledge maps also help identify experts and go to persons on a project, which is especially useful in a post merger scenario. They help reduce the level of effort and time spent on finding the right person to answer a question, which can be considerable (around 30%).
Murali, you can build relationships into a knowledge map. I use knowledge flows and interactions in my maps.
1/18/2009 1:39 PM
Good post Arjun.
I think it essential that at the project level knowledge AND skills mapping takes place. I have often found that the project team is not aware of the knowledge they have, the knowledge they need nor the skills within the team. Getting this right would make a real difference and delivery of project just a little easier.
ABT with LinkedIn.com comments
2/2/2009 11:55 AM
Hi all - these are a few discussions from LinkedIn.com. This is the original URL - http://www.linkedin.com/newsArticle?viewDiscussion=&articleID=23357570&gid=47726&trk=add-news-lnk-cThOon0JumNFomgJt7dBpSBA . The comments are not edited in any way, and are copied in full as they appear originally.
Hemangi Vyas wrote:
That strategizing is very important and is the first step towards building up the KM process is not understood. I found it totally absent or not strictly followed in some companies.Considering that KM as a concept was first initiated in such firms i found that surprising. Thanks for sharing the article.
Daryl McCracken wrote:
Knowledge Maps have been a key component of, and success factor in the development of our companies communities of practice. From the business side, it encourages a structured exploration of the information which needs to be created or gathered. And from the technical side it greatly improves the ability for developers to understand the scope of effort, to plan architecture and to more rapidly deliver web-based solutions.
John Maloney wrote:
Hi -- Knowledge mapping is not recommended. KM is definitely not a process or a "web-based solution." (Hunh?) It is disappointing to see these questions and remarks. It is 2009 folks!
"...it tells you where knowledge resides..." What? Knowledge is not a resident. Knowledge is a dynamic flow. Knowledge inhabits networks.
Data and information are modeled and mapped. It is important, but it is not KM. Please. It is information management, library science, data base admin and document control. Calling this KM is the origin of all the KM problems.
Knowledge is social. Knowledge creates value and wealth. To visualize and optimize knowledge you must examine the value networks. That's all. All the 'web based solutions,' document libraries, and processes (?), will take care of themselves.
KM is a complex adaptive system. It cannot be controled or 'processed.' It can only be served. To understand and improve knowledge, do not waste time and resources on information administration, visualize value. More here...
Nick Milton wrote:
I agree with John that what Aleksander is suggesting is information mapping.
An alternative approach is to map out the business-led knowledge needs. Ask the question "what knowledge do we need to deliver our business strategy and goals"? Then ask - "do we have access to this knowledge? If not, how do we gain it?"
This demand-side mapping is in my opinion more powerful than supply-side information mapping.
Naina Visani wrote:
I am not sure that I totally agree. I agree that the mapping processes do map what is explicit and in this case information. But it can used to map the people or team who do actually hold the knowledge and what that knowledge topic might be. Such a map can be used to identify the experts within a company but we also use this to map out our knowledge domains or capabilities within our organisation so that we can track the health of this (by identifying indivuals or team sizes) to ensure we deliver against our strategic objectives. So mapping knowledge is possible and is not always just about identifying information.
Alastair Stewart wrote:
I agree with Naina; you can map knowledge, and it's useful to do so in two ways:
1) A knowledge structure map can show you the knowledge tree required to do certain tasks, i.e. just what you need to know to carry out a task, and how it is built up from other knowledge. These maps can show you the robustness of the knowledge within your organisation - e.g. how many people know a particular critical topic.
2) A knowledge flow map can show you who has knowledge, who needs it and the mechanisms used to transfer it between them. These maps can show you how effectively knowledge moves around your organisation - e.g. is B out of the knowledge transfer loop between A and C, and does it matter?
9/14/2014 2:57 AM
All of them are valuable, practical and entirely within budget! If not anything, our Professional Consulting practice will know where you can get started.Where do we begin, why aren’t we not already connected? All our services are geared towards you. http://www.redcloudsystems.com/
If you are interested in conveying your message to your target market, please contact us at email@example.com!
Share you project management knowledge and expertise with the hundreds of thousands readers of PMTips.net. Apply here!