Manage Project Knowledge

Sensei Short Scroll 28 Executing Process Group

Manage Project Knowledge

Introduction: Why This Matters

Knowledge is a critical asset in every project. Teams that fail to capture lessons repeat mistakes, while those that leverage organizational knowledge improve efficiency and innovation. The Manage Project Knowledge process ensures that both existing knowledge and newly created knowledge are applied effectively to current and future projects.

On the PMP exam, this process is often tested through situational questions about lessons learned, knowledge sharing, and using organizational process assets (OPAs). In practice, it enhances decision making, fosters continuous improvement, and strengthens organizational learning (Project Management Institute, 2021).

Purpose and Objectives

Primary Purpose: Use existing knowledge and create new knowledge to achieve project objectives and contribute to organizational learning.

Key Objectives:

  • Leverage historical information, lessons learned, and best practices.
  • Capture new knowledge created during the project.
  • Share knowledge across the team and organization.
  • Document lessons learned for future projects.
  • Foster a culture of collaboration and learning.

Overview

The Manage Project Knowledge process is supported by specific inputs, tools and techniques, and outputs that ensure knowledge is continuously captured, refined, and reused.

  • Inputs: Project management plan (quality, resource, communications, and stakeholder plans), project documents (including the lessons learned register and team assignments), enterprise environmental factors such as culture and technology, and organizational process assets like knowledge bases and historical databases.
  • Tools and Techniques: Knowledge management tools (communities of practice, collaboration platforms, expert networks), information management tools (document management systems, intranets, wikis), interpersonal and team skills (active listening, facilitation, knowledge sharing), and expert judgment from experienced project managers and subject matter experts.
  • Outputs: Updates to the lessons learned register, project management plan updates, and organizational process asset updates that store finalized knowledge for future projects.

Characteristics

  • Explicit knowledge: Knowledge that is easily codified and shared through documents, templates, and procedures. Example: A risk checklist from a previous project.
  • Tacit knowledge: Personal, experience based, and difficult to document. Example: An engineer’s intuition on system performance under stress.

Lessons Learned Register

  • The lessons learned register is updated throughout the project, not only at closure.
  • Early phase entries: Planning assumptions, estimation methods, and stakeholder feedback.
  • Mid phase entries: Issues encountered, effective risk responses, and resource performance insights.
  • Late phase entries: Test results, integration challenges, and customer acceptance lessons.
  • At project close, entries are finalized and archived in the organizational lessons learned repository.

Practical Example

Context: A financial firm is upgrading its IT security systems.

Activities:

  • Use existing knowledge: The project team reviews prior cybersecurity projects to avoid repeating vendor selection mistakes.
  • Create new knowledge: When implementing a new firewall system, the team documents configuration challenges and solutions in the lessons learned register.
  • Share knowledge: Weekly knowledge sharing sessions with IT staff ensure lessons are transferred across departments.
  • Organizational contribution: At closeout, lessons are uploaded to the company’s knowledge base for future projects.

Outcome: The firm strengthens its cybersecurity approach, avoids past mistakes, and improves readiness for future initiatives.

Common Pitfalls

Treating knowledge as documentation only

  • Pitfall: Relying only on written reports and documents.
  • Prevention: Balance explicit documentation with tacit knowledge sharing through dialogue and collaboration.

Capturing lessons too late

  • Pitfall: Waiting until project closeout to document lessons learned.
  • Prevention: Update the lessons learned register regularly during execution.

No feedback loops

  • Pitfall: Lessons learned are captured but never applied.
  • Prevention: Integrate lessons into OPAs and ensure they are accessible and used by future teams.

Cultural barriers

  • Pitfall: Team members are reluctant to share mistakes or challenges.
  • Prevention: Foster a safe environment that encourages open learning instead of blame.

Sensei Tip : Explicit knowledge lives in repositories. Tacit knowledge spreads through conversations, mentorship, and collaboration. Both are critical to project success.

Exam Alert : If the question mentions avoiding repeated mistakes, updating the lessons learned register during the project, or using organizational knowledge bases to guide decisions, it is usually pointing to Manage Project Knowledge rather than Close Project or Phase.

Exam Lens

Patterns on the PMP Exam:

  • If a question asks how to avoid repeating mistakes, the answer usually involves Manage Project Knowledge.
  • The lessons learned register is updated throughout the project, not only at closure.
  • Expect questions that distinguish between explicit and tacit knowledge.
  • Organizational process assets store knowledge for future use by other projects.

Sample Question

Question: A project team is reluctant to document lessons learned until the end of the project. What should the project manager do?

  1. Continue as planned since lessons learned belong in closeout.
  2. Encourage the team to update the lessons learned register continuously.
  3. Assign one person to document lessons learned at the end.
  4. Skip lessons learned since they are optional.

Correct Answer: B. Lessons learned should be documented throughout the project.

Quick Recap Table

Concept Description Exam Watch Point
Explicit knowledge Codified and easy to share, such as templates and reports. Stored in repositories and knowledge bases.
Tacit knowledge Experience based and hard to codify. Spread through mentorship, shadowing, and collaboration.
Lessons learned register Captures ongoing lessons during the project. Must be updated continuously, not only at closeout.
Organizational process assets Repositories and systems that store finalized knowledge and lessons. Provide inputs for future projects and planning activities.

Key Takeaways

  • Manage Project Knowledge leverages existing knowledge and creates new insights for continuous improvement.
  • Both explicit and tacit knowledge must be identified, shared, and applied.
  • The lessons learned register is updated throughout the project and then archived in OPAs.
  • On the PMP exam, favor answers that emphasize proactive knowledge sharing to avoid repeating mistakes.
  • In practice, effective knowledge management strengthens organizational maturity and future project success.

Next Step

With project knowledge managed, the next Executing process is Manage Quality, which ensures that quality assurance activities are carried out and processes are continuously improved during project execution.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.

Scroll to Top