Home Current issue 04 cover story
04 cover story
User Rating: / 0
PoorBest 
Article Index
04 cover story
> Knowledge: management vs. retention FI
> Introducing knowledge retention
> ISO9000 and knowledge
> Public and knowledge production
> Knowledge snippets and traceability
> The knowledge side of downsizing
> Management + Costing
> Management and participation
> Knowledge and embedded security
> Guidelines for action
> Timeframe for delivery
> Closing
All Pages


Management vs. retention

Knowledge Management is quite often confused with its tools and methodologies.

Anyway, almost any system or organization works according to the "Garbage In-Garbage Out" (GIGO) principle.

GIGO? Usually, any transformation process does not improve the quality of its inputs- at best, it can keep the additional "background noise" introduced by the transformation process low.

Any tool that tries to build a general description of activities across the functional divide is based on a specific idea of how the organization should be structured- the "embedded company".

The typical tool assumes a specific reference set of accepted processes, results, and way to manage changes: we will define this set of assumptions the "Embedded Corporate Identity" (eCI).

ERP, CRM, and Knowledge Management tools share the same pitfall: unless you know already where you are, you risk that the tools will insert into your organization their own "Embedded Corporate Identity".

We suggest that Knowledge Management is introduced once you have already a working policy for collecting, structuring, distributing, maintaining knowledge: what we call "Knowledge Retention" (KR) policy.