Any individual or group that can affect, be affected by, or perceive itself affected by the project.
A stakeholder is any individual, group, or organization that can affect, be affected by, or perceive itself as affected by a project decision, activity, or outcome. Identification begins early and is continuous — new stakeholders emerge across phases, so the Stakeholder Register is revisited throughout the life cycle. The key exam distinction is between identifying stakeholders (a discovery process) and managing their engagement (the ongoing effort to understand interests, address concerns, and foster participation). Simply listing stakeholders without assessing and adjusting engagement levels is insufficient.
The ongoing work of identifying stakeholders and managing their expectations and involvement throughout the project.
Stakeholder engagement is the continuous process of identifying, analyzing, planning, and actively involving stakeholders throughout the project life cycle to keep their expectations aligned with project objectives. It is not a one-time activity; the project manager must revisit engagement levels as the project evolves and stakeholder interests shift. The key exam distinction is between engagement and communication: communication is the information exchange, while engagement measures the depth of involvement and buy-in. The stakeholder engagement assessment matrix captures current versus desired engagement states (Unaware, Resistant, Neutral, Supportive, Leading), and closing that gap is the real goal, not simply sending status updates.
The process of identifying and handling disagreements constructively to keep the team productive.
Conflict management is a core people-domain skill in which the project manager identifies disagreements early and guides the team toward resolution using one of five recognized approaches: withdraw/avoid, smooth/accommodate, compromise/reconcile, force/direct, and collaborate/problem-solve. PMBOK and the ECO treat these as a spectrum, not a hierarchy of right versus wrong, because the appropriate technique depends on the situation, timeline, and relationship stakes involved.
The critical exam distinction is between collaborate/problem-solve and compromise: collaborating seeks a fully satisfactory win-win solution and is preferred when time allows and a lasting resolution matters, while compromising yields a middle-ground that leaves both parties partially unsatisfied. Forcing delivers a fast decision but damages trust, making it appropriate only for emergencies or non-negotiable constraints. Recognizing which technique fits the scenario described in a question—not just which is “best” in the abstract—is where most candidates lose points.
Reaching agreement between parties with differing needs through discussion and compromise.
Negotiation is a structured discussion used throughout the project to reach mutually acceptable agreements on resources, schedules, contracts, costs, and scope changes. The PMP ECO treats it as a core People-domain skill because project managers rarely hold direct authority over every party they depend on, making persuasion and compromise essential. The key exam distinction is between principled negotiation, which targets underlying interests and seeks win-win outcomes that preserve long-term relationships, and positional bargaining, where each side defends a fixed stance. PMP questions favor principled, collaborative negotiation. In contract scenarios, clear, well-defined requirements give the project manager the strongest negotiating foundation.
Frameworks such as Maslow, Herzberg, and McGregor that explain what drives people to perform.
Motivation theories give project managers a structured way to understand what drives team performance. Maslow’s Hierarchy ranks needs from physiological up to self-actualization, with lower-order needs satisfied before higher ones motivate. McGregor’s Theory X assumes workers are lazy and need direction, while Theory Y assumes they are self-directed and seek responsibility. The key exam distinction is Herzberg’s Two-Factor Theory: hygiene factors (pay, working conditions, job security) only prevent dissatisfaction — they do not motivate. True motivators are achievement, recognition, and growth. Improving hygiene removes a barrier rather than creating drive.
A responsibility assignment matrix marking who is Responsible, Accountable, Consulted, and Informed for each task.
A RACI chart is a type of Responsibility Assignment Matrix (RAM) that maps project activities to people across four roles: Responsible (does the work), Accountable (owns the outcome and signs off), Consulted (gives input before decisions), and Informed (notified of outcomes). The key exam distinction is between Responsible and Accountable: several people can share Responsible on one task, but exactly one person must be Accountable per activity—assigning Accountable to a committee is the classic trap. Unlike an organizational chart, which shows hierarchy, a RACI clarifies work-package ownership and prevents gaps or overlaps in responsibility.
A team whose members work from different locations and collaborate primarily through technology.
A virtual team is a group whose members fulfill their roles with little or no face-to-face contact, relying on communication technology to collaborate across geographic, time-zone, or organizational boundaries. The project manager must adapt team-building efforts in the Develop Team and Manage Team processes to bridge that separation. The exam nuance: virtual teams are not just “remote workers.” Because hallway conversations and body-language cues are unavailable, they introduce risks around trust, cultural differences, and communication latency that demand explicit ground rules, a communications management plan, structured check-ins, and collaboration tools.
The leader's work of identifying and clearing blockers that prevent the team from making progress.
Impediment removal is the ongoing work of identifying anything that slows, stops, or threatens the team’s progress and then actively resolving it. On agile or hybrid projects this responsibility belongs to the servant leader — most commonly the Scrum Master — who shields the team from organizational friction, resource constraints, conflicting priorities, and technical blockers so members can focus on delivering value. The key exam distinction is impediment versus risk: a risk is an uncertain future event, while an impediment is a current, active barrier already affecting the team. The PMP ECO frames this under the People domain task of supporting team performance, so expect questions applying it across predictive, agile, and hybrid contexts.
Fully concentrating on, understanding, and responding to a speaker to confirm the message is received.
Active listening is a communication technique in which the project manager gives full attention to a speaker, processes the meaning behind the words, and confirms understanding through paraphrasing, summarizing, and open-ended clarifying questions. It supports the Manage Communications and Monitor Communications processes and is central to the ECO People domain, where servant leadership and stakeholder engagement depend on genuinely receiving information rather than waiting to respond. On scenario questions, choose active listening whenever a stakeholder or team member feels unheard, misunderstood, or hesitant to raise concerns, because it reduces communication barriers and surfaces risks before they escalate.
Techniques teams use to reach decisions, such as voting, consensus, or fist-of-five.
Group decision-making encompasses the structured techniques a team uses to evaluate options and reach a shared conclusion. Common approaches include unanimity (full agreement), majority (more than half), plurality (largest block wins when no majority forms), and dictatorship (one person decides). Fist-of-five is a visual voting tool used in Agile contexts to gauge consent quickly. PMI emphasizes these techniques because involving stakeholders produces stronger commitment and reduces resistance to change. The key exam nuance is distinguishing consensus from unanimity: consensus means everyone can live with and support the decision, not that everyone agrees it is best. Facilitation and retrospective scenarios often hinge on this difference — a team can reach consensus without every member holding identical views.