b.cognosco
Where leaping to conclusions is my primary form of forward motion.
Most Popular
- Historical Yearly Average Gasoline Prices
- Outlook 2003 Message-ID Insanity
- Real-time Sand Animations
- Adobe Acrobat 7
- Adobe Announces Name Change and New Product
- Largest Technology Boondoggle in Public Education History
- Yahoo! Buys del.icio.us
- Skype - Disruptive, Not Compelling
- Aluminum Christmas Tree Museum
- Network Printing Hell and windoze XP
Book Reviews
Recently
Theme Design
IT Support
Hosting
Saturday, August 10, 2002
Integrated Blogging Functions and KM
I wonder how many of |Matt|'s points are covered with Traction Server, and how easily Traction can be integrated with other, larger systems? Also, with the work David Gurteen is doing in Lotus Notes, and Trellix now including weblogging functions, how long will it be before most KM systems include basic blogger functionality?Integrating klogs with Big-KM.In order for klogging to be successfully I think it is going to have to come to an understanding with Big-KM.
Example: BigCo has invested half a million dollars in a big knowledge management system for their world-wide operations. This kind of investment can become a lode-stone around any other systems neck. For klogging to thrive here it is going to have to integrate.
Here's one idea I have for how this could work.
- Extend Big-KM System-X so that it can aggregate RSS feeds like Radio, MT and others do now.
- Extend your klogging software to allow per-post meta data. (liveTopics does this for Radio)
- For each project in System-X define a set of topics that will act as trigger phrases for that project
- Get the kloggers to use those topics when they want to involve a post in a particular project
- Now subscribe System-X to every klog in the organization and watch as it indexes and archives all that information. Each project grabbing only those postings that are appropriate (by use of the trigger phrases)
- This means that the klogs add value to the big-KM system. Suddenly it doesn't just have the dry dusty project documention, but all the live vibrant stuff that people are really doing!
- Now extend System-X to generate a per-project RSS feed.
- If I am on the project I can subscribe to this feed. Now instead of receiving email from System-X or having to go to an arbitrary web page, I get all the "official" project stuff (new documents, forms etc...) delivered in my RSS stream.
Closing the loop between the big-KM and the klog so that they both add value to each other.
Just an idea... [Curiouser and curiouser!]
Posted by: 
Terry Frazier at 6:37 PM
| Permanent Link
| Trackback URL |
Categories: Collaboration, Strategy, Technology
Terry Frazier at 6:37 PM
| Permanent Link
| Trackback URL | Categories: Collaboration, Strategy, Technology
Tuesday, July 16, 2002
Start Small, Grow Right with KM for Projects
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.
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.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.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 ]
A nice little mini-case. [McGee's Musings]
Syndication
Contact
Presence
This Page was last updated: Wed, 02 Jul 2008 22:06:57 GMT
License: Unless otherwise expressly stated all original material, of whatever nature, created by Terry W. Frazier and included in this website, its related pages and archives, is licensed under a Creative Commons License, some rights reserved.
Disclaimer: This is a personal website. The views expressed here are those of the author and no one else. This is also an experiment in thinking out loud, so there are no warranties as to the reliability or accuracy of anything presented here. Source material -- references, citations, quotes, photos, and other elements -- are gathered from publicly available materials and some of it may be restricted. Any trademarks used are the property of their respective creators or owners. All are reproduced under the principle of Fair Use.