Thursday, April 24, 2008

Good overview of Klogging: Long Island Klogging Network?

"Klogging for Managers - 4/19/02; 10:44:41 PM by PW 1. Introduction. You are a Knowledge Weblog (klog) sales rep calling on an IT department and its customers. What tools do you need to explain your product? To make your case? To guide decision making? To boilerplate deployment and maintenance? You are a Manager who wants to bootstrap knowledge management on a shoe string. What tools do you want to avoid risks, pave the way for success, and to make the whole process fun? Here is a partial list of what a klogging tool vendor's marketing department might produce. Suggestions? 2. Why does Klogging work? whitepaper. Includes case studies and measures of success. Klogging meets some knowledge management goals. Personal Memory Control = Freedom to write Memory = Accessible History + Views Voice = Experience + Judgement Ease = Usage Emergent Knowledge Many voices, each unique, contribute to the body of knowledge. Interactions and social behavior produce second-order results; whole greater than sum of the parts The body of observation grows daily. It is the base for pattern analysis, trend detection, memetic propagation. Marketplace of ideas. Klogs' narrative form and easy citation by linking encourages discussion and debate. Community Identity Out of everyone in the world, you choose some to know better than the rest. Self organizing and affiliating. Meaning, wisdom emerge. Klogging overcomes previously experienced problems. Klogging vs. the 11 Deadly KM Sins "Drift or Shift", Fahey and Prusak, 1998 Motivation Context Memory Usability Klogging rewards people for doing what comes naturally. People tell stories. They observe what's going on and comment. They narrate their lives to themselves. They seek recognition and approval from others. They connect with each other. They try to matter, to influence their surroundings, to control a little of their world. Klogging gives people places to do this. Sanctioned places, safe and comfortable. Suggestions? 3. How do I deploy a klogging at my organization? Klogging Deployment Project Plan. See my project management templates page. Work Breakdown Structure (wbs). Stages and tasks in a model project. Plan Get Project Preapproval Assess Requirements Design Solution Get Project Approval Pilot Rollout Control Tim Jarrett suggests three approaches to deployment at a university: There are three ways to do it that I can see, each with its own merits and disadvantages: Centralized push. Have Sloan’s IT services folks set up a Radio Community Server and put Radio on every first year MBA’s laptop. In the classroom. Have a few professors start using Radio as a knowledge sharing mechanism and put part of the class participation grade for their students in how well they use their weblogs. Approach #2 might have some legs. There are some classes, including the introduction to IT class, a few of the marketing classes, and a class being taught on virtual communities, with which Radio is a natural fit. You might get the professors on board pretty quickly, with the students doing exercises in Radio for a semester. From the grassroots. Have a few bleeding edge folks get their sleeves up and evangelize it. Phil > Let's see if we can adapt this to other organizations. User referrals. A grassroots approach. Seed early adopters with the tool. Listen carefully for hot buttons. Probe for their serious problems and experiment with how the tool makes things better. Pilot projects. Like any pilot, you want to: prove your solution works, discover which features and practices: generated the most value, provoked the strongest positive emotional response learn the best ways to use it in this environment. (click for entire article)"

No comments: