nl There is also a DUTCH VERSION of this site



Most recent articles
Knowledge management
Information Lifecycle Management - What is ILM

All articles

01 Aug - 31 Aug 2006
01 Sep - 30 Sep 2006
01 Oct - 31 Oct 2006
01 Nov - 30 Nov 2006
01 Dec - 31 Dec 2006
01 Jan - 31 Jan 2007
01 Feb - 28 Feb 2007
01 Mar - 31 Mar 2007
01 Apr - 30 Apr 2007
01 May - 31 May 2007
01 Jun - 30 Jun 2007
01 Jul - 31 Jul 2007
01 Aug - 31 Aug 2007
01 Sep - 30 Sep 2007
01 Oct - 31 Oct 2007
01 Nov - 30 Nov 2007
01 Dec - 31 Dec 2007
01 Jan - 31 Jan 2008
01 Feb - 29 Feb 2008
01 Mar - 31 Mar 2008
01 Apr - 30 Apr 2008
01 May - 31 May 2008
01 Jun - 30 Jun 2008
01 Jul - 31 Jul 2008
01 Aug - 31 Aug 2008
01 Sep - 30 Sep 2008
01 Oct - 31 Oct 2008
01 Jan - 31 Jan 2009
01 Apr - 30 Apr 2009
01 Aug - 31 Aug 2009
01 Sep - 30 Sep 2009
01 Dec - 31 Dec 2009
01 Jan - 31 Jan 2010
01 Feb - 28 Feb 2010
01 Mar - 31 Mar 2010
01 Apr - 30 Apr 2010
01 Jun - 30 Jun 2010
01 Jul - 31 Jul 2010
01 Sep - 30 Sep 2010
01 Oct - 31 Oct 2010
01 Nov - 30 Nov 2010
01 Dec - 31 Dec 2010
01 Jan - 31 Jan 2011
01 Feb - 28 Feb 2011
01 Mar - 31 Mar 2011
01 Apr - 30 Apr 2011
01 May - 31 May 2011
01 Jun - 30 Jun 2011
01 Jul - 31 Jul 2011
01 Sep - 30 Sep 2011
01 Oct - 31 Oct 2011
01 Jan - 31 Jan 2012
01 Nov - 30 Nov 2012
01 Dec - 31 Dec 2012
01 Apr - 30 Apr 2013
01 May - 31 May 2013


Ruth Malan
Gaudi site
Byelex
XR Magazine
Esther Barthel's site on virtualization



Misc

 
XML: RSS Feed 
XML: Atom Feed 


Knowledge management

Thursday 27 March 2008


In many companies, knowledge management is a big headache. Especially in knowledge intensive companies, like IT companies, financial companies or consulting companies, knowledge is mostly stored in the heads of the people.

Every few years companies tend to start a knowledge management project. These projects aim at getting the knowledge of their staff into some information system. Usually these projects fail. I think this is because of the following reasons:

  • It is very hard for knowledge workers to express the knowledge they have in some format in an information system.
  • Staff feel no benefit from the sharing of their knowledge.
  • It is very hard to keep the knowledge up-to-date.
  • It is hard to find information back
  • People tend to keep information to themselves , because it gives them power (I am the expert).

The information systems that can be used to store knowledge are among others: Microsoft Sharepoint, Documents on a fileserver describing some subject, etc. The information in these systems are typically not very easy to retrieve or to maintain. The knowledge worker who took the time and effort to write down some information, will have little satisfaction when the information cannot easily be found back using the search function (if search is implemented at all).

I have a little experiment for you: In an audience of knowledge workers, please ask how many people solved a (technical) problem using Google or Wikipedia on the Internet in the last 3 months (please raise hands). Then ask how many of them solved a problem by contacting a colleague. Finally, ask them how many problems were solved by using the information on the company's Intranet.

I will predict the outcome: 100%, 70%, 20% respectively.

My experience is that almost all problems can be solved and most questions can be answered by using internet search (Google, Microsoft Live Search, Yahoo), Wikipedia, and  by contacting an experienced colleague.

If the above is true, why invest in knowledge systems in the enterprise? I think it is much better to invest in making all information that is already in the enterprise globally searchable (emails, project plans, file folders, etc), and present the outcome just the way Google does. This is what people are used to these days. Google sells a nice appliance that searches all internal documents and delivers the Google look and feel for the results.

The other component to extract information from knowledge workers is to create a wiki. Why is it that many people are writing Wikipedia articles in their own spare time for no money at all? Because it gives them their 15 minutes of fame. Their name is displayed with the article, and they can reference to their published articles to their friends and colleagues. Why not use this psychological effect in the enterprise as well? Install a wiki with the same look and feel as Wikipedia (the Wikipedia software can be downloaded and used for free for this purpose), and make sure the author of the article is clearly visible. Install a rating system, where people can get kudos for good information.

The third component is to make consulting colleagues as easy as possible. The technology for this is Instant Messaging, for instance with Windows Office Communications Server. Especially young people are using this technology already to communicate between peers, using Windows Live Messenger (or MSN, like it was called previously). A question can be asked easily to a group of experts in the company, and by using presence icons, people are not disturbed if they are busy or out of the office. This solves the disturbing effect that telephone calls usually have.

I feel that using the three components presented here will avoid the need for the official knowledge management systems. In the enterprise, please use what works and what people are comfortable with already.


Information Lifecycle Management - What is ILM

Thursday 13 March 2008


These days, companies produce an incredible amount of new data every year. On average the amount of data grows 30-70% a year (depending on the type of business). Most of this data is rarely used 3 months after it's creation.

Storage of data is expensive. While the storage capacity per hard disk grows every year, the need for storage grows even faster. Managing all this data is expensive too. Data needs to be backed-up and new storage capacity must be purchased and installed.

Information Lifecycle Management (ILM) is about storing data on the most economical media for a certain time.

When data is generated (when you write a Word document, for instance), the file can be stored on a fast expensive SCSI disk. In the first few weeks you are working on the document, and several people might read it. Usually after two months everyone has read your document, and the file will hardly be opened anymore. ILM software can automatically move the document to a cheaper, slower IDE disk.

The location of the file is virtualized by the ILM software. The user thinks the file is still on the same location. People can still use the file, but reading it will not be as fast as in the beginning.

After a year, the document could be automatically moved to a tape by the ILM software. This time when the document is opened, it could take a few minutes before the file is available, because it has to be read from (cheap) tape.

If a document is read more frequently again, the file could be moved to the faster storage media by the ILM software.

ILM is a hype in the storage world. Among others, IBM, Storagetek, Hitachi, Legato, Veritas, EMC and HP deliver Information Lifecycle Management solutions.



More articles: See left pane.
 
About Sjaak Laan

Sjaak Laan

Sjaak Laan (1964) is married with 3 children. He lives in Drachten in The Netherlands. He works as Principal IT Architect for CGI and has more than twenty-five years of IT experience. More information can be found on his Linkedin profile.

My book

More information on ordering the book can be found here.

Some course material can be found here.


 
Contact

I can be reached through sjaak.laan [ a t ] gmail [dot] com.

Follow me on social media
Twitter LinkedIn Facebook RSS

This site states my opinion only, and not nessecarily the opinion of my employer or of the clients I work for.

The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.

 

Copyright Sjaak Laan