The Problem with Knowledge Management (and how to knock it on the head!)

By R Pool posted 07-02-2012 11:11



“Knowledge Management” is one of those terms that’s used often, seems to mean different things depending on who’s using it, that everybody knows they need but few know how to deliver. Even worse, most knowledge management solutions are cobbled together with disparate solutions that resemble a patchwork quilt sewed by Frankenstein’s blind cousin.

So how does someone, or an organisation, serious about things like:

  • making it easier for their staff (in different departments, offices and possibly countries) to actually find all relevant knowledge resources or assets quickly and easily,
  • putting internal and external information sources into one knowledge portal so searching can be across everything relevant
  • managing automated archiving rules in a standardized way

actually get the job done elegantly, smoothly and effectively?



1.      Provide an intuitive UX (user experience).

2.      Utilize a top of the line federated search engine – preferably one whose algorithm can be tweaked to produce results that are based on your organisation’s taxonomy (company classifications and industry jargon), and your own user ratings.

3.      Pull-in and make searchable in the one tool, relevant external resources: these could include subscriptions to industry analyst or research reports, trade periodicals and blogs, RSS news feeds, information services and even social media monitoring.

4.      Pull-in and make searchable in the one tool, internal files from disparate repositories, servers, and portals while being agnostic to the hardware or software platforms used.

5.      Enable and promote user ratings, comments, and communication while looking at a knowledge asset or file.

6.      Facilitate access to key work process resources (calendars, workflow enablers, expert communities etc.)

Most people hoped Microsoft’s SharePoint would do the trick, and it goes a long way toward the goal – hence its massive worldwide proliferation – but most users will tell you...that out of the box it falls a bit short where knowledge management is the goal.


What are your thoughts on this subject?


Here’s hoping you find what you’re after,


ECM expert


I work for Knowledge Systems (Nunwood) Ltd. makers of Fizz - an enterprise content management platform. For more information on Fizz please click here.

#SharePoint #searchengine #archiving #sharepoint #knowledgemanagement
1 comment


07-02-2012 14:49

I think what you listed here is definitely what vendors should be focusing on, at the least. Personally, I'd like to see a KM tool that uses these components plus the capabilities that Splunk is predicated upon; Splunk shouldn't just be a tool for back office wizzes.
Moreover, I think that tomorrow's KM tools will need to incorporate Collective Intelligence more and more into the core fabric of the product as opposed to it being a "nice to have".
Not only that, but these tools will need to provide a way to categorize and index data that is not our own, that is, the resultant set of data born from any Collective Intelligence algo. And since this data is always changing, there should be a way to take snapshots of this data at a particular point in time so as to analyze trends and update key knowledge points.