Re: Identification of Potential Business Value #value
toggle quoted messageShow quoted text
What you have described is essentially something I designed for the US DoD in 1994.
It was to house their Business Process Re-engineering methodology, which a team of us BPR consultants had documented.
The question was how to publish it for wide distribution.
In 1994, a hard copy manual would have been the traditional solution.
But, to save trees and many other reasons such as frequent updates, and to start leveraging DoDs IT network, I suggested an approach we ultimately called a Knowledge Base.
It was housed in a KBase Tool (Microsoft Access and Visual Basic 3.0 for those who know such s/ware). In those days, a KBase was definitely not a repository.
A methodology is analogous to a process, typically with a work breakdown structure (WBS).
Each WBS activity had a description and any number of attached (associated) objects.
These three components are essential and remain the main ingredients of today's granular, process-oriented KBases.
In 1995, DoD funded the development of a KM methodology, which was housed on the same tool (VB 5.0 by then).
That early KM Methodology was the core for the eventual KM Institute's KM Methodology.
As a KM Consultant, I later recommended the KBase use to the UN.
But I recommended integration of CoPs, for which I coined an expression "Connect & Collect", where 'Collect' referenced the KBase content and 'Connect' referenced the CoP when the KBase content was inadequate or some K nugget (object) needed clarification.
The above history and the evolution of KBases is described more fully in a chapter in the book,
Knowledge Management Matters - Words of Wisdom from Leading Practitioners, 2018
Where is KM going? One Long-Term Knowledge Manager’s Perspectives on KM’s Roots by Chronological Stages
If anyone would like a copy of my chapter, just ping me at: douglas.weidner@...