Knowledge Base Design Patterns

Process Component Design Patterns


Description

A section on the intranet that includes useful collateral such as:

- Demo models

- Extended Papers describing certain features of the product

- Useful shortcuts, tips, and tricks

- Sample code

It is also imperative that this is properly designed with an underlying information architecture and these artefacts and resources are simply not "shovelled online" creating an unusable and unfindable mess.

See also my attempt to create a prototype "Consultants' Handbook".

Processes (that produce or use this component)

Deliver Consulting Services

  • Category: Resource
  • VSM Role: System 2 - Co-ordination
  • Feedback Notes:

    Provide anything useful from the Assignment Feedback or the Deliverables (e.g. Model Artefacts) to whoever plays the "Knowledge Manager" role (e.g. web site manager, designated web site editor).

  • Potential Issues:

    Badly designed and/or poorly maintained intranet so that useful information is lost in the noise. This is symptomatic of a wider problem, namely: No understanding of, or commitment to, the idea of knowledge as an enabler - especially for a knowledge-intensive process like service delivery and consulting.
    Consider two key principles of Human Performance Technology
    - Does the consultant have access to relevant knowledge and information in order to do the job?
    - Do activity standards exist?
    Therefore, when evaluating this interaction, it should not be just a crude quantitative measure such as "Number of documents on an intranet", but more about the organisation and accessibility of those artefacts and how useful they are.

  • Evaluation: 1

Manage Technical Knowledge Base

  • Category: Output
  • VSM Role:
  • Feedback Notes:
  • Potential Issues:
  • Evaluation:
Appears On

IGOE Scope Diagram Deliver Consulting Services

VSM View Deliver Consulting Services