very rough notes from snipsnap talk

Bottom up km with snipsnap

Why km doesn't work

Most km is top down

Management decides what tools process and org to use

Non-matching ontologies

Some structure gathered at mgmgt level and pushed down, doesn't reflect what employees need

Complicated processes

Complex tools

All of these lead to low user acceptance [ref UCD !!!!, once again technology is driving the agenda]

What is bottom up KM ?

From users -> mgmt

Self organising

Emerging structures

Ppl structure their work the way they like it

Fit users needs

Bottom up structures

Usually knowledge is floating around - unconnected and unstructured

Then

Collecting knowledge

Just collect it, don't organise it yet [ie don't worry about tagging and metadata]

Then

Structure knowledge

Build ontologies as necessary

Refactoring [extreme/agile processes]

But refactoring in code only affects a few developers, refactporing structires can affect users

Organisation

Isolated islands [isolated people with blogs]

Start to grow network/community and interconnect, links comments and trackbacks

Communities start to overlap -> large single meta[?] community

Connecting structure and org

RDF/FOAF/Atom/Trackback

Didn't mention links !!!

Why weblogs and snipsnap ?

Weblogs ideal to start community

Weblogs contain connection technology

Maintained by enthusiastic ppl

Wikis store knowledge and grow communities [???]

Installed without mgmt [and therefore subject to censure/termination when found]

Lots of work in refactoring k in wikis

Use Cases for bottom up KM

CRM

Sun are tyrying to use snipsnap as a CRM tool

Virtual companies and projects

CoPs

Universities

SnipSnap

Open source GPL

Weblog and wiki [no real difference between wiki/weblog according to him]

Java

http://snipsnap.org