Getting to know a tool for knowledge management – or for anything which sounds as if your organization should be doing it – is like receiving a present. It’s gift-wrapped and looks very promising on the outside. But there is an issue.
This tool is too new and shiny. Everyone wants it, just for haves. Knowledge management sounds like a great thing to be doing so the word itself will attract the most unlikely suspects.
Tools for knowledge management – or not
When I started using SharePoint as a tool for knowledge management I soon discovered two things.
- SharePoint doesn’t do knowledge management by itself. Obviously. It does a number of things which, in the right hands, can get close to taking care of some aspects of knowledge management.
- A lot of people who want the tool are not really interested in knowledge management.
What people want:
A Cool website
A shiny website because management wants one. If your specific tool doesn’t look flashy it’s going to need a lot of customization. If you build a website for management it won’t be used for knowledge management – it’ll be like 10 volumes of Vitruvius on architecture on your management’s bookshelf. If it’s actually used they’ll want alterations which take a lot of time because of the extra work you put in earlier.
Content management without needing to manage content
An online archive because every other place for documents is a big mess. Years before I ran into SharePoint a coworker told me that the folder structure his team used looked like a bookcase had been overturned. The picture is pretty much the same in every online location where everyone is allowed to create extra folders. So people come looking for a content management tool. Unfortunately many of them want a tool that will do content management for them without their involvement.
A place that would support their workflows. Actually this may even work for SharePoint. In older versions you could already design InfoPath forms to perform actions and have them run in a SharePoint environment. But these workflows only work for people who like and need structure in their work. For everyone else: yes, you can break it.
A couple of my former coworkers once tweaked a constellation of InfoPath forms to meet a huge set of criteria – until it broke. I’m proud of them 😉
Twisting (knowledge management) tools
The strange part is that ‘unintended use’ happens to every tool if you allow it to happen. And it’s not just knowledge management tools.
- Whatever the tool, if it’s new and shiny, people will go out of their way to find a use for it. Next thing you know, you’re apologizing for an obvious lack of features: “Yes, I know it doesn’t mow the grass very well. But it did start out as a blender…” If you’re the only one offering a certain tool, you’re bound to run into people who want to use it for their own purposes.
- If you’re able to make alterations to the tool, the conversation might continue like this: “Well… we could construct a bag to hold the grass clippings – it would take about four months to design and build… or you could go to the shop and buy a lawnmower. Oh, you don’t have the budget. I see.”
However much you like the tool you offer, make sure you don’t make many changes to the tool itself, especially if it’s for internal use only.
Any tool basically does A, B, and C, which may add up to knowledge management – or to any other business purpose. It’s up to the team using the tool to collaborate across teams, to choose to share knowledge, and to use an online workspace to that purpose.