Course Documents
     Main Page
     Contact Information
     Course Announcement
     Schedule and Syllabus
     Course Participants
     Discussion Forum
     Swiki Chat Area
     Lecture Material
     Independent Research
     Previous Course
Swiki Features:
  View this Page
  Edit this Page
  Printer Friendly View
  Lock this Page
  References to this Page
  Uploads to this Page
  History of this Page
  Top of the Swiki
  Recent Changes
  Search the Swiki
  Help Guide
Related Links:
     Atlas Program
     Center for LifeLong Learning and Design
     Computer Science Department
     Institute of Cognitive Science
     College of Architecture and Planning
     University of Colorado at Boulder
1.1. what did you find interesting about the article?

Not much.

1.2. what did you find not interesting about the article?

This just isn't a subject I'm that interested in, so I found the article a little dry.

2. what do you consider the main message of the article?

Real-time knowledge management is possible and will become commonplace in the future.

3.1. what are the strengths / successes of knowledge management?

Gathering data, storing data, accessing data.

3.2. what are the weaknesses /failures of knowledge management?

Having data in a format that can be processed and analyzed so that trends are recognizable.

4.1. what are your personal experiences with knowledge management

My software development team uses several sort of informal methods to ensure that information is available for all team members: a wiki and emails. I don't we're very effective in communicating all the information that is necessary to do our jobs.

4.2. what are your personal experiences with knowledge management systems?

Sales teams rely very heavily on database systems. As far as I know, these systems work relatively well for communicating information, but it really depends on how they are set up. Also, when the database is down, the sales people are completely unable to do their jobs. I think this makes them very vulnerable.

5. How would you differentiate between "pull" and "push" approaches in knowledge management? What are the trade-offs between the two approaches? In which situations would you use one or the other approach?

In a "push" approach, the system is more active by sending information to the user based on some preferences specified by the user; in a "pull" approach, the system is more passive and waits for a query from the user. "Push" requires more from the system and less from the user; "pull" is the opposite requiring more from the user and less from the system. A "push" approach can be useful when new information is constantly added to the knowledge base; the "pull" approach seems appropriate for systems in which the knowledge base is static.

6.1. "Those who cannot remember the past are condemned to repeat it." (George Santayana)

To learn from the past, we need to have historical knowledge and information available. Furthermore, the information needs to be in a format that can be analyzed.

6.2. "Innovation is everywhere; the difficulty is learning from it" (John Seeley Brown)

There is so much new information becoming available that it's difficult to have it all in a format that can be analyzed.

View this PageEdit this PagePrinter Friendly ViewLock this PageReferences to this PageUploads to this PageHistory of this PageTop of the SwikiRecent ChangesSearch the SwikiHelp Guide