Study guide
PMI's Examination Content Outline effective July 2026 groups the human-relationship work of running a project under the People domain, which makes up roughly a third of the exam (33%). Most questions in this domain are situational: you are typically given a scene already in progress and asked what the project manager should do next, so the goal here is judgment, not memorization.
Building a Shared Vision and a Working Team
A project team rarely arrives already aligned. People join from different departments, vendors, or even different companies, each carrying their own assumptions about what success looks like. Early in a project, the project manager's job is to convert a sponsor's one-paragraph business case into a picture the whole team can see and agree to. This is the shared vision: a plain statement of why the project exists, what done looks like, and how each person's work ladders up to it. Without it, a developer and a business analyst can both work hard all sprint and still pull in different directions. Consider Priya, who is asked to lead a claims-processing upgrade. Instead of starting with a task list, she holds a kickoff where the team drafts a one-sentence purpose statement together and posts it in the team's workspace. Later, when a debate breaks out over whether to build a flashy reporting dashboard or fix a slow approval step first, the team resolves it by asking which choice serves the stated purpose. On the exam, when a scenario shows a team arguing about priorities with no shared reference point, the better answer is usually to facilitate agreement on vision or objectives before jumping to a technical fix. This lines up with the PMBOK Guide's emphasis on stewardship and creating a collaborative team environment: the project manager's first duty is often to the health of the team's shared understanding, not to any single deliverable.
Managing Conflict Constructively
Conflict on a project is not automatically a problem to eliminate; unresolved or poorly handled conflict is the problem. Healthy disagreement about approach can surface risks early and improve decisions. The situational skill being tested is recognizing which conflict-handling mode fits the moment. Five common modes appear across project management literature: withdraw or avoid (postponing the issue), smooth or accommodate (emphasizing agreement over the disagreement), compromise (each side gives up something), force or direct (one party imposes a decision, appropriate mainly for safety or compliance issues), and collaborate or problem-solve (working together to find a solution that satisfies everyone's real interests). Collaboration generally produces the most durable outcome because it addresses root causes, but it takes the most time and trust, so it is not always the right tool under a hard deadline. Picture Devon, a scrum master, noticing two engineers repeatedly clashing over code review standards. If Devon simply assigns them to different modules to avoid friction, the underlying disagreement about quality standards will resurface elsewhere. A stronger move is a facilitated conversation where both engineers state their concerns and agree on a shared review checklist. Exam scenarios often describe a conflict and then offer one answer that avoids the conflict, one that forces a decision, and one that facilitates a joint solution; absent a safety, ethics, or hard-deadline reason to force it, PMI's servant-leadership orientation favors facilitating collaboration and addressing the conflict directly rather than escalating immediately or ignoring it.
Leading Through Servant Leadership and Empowerment
The Agile Practice Guide and the PMBOK Guide both describe a shift away from command-and-control management toward servant leadership, in which the project manager's primary role is removing obstacles, protecting the team's focus, and developing people's capability rather than directing every task. A servant leader asks what the team needs to succeed and then works to supply it: clearing a bureaucratic approval, shielding the team from a barrage of side requests, or coaching a quieter team member to speak up in planning sessions. This does not mean the project manager disappears; it means authority is used in service of the team rather than over it. Empowerment follows naturally: teams that are closest to the technical work often make better day-to-day decisions than a manager relaying instructions from above, so mature project leaders push decision-making downward and reserve their own involvement for genuine blockers, cross-team dependencies, and matters that require organizational authority. Take Marcus, leading a hybrid infrastructure project, who notices his team hesitating to make a database schema change without his sign-off even though it is squarely within their expertise. Rather than approving each detail, Marcus asks the team to document their reasoning and make the call themselves, checking in only if the change affects another team's timeline. On exam questions, answers that describe the project manager personally solving a technical problem the team is capable of solving are usually wrong; answers that describe coaching, clearing impediments, or delegating authority to the team are usually right.
Engaging Stakeholders and Aligning Expectations
Stakeholders are anyone who can affect or be affected by the project, and they rarely share one unified opinion about what the project should deliver. A sponsor may want speed, a compliance officer may want documentation, and end users may want a familiar interface. The project manager's job is not to make every stakeholder equally happy but to understand each one's interest and influence, communicate honestly about tradeoffs, and keep expectations grounded in what the project can realistically deliver. This starts with identifying stakeholders early, including ones who are easy to overlook, such as a night-shift support team or a downstream vendor. A stakeholder engagement approach then maps how much involvement each group needs and how they prefer to receive information. When expectations drift, for example a stakeholder who assumed a feature was in scope when it was not, the fix is a direct conversation, not silence and hope. Consider Elena, managing a hospital scheduling system rollout, who learns that a nursing supervisor expected a mobile app even though the approved scope covers only desktop access. Elena's best move is to meet with the supervisor promptly, explain the scope decision and its reasoning, and jointly decide whether to raise a change request or manage the expectation. On the exam, when a stakeholder's expectations diverge from the plan, look for the answer that re-engages the stakeholder directly and transparently rather than one that quietly proceeds or escalates without first having that conversation.
Knowledge Transfer and Managing Communication
Projects end, but the knowledge generated during them should not disappear with the team. Knowledge transfer means deliberately moving both explicit knowledge, such as documented procedures and specifications, and tacit knowledge, the informal know-how in people's heads, to the people who will operate, maintain, or continue the work. This might mean pairing a departing contractor with a permanent employee for two weeks, recording a walkthrough of a complex configuration, or holding a structured handover session before a team disbands. Communication planning is the broader discipline underneath this: deciding what information different audiences need, how often, through what channel, and in what format, then adjusting as the project evolves. A common exam trap is treating communication as something that only flows from the project manager outward; effective communication planning also creates channels for the team and stakeholders to send information back, including bad news. Consider Tomas, closing out a manufacturing automation project, who realizes the maintenance team was never looped into the vendor's escalation contacts. Rather than closing the project as scheduled, Tomas arranges a short knowledge-transfer session and hands over a living document the maintenance team can update. When exam scenarios describe a transition, a departing team member, or a stakeholder who says they were never told something, the situational answer usually involves proactively building or repairing a communication or knowledge-transfer mechanism rather than assuming information will find its way to the right people on its own.
Key terms
- Servant leadership
- — A leadership style in which the project manager prioritizes removing obstacles, developing team members, and serving the team's needs over directing and controlling their work.
- Shared vision
- — A common understanding among team members and stakeholders of the project's purpose and definition of success, used to align decisions and priorities.
- Conflict-handling modes
- — Approaches to resolving disagreement, commonly described as withdraw/avoid, smooth/accommodate, compromise, force/direct, and collaborate/problem-solve.
- Empowerment
- — Delegating decision-making authority to the people closest to the work, rather than routing every decision through the project manager.
- Stakeholder
- — Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by a project's decisions or outcomes.
- Stakeholder engagement
- — The ongoing process of understanding stakeholders' interests and influence and building and maintaining relationships with them to meet project needs.
- Knowledge transfer
- — The deliberate transmission of both documented (explicit) and informal, experience-based (tacit) knowledge from one person or team to another.
- Communication management plan
- — A plan describing what information stakeholders need, how often, through which channel, and in what format throughout the project.
- Tacit knowledge
- — Informal, experience-based know-how that is difficult to document and is usually transferred through mentoring, pairing, or direct observation.
- Self-organizing team
- — A team empowered to decide, within agreed boundaries, how to accomplish its work rather than being directed task-by-task by a manager.
- Emotional intelligence
- — The capacity to recognize, understand, and manage one's own emotions and to recognize and influence the emotions of others, a core power skill for project leaders.
Exam tips
- When a scenario describes team disagreement with no safety or compliance urgency, favor answers where the project manager facilitates the team toward its own resolution over answers where the project manager decides for them.
- Watch for answers where the project manager personally fixes a technical problem the team is capable of solving; empowering the team is usually the stronger choice unless a cross-team or organizational blocker requires the project manager's authority.
- If a stakeholder's expectations have drifted from the agreed scope, the situational answer almost always starts with a direct conversation with that stakeholder before any process step like a change request.
- Treat 'escalate immediately' and 'do nothing and hope it resolves' as usually-wrong extremes; the middle path of addressing the issue directly at the lowest appropriate level is typically correct.
- Knowledge-transfer and communication questions often hide the real issue in a transition, handoff, or closing scenario — check whether information is reaching the people who need it, not just whether a status report was sent.