1 / 7

A Design Theory For Systems That Support Emergent Knowledge Processes

A Design Theory For Systems That Support Emergent Knowledge Processes. M. Lynn Markus, Ann Majchrzak , and Les Gasser MIS Quarterly (2002) Gun- woong Lee. Overview. Motivation Problem: Unique requirements for EKPs (Process, User types, Users’ info. requirement)

paco
Download Presentation

A Design Theory For Systems That Support Emergent Knowledge Processes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Design Theory For Systems That Support Emergent Knowledge Processes M. Lynn Markus, Ann Majchrzak, and Les Gasser MIS Quarterly (2002) Gun-woong Lee

  2. Overview • Motivation • Problem: Unique requirements for EKPs (Process, User types, Users’ info. requirement) • Academic: Extant development methods does not meet the requirements • Practice: No guideline on how to build such systems • RQ • What are the design problems to support for emergent knowledge processes? • Why is a new design theory needed for EKPs? • What are the EKP design theory principles? • Theory: IS design Theory and organizational design theory • Research Methods: Field study (TOP Modeler) • Outputs • Instantiation: Top Modeler • Method: A set of design principles supporting EKPs

  3. Findings • Requirements for EKPs • Cannot target specific user groups • Accommodate complex and distributed knowledge bases • Support an unstructurable and dynamic process of deliberations • Development Principles to Support EKPs • Design for customer engagement by seeking out naïve users • Design for knowledge translation through radical iteration with functional prototypes • Design for offline action • Integrate expert knowledge with local knowledge sharing • Design for implicit guidance through a dialectical development process • Componentize everything, including the knowledge base

  4. Strengthens • Design as an Artifact • Method: The design principles • Instantiation: TOP Modeler • Problem Relevance (Effectiveness and Improvement) • Systems for EKPs is crucial to many organizations. • Design as a Search • TOP Modeler • Prototypes • Deployment -> Observation -> Identification -> Implementation

  5. Weaknesses • Generalizability • Theory from experience (?) • Restate the principles as a set of hypotheses • Test them in other situations with same hypotheses • Biased Observation and Misled conclusion • Limitation of field study • No criteria for estimating the effectiveness of at each iteration

  6. Unanswered Questions • Do the requirement and principles apply only to EKPs and EKP support systems? Can they also be applicable to other knowledge work processes (e.g., semi-structured decision making) ? • Are EKP support systems effective in all other contexts? • Differences in organizational structure and culture

More Related