Personalizing Knowledge Delivery Services for Emerging Knowledge Processes (EKPs): A Conceptual Framework

Abstract

The contents include: 1) What do most KMS in use today assume?; 2) Assumptions are violated when KMS is used by EKP workers - Why?; 3) Current State of KMS for EKPs are inadequate; 4) What would an "adequate" KMS for EKPs look like?; 5) "User-as-Consumer" Analogue: Ecommerce/Eem ployee Services; 6) Why is an ideal KMS for EKPs hard to achieve?; 7) So, what type of KMS design would work?; 8) Human-Based KMS for EKP - Proposal Call Managers at R&DLAB; 9) Proposal Call Managers (PCMs); 10) Specific PCM tasks; 11) Why is a R&DLAB PCM a human metaphor for a KMS for EKP?; 12) Data Collection; 13) Finding #1; 14) Finding #2; 15) Finding #3; 16) Factors affecting How/when; 17) Finding #4; 18) Finding #5; 19) Implication#l for a KMS for EKP: From System to Service; 20) Implication #2: From technology or human-centric to Mixed Mode; 21) Implication #3: From Simple User Profiles to Dynamic Delivery Profiles; 22) Implication #4: Maintaining a trustworthy environment; 23) Implication #5: Constructing a dynamic delivery profile; 24) Implications for Research: Model; and 25) Example Research Qs on KMS Support for EKPs.