PMP · Question #834
A team member has encountered a technical issue, similar to the one faced in a successfully closed project. However, the team member did not know about the previous project and would like to resolve t
The correct answer is D. Share the lessons learned from the previous project with the team member.. The project manager should share lessons learned from a similar previous project to efficiently resolve the current technical issue and prevent reinvention.
Question
Options
- AReach out to the project manager of the previous project for assistance.
- BAllow the team member to work through the issue as a training opportunity.
- CImprove the risk management strategy and risk monitoring.
- DShare the lessons learned from the previous project with the team member.
How the community answered
(42 responses)- A2% (1)
- B7% (3)
- C14% (6)
- D76% (32)
Why each option
The project manager should share lessons learned from a similar previous project to efficiently resolve the current technical issue and prevent reinvention.
Reaching out to the previous project manager might be a step if the lessons learned are insufficient, but the primary resource is the documented lessons learned.
While problem-solving is a learning opportunity, deliberately allowing a team member to struggle with an already solved problem wastes time and resources.
Improving risk management strategy is a broader process improvement, not the immediate action for a known, recurring issue.
Lessons learned are valuable organizational process assets that document challenges, solutions, and best practices from past projects. Sharing these directly with the team member allows them to benefit from previous experience, apply proven solutions, and avoid repeating mistakes, thus resolving the issue more efficiently and effectively. This also promotes knowledge transfer within the organization.
Concept tested: Utilizing organizational process assets (lessons learned)
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/current
Topics
Community Discussion
4
Orla P.Jun 26, 2026D is correct here. The PMI mindset is that lessons learned exist to be consulted, not archived and forgotten. A team member wanting to solve it independently is fine, but handing them the prior project notes simply gives them a baseline reference so they are not reinventing the wheel. Options A and B waste time or ignore organizational assets, and C is a long process fix when the team member needs help right now.
Mateus R.Jun 20, 2026D is correct here. Think of it like a farmer who keeps a journal of which crops survived the drought: if a neighbor is about to plant the same field and hit the same dry spell, you hand over that journal instead of letting him rediscover the hard way. The technical term is organizational process assets, specifically the lessons learned register, and the PM's job is to make sure that knowledge gets shared so the team member does not reinvent the wheel.
Lena V.Jun 25, 2026Going with A. The team member wants to solve it solo and is unaware of the prior project, so the PM looping in the previous PM gets you the actual lessons learned straight from the source rather than dumping a document on someone who already said they want to figure it out themselves.
Mateus R.Jun 27, 2026Actually Lena, the right call is D, because the PMs job is to point the team member toward the existing lessons learned so they can learn from them, not babysit the handoff. Think of it like a librarian pointing you to the shelf instead of calling the author for you: the knowledge is already captured, so the team member gets pointed to it and the PM stays out of the way.