PMP · Question #1149
A new team member inquires about how much they need to learn about the organizational process assets (OPAs) residing on the company intranet. Another team member states they only need to know the basi
The correct answer is C. Clarify the relevance of reviewing the documentation on the intranet.. A new team member is uncertain about the extent of learning organizational process assets (OPAs), receiving conflicting advice. The project manager needs to provide clear guidance.
Question
Options
- ACreate a training schedule for the new team member to follow over the next few weeks.
- BEscalate the inquiry to the team member's functional manager.
- CClarify the relevance of reviewing the documentation on the intranet.
- DAsk a senior team member to help the new team member navigate through all the documentation.
How the community answered
(24 responses)- A4% (1)
- B4% (1)
- C79% (19)
- D13% (3)
Why each option
A new team member is uncertain about the extent of learning organizational process assets (OPAs), receiving conflicting advice. The project manager needs to provide clear guidance.
Creating a training schedule is a means to an end; the project manager should first clarify the 'why' before dictating 'how much' training is needed to foster understanding and buy-in.
Escalating a simple inquiry about learning company assets to a functional manager is an overreaction and undermines the project manager's authority and ability to guide the team directly.
When there's conflicting advice and uncertainty, the project manager's role is to clarify the specific relevance and importance of the OPAs. Explaining *why* understanding the documentation is critical to the team member's role and the project's success provides context and motivation, enabling them to prioritize their learning effectively.
Asking a senior team member to help navigate is a good tactic for *how* to learn the OPAs, but it doesn't address the new team member's core question regarding the *relevance* and necessity of learning all the documentation.
Concept tested: Team onboarding and knowledge transfer
Topics
Community Discussion
8C is the answer here. The PM should clarify what is actually relevant for the new person instead of forcing them to memorize everything, since OPAs are huge and nobody needs all of it day one.
Agree on C but would add that tailoring the OPA info to the new person's role is what makes this relevant, not just trimming volume, since some org assets that seem irrelevant on paper end up being critical context later.
Got C on my exam last month, and the key is that the PM should not insist on full OPA coverage or brush it off with basics, but instead help the new member understand what is actually relevant to their role. Our study group unanimously agreed on C, though a couple folks initially leaned D thinking mentoring was the collaborative answer.
Thanks for confirming C, Anjali, and the role-based relevance point is spot on - just want to add that the PMBOK language around tailoring OPA to fit the situation is what makes C click if you see it again in a differently worded question.
I first leaned toward A because creating a training schedule seemed like a solid practical step, but the real issue here is that the PM expects the team member to know everything without explaining why. Once I re-read it, C made sense because the PM needs to clarify which OPAs are actually relevant to this project rather than overwhelming someone with the entire intranet.
Spot on with C, Nina, and remember the mnemonic PACE for these OPA questions: Pick what is relevant, Align to the project, Clarify expectations, and Educate the team, so the PM skips straight to the P and A steps instead of dumping the whole intranet on someone.
C is the pick here because PMP loves relevance over brute force. I call it the CAR trap: Choose A because you think training fixes everything, but that is overkill if the person does not need it. The PM should clarify what is actually relevant to the role, not force a newbie to memorize every template on the intranet. Option D is tempting because buddy systems sound nice, but the PM owns this clarification.
Adding to Fatima's point: the PM clarifying role expectations up front also prevents the buddy from passing on their own bad habits, which I have seen happen way too many times in teaching when new staff get paired with whoever is available rather than whoever is correct.