As I explained in the first article of this knowledge mapping series, a knowledge map is a powerful tool for communities and organisations to capture and share their most valuable asset: intellectual capital.
In this article, I will share why and how to build a Knowledge Map and some concepts to consider when doing so.
Do not search for knowledge, access it
In every meeting and workshop about knowledge management, I get the following question: “Shouldn’t we have a search field?”.
We are so used to searching for information that it comes as a surprise when searching for knowledge is discouraged. The premise for the argument is that knowledge should be accessed rather than searched for. When we search for knowledge and if we are lucky, the best thing that can happen is that we find what we’re looking for. When we access knowledge by navigating the knowledge map, we discover things we did not know existed. We also gain a quick understanding of what we know as a group, what we have available to us and what we would like to have available to us, but do not yet possess.
Many of us have experienced varying levels of frustration when we complete a search in a database. Often the computer returns lists of 20 items or more with vaguely similar titles, forcing us to open file after file. I can assure you that searching is not faster than accessing.
How knowledge mapping can help
Organisations can curate an experience for their members when accessing their collective intelligence. The intellectual capital of the company can be quickly accessed by organising the knowledge assets in a knowledge map.
The image below belongs to the knowledge map for the preparation of the annual OuiShare Festival held in Barcelona. Knowledge maps are extremely intuitive and they provide great platforms to showcase our knowledge assets. Members of the team can navigate the different branches of the map, leading them to groups of assets and new maps. Most assets can be reached following different paths, as different people follow different thought processes.
Knowledge vs Information
The key to building a good knowledge map is to avoid unnecessary noise. The best way to avoid cluttering is to have a clear mind about what qualifies as a knowledge asset and what does not. I like the definition from Davenport and Prusak: “Knowledge is a high-value form of information that is ready to apply to decisions and actions” and that “knowledge derives from information as information derives from data”. This is extremely important, as I’ve often seen knowledge-sharing platforms suffering from an excess of information. This is damaging for the Knowledge Mapping initiative. Too much information becomes noise and noise prevents people from accessing the most important content. Here is where the ‘knowledge asset’ concept becomes important.
For me, knowledge assets are minimum common denominators of knowledge, an atom if you like. They are actionable productive units. I normally expect over 90% of knowledge assets to be produced as part of the normal team workflow. I like assets to be small and actionable. Those atoms are then added to the knowledge map for users to navigate and grab at will, so they become the building material of their projects.
Examples of Knowledge Assets
To help with the differentiation between Information and Knowledge, the following list shows a handful of assets we identified at OuiShare during the preparations of the OuiShare Fest.
■ Sponsorship Policy
■ Call for Volunteers
■ OuiShare Logo
■ Use of Fonts
■ Track Template (the conference is composed of four or five different tracks each year)
How to apply these theories to create a Knowledge Map
Let’s now imagine we’re part of the team who will prepare the OuiShare Fest in Barcelona next year. It’s a lot of work, which will keep the whole team of around 30 people fairly busy over the next few months.
You have chosen to work on the ‘Sponsors’ team and your objective is to engage as many companies as possible. The nature of this engagement is not only to obtain funding, but also to establish links between those companies and the experts, participants and entrepreneurs that will attend the conference. Ultimately, the goal of OuiShare is to help these companies start initiatives and projects related to the sharing economy.
List any knowledge assets you can think of related to ‘Sponsors’. Keep in mind that those assets should be useful and actionable pieces of information. The assets should help you and your colleagues to carry out your work, engage companies, achieve record funding and subsequently, kick off exciting collaborative projects with those sponsors. Please list those assets in the comments section, so we can discuss them. One key asset that comes to mind, for example, is ‘Presentation Email’.
How to organise your Knowledge Assets around Knowledge Domains
There are hundreds of knowledge assets in every community and every organisation. The first piece of advice when building the knowledge map for your organisation is to not try and capture all of your knowledge assets into one single mind map.
When you and your colleagues start creating your collective knowledge, you should be thinking of it as domains of knowledge. You can then dedicate one mind map to each of these domains. A domain is just a group of assets that share a particular area. It’s important to note that one given asset could be present in a number of domains. This is a key characteristic of an ontology when compared to a taxonomy, as we discussed in the first article.
In the OuiShare example, I am using for this article, one domain is called ‘Sponsors’ and has its own dedicated map. Other domains include ‘Branding’, ‘Production’, ‘Programme’ or ‘Volunteers’. Different members of the organisation will specialise in one or two domains. These team members will develop a feeling of ownership over these domains which is more important than it sounds, since company culture is the main obstacle for any knowledge management initiative.
Let’s focus on one single domain – Sponsors. Create a new mind map and call it ‘Sponsors’. This is the domain where we should be able to access all knowledge relevant to working with sponsors. Please add to the map all the knowledge assets you have thought of in the previous exercise.
Keep in mind that anyone in your organisation may come to this domain in search of useful and actionable information. While you create the mind map, try to create an experience for those visitors. I strongly recommend that if you start getting a long list of topics, you may consider grouping them as sub-topics. We often feel more comfortable with groups of no more than six or seven elements.
With the following mind map, you can explore some of the initial assets we identified at OuiShare, for the Sponsors domain. In the next articles, we will explain how this knowledge map evolved and why it matters so much.
We have seen the difference between information and knowledge, enabling us to start building our first knowledge map. Please use the comments to share your views on what ‘knowledge assets’ we should have in the ‘sponsors’ section. Also, if you’re making your own sponsors mind map, please do make it public and share the link in the comments below. I’ll then take a look and let you know what my feedback would be.
In the next article, I will share how the ‘Sponsors’ team mind map evolved. I’ll also show how to build connections between the different domains. This is the basis behind building the common brain, or collective intelligence, of your company, organisation or team.