6.2 Manage Project Knowledge

6.2 Manage Project Knowledge
Inputs Tools & Techniques Outputs

Systematically use existing knowledge and create new knowledge so the project performs better now and future work benefits from what was learned.

Purpose & When to Use

  • Purpose: make smarter decisions by reusing what the organization already knows and capturing new insights as the project unfolds.
  • Use throughout the project, starting on day one, not only at closing.
  • Apply during planning to avoid past mistakes, during execution to solve problems faster, and at phase gates or major reviews to spread lessons.
  • Continuously update organizational assets so other teams can benefit later.

Mini Flow (How It’s Done)

  • Define knowledge needs: what the team must know to meet objectives and where gaps exist.
  • Find sources: organizational repositories, previous project artifacts, subject matter experts, and communities of practice.
  • Capture tacit knowledge: hold peer shares, interviews, shadowing, and retrospectives to surface experience-based tips.
  • Record explicit knowledge: document checklists, decision logs, playbooks, and lessons with clear context and recommended actions.
  • Validate and curate: have experts review, tag items with keywords, and store in the right repository for easy retrieval.
  • Apply and share: integrate insights into plans, risk responses, and processes; brief the team and stakeholders.
  • Track actions: assign owners and due dates for lesson follow-ups; update the lessons learned register regularly.
  • Update organizational assets: when a lesson changes a standard or template, route through change control and publish the new version.
  • Protect information: respect confidentiality and access rules while still enabling learning.
  • Measure and adapt: monitor reuse and outcomes (e.g., fewer defects, faster cycle time) and adjust the approach.

Quality & Acceptance Checklist

  • Knowledge needs are defined and linked to project objectives.
  • Relevant repositories and experts were consulted early and often.
  • Lessons include date, context, trigger, what happened, why it mattered, recommendation, owner, and status.
  • At least one knowledge-sharing event occurred after each major milestone.
  • New insights were applied to deliverables, plans, risks, or processes and are traceable to decisions.
  • Items are tagged, searchable, and stored in the approved location with version control.
  • Action items from lessons are tracked to closure and reflected in updated assets.
  • Sensitive information is handled per policy and access controls are in place.
  • Stakeholders confirm they can find and use the knowledge provided.

Common Mistakes & Exam Traps

  • Collecting lessons only at project close. Capture and use them continuously.
  • Storing insights without applying them to decisions, plans, or standards.
  • Focusing only on documents and ignoring tacit knowledge that emerges through conversation.
  • Confusing knowledge sharing with communications management. Knowledge management is about creating, curating, and reusing know-how; communications is about sending the right information to the right people.
  • Skipping expert validation, which leads to outdated or incorrect guidance being reused.
  • Not routing improvements through change control, so updates never make it into organizational assets.
  • Over-documenting without indexing, making content hard to find and unlikely to be reused.

PMP Example Question

A project manager wants to reduce risk by avoiding mistakes made on similar past projects. What should the manager do first?

  1. Schedule a lessons learned workshop at project closing.
  2. Create a new checklist based on the team’s current assumptions.
  3. Review organizational repositories and consult experts, then apply relevant lessons to the plan.
  4. Send a status report asking stakeholders to email any tips they recall.

Correct Answer: C — Review organizational repositories and consult experts, then apply relevant lessons to the plan.

Explanation: Start by reusing existing knowledge from organizational assets and experts, then integrate it into planning. Lessons gathering should be continuous, not only at closing.

AI for Agile Project Managers and Scrum Masters

Become an AI-first leader and transform your agile practice by leveraging artificial intelligence as your most powerful co-pilot. This course is designed to help you drive efficiency, insight, and innovation, ensuring you stay at the forefront of a rapidly evolving project management landscape.

This isn't about replacing human intuition—it's about augmenting it. You'll master prompt engineering to automate mundane tasks, freeing up your time for high-impact strategic leadership and creative problem-solving. Learn to refine backlogs, create strategic roadmaps, and integrate AI seamlessly into your agile ceremonies.

Gain predictive power by using AI-driven insights to anticipate project risks and seize new opportunities for more reliable outcomes. We deliver practical, prompt-based workflows and proven strategies built around real-world agile challenges that you can implement immediately within your framework.

Master foundational AI concepts specifically relevant to Scrum environments while developing advanced skills to handle diverse agile scenarios. You will learn to champion an AI-enabled culture within your organization, fostering a dynamic environment of continuous improvement and superior team delivery.

Learn alongside professionals around the world working in project leadership and delivery.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More