Collab.klog.km

As Jim says, a nice little mini-case on KM -- how to start small and achieve success. This is important for those of us looking to get a company started on the right track. The case study talks about successfully applying KM practices to a single project as a way to embrace the principles. Among the key thoughts:

Start small and grow steadily over time.
Set the "rules of the road" up front and keep it simple.
Enforce the new culture.
Define standards but be reasonable.
Pilot a project.
Assign a KM owner.
Show everybody everything.
Management support.
Team feedback.

This is a useful 15-minute read for anyone getting ready to start or lead a new project.

Project Level Knowledge Management.
Project-level implementations of KM hold promise for one simple reason: They address real day-to-day problems that can only be solved with collaboration. Notice I didn't say collaboration tools. That's a very important distinction because this is where KM has traditionally gotten into trouble. The tools are enablers; collaboration is an interaction of people. If you use the tools right, you make the interaction easier; people see the value and buy into the concept. Once people buy into the concept, any initiative will grow and nurture itself.
This approach is exactly why we're having success with project-level KM. The ability to focus on core collaboration tasks and really get to the heart of what workers need is key to any KM initiative. [ADVANCE for Health Information Executives ]
Another example of some solid thinking about how to introduce KM into the organization. This article focuses primarily on how to support a transition from typical practices (e.g. e-mail and ad hoc documentation) to practices that will support improved knowledge management in the long run. If you look at the examples offered, it's clear that k-logs would be an ideal technology tool to meet KM needs at a project level.
A nice little mini-case.
[McGee's Musings]

See also: Blunt Force Trauma | Blunt Force Trauma | Blunt Force Trauma | ADVANCE for Health Information Executives | Past Articles | ADVANCE for Health Information Executives | Past Articles | This is the Title of Your Presentation | | Quicken Learning Center: WHO ARE YOU? | CIO Asia - Issue - Knowledge Deposits |

In the Same Room Does Not Mean on the Same Page

4:44:30 PM

comment []

How many times have you heard it said -- "Sometimes you just have to all get in the same room." Well, I've been in that room. And I can tell you that when 27 people walk out that door to go their 27 separate ways, they hold 27 different ideas about what they heard, what it means, and what they should do about it.
This cuts to the core of what goes wrong in many virtual teams and virtual organizations. Conference calls don't get it. More meetings don't help. The only thing that helps is getting people to expose what they are thinking in an open fashion. This essay at Technography is well worth your time. It is short, pithy, and to the point.
I don't know where he finds this stuff. This page has an original post date of January 1999. But Ron Lusk has done it again.

Technography: Group Journaling.
So here's the problem: Presentations, all be they clear, graphic, succinct, perhaps entertaining and even electronic presentations, do not a consensus build.
When all is said, and all the presentation presented, and the doing has to get done, the page we're on is not the same anymore. We each have a somewhat different understanding of what we supposedly learned. Informed as we have supposedly become, the information isn't part of our common knowledge.

[Ron Lusk's Radio Weblog]

See also: Galaxy ACE Awards | On the Same Page Cincinnati: About the Book Reviews and | Notre Dame Undergraduate Admissions-Get In Touch-ChatTime | The Officially Not -Unofficial Rob Bartlett Page | Gestalt Archive: LW Brandt and W. Metzger: 'Reality,' what does | moo-ms-users-guide | LWN: Letters to the editor | Compass - Issue 1, Spring 1998 | Duxbury Systems MegaDots -- About Braille | Steve's Fossil Shark Teeth ~ High Quality Megalodon, Great White

Radio -- More Than a Blog Tool

3:17:57 PM

comment []

Yeah, what Matt Mower said.
After reading and writing about blogging books yesterday I began to think about what it is that separates Radio from the other tools, and why this distinction is important.
I don't journal. There is nothing in my personal life worth remarking on, and tools that cater to the user who wants an online personal journal don't appeal to me. I enjoy reading some journals, but had that been all there was to Blogging I would never have tried it myself.
I'm more interested in business and learning, and I need a different tool. I want something that fosters collaboration with less structure, and less intimidation, than formal KM systems. I want to successfully run a virtual company -- something I now believe to be virtually impossible. But I think a transparent, user-friendly, addictive method for getting people to enter the collaborative system is mandatory for any chance of success.
So when I saw Radio's personal content management, networking, and k-logging possibilities I was hooked. It's still a little rough around the edges, but it's a great tool, and I can see tremendous possibilities for using it in business and learning environments.
I agree with Matt, Radio won't ever be right for everyone. There's no reason for it to be. Blogging is becoming a generic descriptor for a set of personal software tools, with specific types emerging for different users. As Dave Winer said:

In 2002, we're beginning to get to a category of software, with lines of delineation -- Movable Type is different from Manila, and Radio is different from Blogger, if one wanted to study a category, the products are lining up to accomodate. Other than that there's little that each blog has in common with other blogs.
There will be plenty of room for different tools in the future, and I look forward to seeing developments from all the BlogTool writers. My eyes have been opened to a new paradigm in web space. Many years ago I naively thought XML would kill the web as a personal medium, making it too inscrutable for all but the brainiest experts.
I was wrong. The BlgTool writers have taken XML to the masses, and it is good. There are many, many people who don't know it yet. But they will. And when they do there will be a BlogTool to meet their specific needs.

Why Radio?.
Why have I choosen Radio over MovableType? It's a question I've asked myself recently.
I think MT looks like an excellent blogging system. In a few years time I think that MT (or son-of-MT) is likely to be the choice for bloggers who need a little more than Blogger (or son-of-Blogger) will provide. I don't believe, as much as I love it, that Radio will be that choice.
However I do believe that Radio could be the klogger tool of choice. Why?
Because Radio has such potential in both a networked (social) and standalone (personal) context. Because Radio is a general computing platform that has been specialized to handle blogging but could also be specialized for a thousand other applications.
I, along with others, are looking to take it to the next stage with k-log ready tools. Userland are doing their part with things like Instant Outlining and RCS.
So, that's why Radio.
[Curiouser and curiouser!]

See also: Blunt Force Trauma | Dave's Handsome Radio Blog ! | Dave's Handsome Radio Blog ! | Blog Software MT and RU | Jake's Radio ' Blog : Thu, Aug 15, 2002 | Vic's Radio Blog | Radio Free Blogistan | Radio UserLand : Salon's blog and Radio | Comments on 95 | mesh on MX