« September 2004 | Main | November 2004 »

October 21, 2004

KM tomorrow

An aspect of KM that does not get much attention is awareness & agility.

More than improved decision making, more than increased problem solving, more than access to expertise - KM helps companies to be come aware of their environment, individuals to build connecting personal networks and teams to respond faster to external changes.

The OODA loop is one of KMs little known advantages. KM helps with recognition of new and important concepts, assists with context finding, making connections, vetting observations, ideas, theories and heuristics.

OODA explained

Awareness
A sensitivity to discontinuous change, an ability to discover, discern and focus on emergent, important issues, a filter for sifting the significant and intuition for discriminating context.

Agility
Fast comprehension, compiled reactions, resolute activity, alertness and nimbleness in sense-making.

October 09, 2004

Patterns for change

Mary Lynn Manns & Linda Rising are pattern evangelists who have just completed an interesting book on 48 patterns for introducing new ideas.

Patterns
Capture expertise in the form of vetted solutions to repetitive issues. This is a key knowledge representation and a neat way to leverage learning. Patterns are an advanced knowledge practice that combine best practices and distinctions with community adoption.

Pattern language
A collection of patterns that are related, focus on the same domain, work together to record proven solutions, capture expertise and solve known problems, perform a higher level function - they allow users to articulate, share and relate complex thoughts - they leverage communication and lift the level of the discourse.

The book
Fearless change. Patterns for introducing new ideas. 2004 Addison Wesley, captures the experiences of two real life pattern evangelists. First half introduces patterns, the form, uses, styles and theory. The remainder catalogs 48 patterns in an easy reading format (opening story, summary, context, problem, forces, essence of solution, more on the solution, resulting context and known uses).

Their 48 patterns are grouped into themes (early (21), later (16), resistance (6) and throughout (5)), given easy to identify names, e.g. corridor politics, just enough, bridge-builder or time for reflection and each follows the same format.

Patterns - been there
Good patterns leave one with the feeling - I know that or I do that already - what the authors have done, is the hard work of providing examples, rationale and context - the key to turning information into working knowledge.

I'm skeptic, patterns do not exist as documentation, they only come alive and yield value when adopted and practiced within a community. The real challenge is now to build or find a group that will work through these excellent patterns and adopt the language.

October 03, 2004

KM tool selection

What are some of the key choices we have to make when considering a KM system?

Making a tool selection is no easy task as there are many tools that can be used for KM. Consider these questions:

* Will we focus on explicit (documents) or emergent (communication) forms?
This points to a codification vs. personalization strategy decision, corporate memory and intellectual property / knowledge asset orientations.

* Should we concentrate on support for individuals or communities?
Highlights concerns with diversity, the need for collaboration structures and aggregation issues.

* Do we include 'outsiders' in the mix e.g. customers, stakeholders & suppliers?
Extranets vs. intranets relate to strategy decisions on (virtual) organizational forms, competitive advantage and industry networks.

* Must we have a distributed (blogs) vs. centralized (intranet) approach?
Similar to previous dichotomies, this choice highlights concerns with quality, control and retrieval.

* Should we allow a mix of mediums (IM, SMS, VOIP) or settle for a single approach (asynchronous)?
Immediacy helps with idea capture, builds trust and assists with JIT solutions, reflection, revisions and quality may be compromised.

* Will we need inference and 'intelligence' or do we favor a manual style?
Relates to issues of 'discovery', assigning meta-data, auto-profiling and corporate ontology development.

* Do we support 'road warriors' or will we concentrate on 'in-the-office' connectivity?
Mirrors decisions around intra / extranets, complicates issues with aggregation, classification and corpus navigation.

Meta thoughts on KM tool selection