Knowledge adds value when it is current, useful, validated, acccessible, combines knowledge from many sources, and is packaged in a usable format. Here's how Siemens does its knowledge synthesis and packaging.
Siemens define a knowledge asset as being Validated Explicit knowledge on a value-adding Business processes. I like this definition, as it implies that knowledge becomes an asset when it is validated, and when it helps the business.
However creation of such an asset requires a creation process involving the main knowledge holders from across the organisation. From this source, here's a diagram showing how Siemens goes through the synthesis and validation process.
You can see from the diagram that a knowledge asset takes about 3 months to build, and involves three workshops involving the relevant subject matter experts, plus a final review workshop.
The validated knowledge assets are stored separately from non-validated project documents, therefore making a clear distinction between project information and cross-project knowledge.
Once the knowledge asset is in place it is continually improved through work experience.
However creation of such an asset requires a creation process involving the main knowledge holders from across the organisation. From this source, here's a diagram showing how Siemens goes through the synthesis and validation process.
You can see from the diagram that a knowledge asset takes about 3 months to build, and involves three workshops involving the relevant subject matter experts, plus a final review workshop.
- A strawman of the asset is prepared before the first workshop, at which the SMEs agree the content structure, the scope, and the key knowledge to be included (in the form of processes, products and roles).
- At the second workshop, the SMEs start to populate the content with processes, work products, and best practices - namely, searching around for good Explicit examples. They may provide practice guides, methodology, business frameworks, example work products, case studies, templates, architectures and role descriptions.
- At the third workshop, the tacit knowledge is added in the form of tips and guidance, checklists etc.
The validated knowledge assets are stored separately from non-validated project documents, therefore making a clear distinction between project information and cross-project knowledge.
Once the knowledge asset is in place it is continually improved through work experience.
from Knoco stories http://ift.tt/2AJZXii
via IFTTT
No comments:
Post a Comment