Knowledge management

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.


This entry was posted on Thursday 27 March 2008

Information Lifecycle Management - What is ILM

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.


This entry was posted on Thursday 13 March 2008


Earlier articles

Software Defined Data Center - SDDC

The Virtualization Model

Software Defined Computing (SDC), Networking (SDN) and Storage (SDS)

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

The Zachman framework

An introduction to architecture frameworks

How to handle a Distributed Denial of Service (DDoS) attack

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

My Book

Infrastructure Architecture - Infrastructure Building Blocks and Concepts

What is Big Data?

How to make your IT "Greener"

What is Cloud computing and IaaS?

Purchasing of IT infrastructure technologies and services

IDS/IPS systems

IP Protocol (IPv4) classes and subnets

Infrastructure Architecture - Course materials

Introduction to Bring Your Own Device (BYOD)

IT Infrastructure Architecture model

Book general available

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

Computer crime

Introduction to Cryptography

Introduction to Risk management

The history of UNIX and Linux

The history of Microsoft Windows

The history of Novell NetWare

The history of operating systems - MS-DOS

The history of Storage

The history of Networking

History of servers

Tips for getting your ITAC certificate

Studying TOGAF

Is your data safe in the cloud?

Proof of concept

Who needs a consistent backup?

Measuring Enterprise Architecture Maturity

Human factors in security

Master Certified IT Architect

ITAC certification

Human factors in security

Google outage

SAS 70

TOGAF 9 - What's new?

DYA: Development without architecture

Spam is big business

Why IT projects fail

Power and cooling

Let system administrators participate in projects

The 7 Habits of Highly Effective People

Archimate

A meeting with John Zachman

ITAC - IT Architect certification

Personal Information is Personal Property

The Irresistible Forces Meet the Movable Objects

Hardeningscheck and hack testing for new servers

Knowledge management

Information Lifecycle Management - What is ILM

LEAP: The Redmond trip

LEAP: The last Dutch masterclasses

What do system administrators do?

Is software ever finished?

SCADA systems

LEAP - Halfway through the Dutch masterclasses

Securing data: The Castle versus the Tank

Non-functional requirements

LEAP - Microsoft Lead Enterprise Architect Program

Reasons for making backups

Log analysis - Use your logging information

Archivering data - more than backup

Patterns in IT architecture

Layers in IT security

High performance clusters and grids

Zachman architecture model

High Availability clusters

Monitoring by system administrators

What is VMS?

IT Architecture certifications

Storage Area Networks (SAN)

Documentation for system administrators

Rootkits

Presentations: PowerPoint sheets are not enough

99,999% availability

Linux certification: RHCE and LPI

IT Infrastructure model

Sjaak Laan


Recommended links

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


Feeds

 
XML: RSS Feed 
XML: Atom Feed 


Disclaimer

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

 

Copyright Sjaak Laan