Jack Ivinson's article KM is about linking people...and lots of formatting opens up the idea that retrievable pieces of information, such as document, may not necessarily provide all of the information you needed when you set out to retrieve the document.

In the context of managing a project this idea is critical. A person may be able to find a document they need in a folder, by iteself. However, there may be additional information surrounding that document that has an impact on the project. Who received the document? Did they respond if a response is required? Were there other meetings or discussions happening at the time the document what created or received? Who was involved and what were those individuals doing?

There is a tangible benefit to having a complete overview of a project that places any piece of information in it's correct context. This means being able to look at the trail of information that a project creates in a linear fashion.

Digital project documents, internal information exchanges, time entries, etc. all need to be collected in the same portal.

KM Executive approaches project knowledge management with a set of tools designed to collect information during the course of a project as a natural function of the organization. This collection creates a chronoligically ordered knowledgebase allowing users to understand the context of the information they may need to retreieve.