Back to Top

C 5.0 Knowledge Management

Capturing, documenting, and sharing lessons learned and best practices in an organized fashion to reduce risk and improve performance on future programs/projects through the use of NASA processes and systems.

Select a competency from the outline menu or scroll down the page.

Categories and Competencies

Common Competencies


C 5.1 Knowledge Capture and Transfer

Identifying, capturing, evaluating, and transferring knowledge in an organized fashion to improve performance and reduce the risk associated with future programs, systems, and projects.

Underlying Skills

  • Clear communications
  • Leadership
  • Strategic thinking
  • Win-win negotiations
  • Working in teams

Fundamental Knowledge of:

  • Project mission, goals, and objectives
  • Project architectures and concepts
  • Team organization and make-up
  • Political, economic, and other factors that influence project goals

Explore proficiencies for each role.

Team Practitioner / Discipline Engineer

Proficiency Level

  • Participates as a project team member to gain an overall understanding of knowledge capture and transfer practices and to gain initial experience in the competency.
  • Actively seeks lessons learned and knowledge transfer from other project teams.
Illustrations
Team Practitioners/Discipline Engineers should be able to describe, identify, or define:

  • The importance and value of project learning in all stages of a project.
  • Lessons learned/best practices from previous programs, projects, and significant studies.
  • The steps to use NASA’s Lessons Learned Information System (LLIS).

Team Lead / Subsystem Lead

Proficiency Level

  • Leads teams (intact and at a subsystem level) in the execution of the knowledge capture and transfer process.
  • Provides guidance and expertise to team members, assisting in resolving issues.
  • Develops a Knowledge Management (KM) Plan that outlines knowledge sharing and transfer activities throughout the life of the project.
Illustrations
Team Leads/Subsystem Leads should be able to:
  • Communicate the value of project learning in all stages of a project.
  • Provide access to subsystem work products to the appropriate users.
  • Access relevant lessons learned applicable to the project over the life cycle of all project phases.
  • Capture appropriate knowledge and trends relating to project management and engineering issues within the subsystem for input into a knowledge management system.
  • Contribute to knowledge capture activities such as pause and learn sessions, case studies, and knowledge-sharing forums.
  • Evaluate lessons learned/best practices from previous programs, projects, and significant studies.

Project Manager / Project Systems Engineer

Proficiency Level

  • Leads teams at the project level in execution of the knowledge capture and transfer process.
  • Provides guidance and expertise at the project level, resolving project issues.
  • Actively supports the KM Plan implementation for project learning, reflection, and knowledge capture.
Illustrations
Project Managers/Project Systems Engineers should be able to:
  • Facilitate or plan project pause and learn sessions to capture lessons learned.
  • Develop lessons learned case studies.
  • Integrate the knowledge capture and transfer activities for their project.
  • Elicit and document lessons learned.
  • Direct the activities conducted by Team/Subsystem Lead in relation to this competency.

Program Manager / Chief Engineer

Proficiency Level

  • Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level internal, external, and international contacts.
  • Acts as KM Plan champion in support of all activities for project learning, reflection, and knowledge capture and transfer.
Illustrations
Program Managers/Chief Engineers should be able to:

  • Promote and require the effective application of lessons learned/best practices from previous programs, projects, and significant studies.
  • Lead and support team knowledge transfer activities.
  • Coordinate the development and maintenance of knowledge management systems that are useful for improving decision making, information sharing, and engineering issue resolution.
  • Establish proper knowledge management policy and processes.

C 5.2 Knowledge Sharing

Sharing organizational practices and approaches related to generating, capturing, and disseminating know-how and other content relevant to NASA’s business and processes.

Underlying Skills

  • Clear communications
  • Leadership
  • Critical thinking
  • Systems thinking
  • Strategic thinking
  • Win-win negotiations
  • Working in teams
  • Facilitation and meeting management
  • Complex decision making
  • Executive presentation skills

Fundamental Knowledge of:

  • Project mission, goals, and objectives
  • Team organization and make-up
  • Political, economic, and other factors that influence project goals

Explore proficiencies for each role.

Team Practitioner / Discipline Engineer

Proficiency Level

  • Participates as a project team member to gain an overall understanding of knowledge-sharing practices and to gain initial experience in the competency.
  • Carries out KM Plan activities that support knowledge sharing.
Illustrations
Team Practitioners/Discipline Engineers should be able to describe, identify, or define:

  • The distinction between knowledge sharing and knowledge management.
  • The distinction between tacit knowledge and explicit knowledge.
  • Agency and center practices and resources for capturing and sharing tacit knowledge.
  • The value and application of lessons learned/best practices.

Team Lead / Subsystem Lead

Proficiency Level

  • Leads teams (intact and at a subsystem level) in knowledge sharing.
  • Implements KM Plan activities for knowledge sharing.
  • Provides guidance and expertise to team members, assisting in identifying knowledge to share.
Illustrations
Team Leads/Subsystem Leads should be able to:
  • Design and facilitate team-based knowledge-sharing activities.
  • Procure agency and center resources to support knowledge sharing.

Project Manager / Project Systems Engineer

Proficiency Level

  • Leads teams at the project level in knowledge sharing in accordance with activities outlined in KM Plan.
  • Provides guidance and expertise at the project level, resolving project issues.
Illustrations
Project Managers/Project Systems Engineers should be able to:
  • Apply knowledge-sharing activities to enhance project performance.
  • Provide examples of the use and contributions of knowledge-sharing activities.
  • Encourage the application of knowledge-sharing principles within their project.
  • Capture and share the project’s tacit knowledge with other projects at the center and/or agency.
  • Contribute documented project lessons to be placed in the NASA/NEN LLIS across all phases of the project.
  • Know what agency resources best provide relevant knowledge to their project team.
  • Host knowledge sharing/lessons learned forums at the conclusion of projects.

Program Manager / Chief Engineer

Proficiency Level

  • Leads overall effort, reviews and approves products, resolves issues, and maintains relationships with the highest level internal, external, and international contacts.
  • Acts as champion for all activities for knowledge sharing as outlined in the KM Plan.
Illustrations
Program Managers/Chief Engineers should be able to:

  • Define agency knowledge requirements, resources, and activities.
  • Lead strategy to create a culture of knowledge capture and application of lessons learned/best practices.