Knowledge mapping = a visual architecture of knowledge which enables and faciliates knowledge users to more easily and quickly access relevant knowledge and knowledge owners (Gomez et al 2000).
It sounds great to me – a visual, intuitive way to signpost people to important knowledge and/or relevant experts within your firm/department. And you get to identify “who knows what” and where your gaps are and future problems lie, at the same time.
Why then aren’t there more knowledge maps around in UK law firms?
I’ve come to the conclusion it is partly because people want a perfect map. They worry about the amount of work there would be in mapping out *all* the knowledge in their organisation. They plan to investigate fancy software, but get put off before they start. Or they don’t want to publish it until it is perfect, but the “knowledge” keeps changing and it is never finished. Or they simply don’t see enough value in it compared to the amount of work, to get it to the top of their “to do list”.
So, why not divide your knowledge map project into little sub-projects or mini-maps? Have a map for a single department (if it is fairly sizeable)? Or even, if your department is large, a map for an area of knowledge?
If the map was going to take less than a week, would you find time to squeeze it in?
Different knowledge maps have been used for different purposes. These are just the three main ones:
- procedural maps or process-based maps visualise knowledge and knowledge resources in process-based projects, and are useful for planning and implementing effective KM
- conceptual maps are used for content management of knowledge and used as a method of organising and classifying knowledge
- competency maps document the skills, techniques, positions and job experience of individuals and can be used by HR for development and placement, as well as to enable knowledge users to find the right knowledge owners and experts at the right time
I think the competency map is a great place to start for PSLs.
Map out the main areas of knowledge needed by your fee earners to do their work in one department or team, then map against those areas the right subject matter expert for each one. No doubt there’ll be politics in deciding who is an expert, but you are used to that particular minefield, I’m sure!
If it connects to your intranet/database or your White Pages/employees database … that’s great … but it doesn’t have to. A mindmap-style drawing on a whiteboard would do the job (and you could easily/quickly change it). If you are using a map for one department across a couple of offices, it wouldn’t be difficult or onerous to copy it out or photograph it.
What do you think? If you’ve experience of bite-sized mapping in your department, it’d be great to hear about your experiences in the comments.
If you like the idea of this bite-sized project, you may like my new book of KM Projects.
- APQC “Knowledge mapping guides organisations to knowledge within its walls” by Vicki Powers
- APQC “Knowledge mapping templates”
- “A framework for selection of knowledge mapping techniques” Jafari et al 2009
p.s. I know there is a split infinitive in the first paragraph, but I tried it with and without and it was harder to understand without. Clarity is all. 🙂
I also talk about knowledge maps in my popular “KM: The Works” training sessions, which run three times a year in London (January, May and September). Find out more here.
I also run lunchtime in-house training sessions on each of the projects from “Practical Projects”.
Do you suffer from info overload? Do you want a monthly summary email with updates about my latest blog post and open training events? Sign up here.