Search NASA⌕ Search

Engineering topics

Majchrzak, Ann

Publications and source records attributed to Majchrzak, Ann.

6 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Learning from project experiences using a legacy-based approach

As project teams become used more widely, the question of how to capitalize on the knowledge learned in project teams remains an open issue. Using previous research on shared cognition in groups, an approach to promoting post-project learning was developed. This Legacy Review concept was tested on four in tact project teams. The results from those test sessions were used to develop a model of team learning via group cognitive processes. The model and supporting propositions are presented.

knowledge reuse↗
NASA NTRS2003

Personalizing knowledge delivery services: a conceptual framework

Consistent with the call of the Minnesota Symposium for new theory in knowledge management, we offer a new conceptualization of Knowledge Management Systems (KMS) as a portfolio of personalized knowledge delivery services. Borrowing from research on online consumer behavior, we describe the challenges imposed by personalized knowledge delivery services, and suggest design parameters that can help to overcome these challenges. We develop our design constructs through a set of hypotheses and discuss the research implications of our new conceptualization. Finally, we describe practical implications suggested by our conceptualization - practical suggestions that we hope to gain some experience with as part of an ongoing action research project at our partner organization.

knowledge management↗
NASA NTRS2003

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

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.

knowledge management↗
NASA NTRS2003

Managing a project's legacy: implications for organizations and project management

Organizations that rely on projects to implement their products must find effective mechanisms for propagating lessons learned on one project throughout the organization. A broad view of what constitutes a project's 'legacy' is presented that includes not just the design products and leftover parts, but new processes, relationships, technology, skills, planning data, and performance metrics. Based on research evaluating knowledge reuse in innovative contexts, this paper presents an approach to project legacy management that focuses on collecting and using legacy knowledge to promote organizational learning and effective reuse, while addressing factors of post-project responsibility, information obsolescence, and the importance of ancillary contextual information. .

risk management↗