Leading the Project Team
PMP PMP · People
What leading a project team means on the PMP exam
Leading the project team is the heart of the People domain, and the July 2026 Exam Content Outline gives it two tasks: lead the project team, and develop a common vision. The exam's view of leadership is specific and consistent: the project manager is a servant leader whose job is to make the team successful, not a commander whose job is to issue orders. A servant leader removes obstacles, shields the team from distractions, helps people grow, and earns authority through trust and competence rather than through a job title. This matters because the PMP is often taken by people who have led projects in organizations where authority comes from hierarchy, and the exam deliberately tests whether you can switch to the servant-leadership model.
Servant leadership shows up in the exam in very practical ways. When a team member is struggling, the servant leader coaches rather than punishes. When the team disagrees with a decision, the servant leader listens and involves them in finding a better one rather than overriding them. When the sponsor demands something unrealistic, the servant leader protects the team from an impossible commitment while still working transparently with the sponsor on alternatives. If you remember one sentence for the whole People domain, make it this one: the project manager serves the team, and the team delivers the project.
Building a team and developing a common vision
Teams do not arrive fully formed. PMI's exam expects you to know the classic stages of team development — forming, storming, norming, performing, and adjourning — and, more importantly, to know what a leader does at each stage. In forming, people are polite and uncertain, and the leader's job is to set direction and create safety. In storming, disagreements surface as people test boundaries; the leader's job is to let healthy conflict happen while keeping it productive, not to suppress it. In norming, the team agrees on how it works together. In performing, the team delivers with little supervision, and the leader's job is mostly to stay out of the way and remove obstacles. In adjourning, the project ends, and the leader's job is to recognize contributions and help people transition. Exam questions often describe a behavior — for example, team members arguing about how to do the work — and ask what stage the team is in and what the leader should do. The correct action always matches the stage.
A common vision is what holds a team together through those stages. The 2026 ECO gives "develop a common vision" its own task, which tells you how seriously PMI takes it. A vision is not a slogan on a slide; it is a shared understanding of why the project exists, what success looks like, and how each person's work contributes to it. The project manager develops it with the team, not for the team — people commit to a vision they helped create and merely comply with one that was handed to them. In practice this means workshops, kickoff meetings, and repeated conversations that connect daily tasks to the project's purpose. When a question describes a team that is demotivated or pulling in different directions, the missing ingredient is very often a shared vision, and the right first step is to build one together.
Team charters, ground rules, and working agreements
High-performing teams agree explicitly on how they will work together, and the exam tests the documents that capture those agreements. A team charter records the team's purpose, values, ground rules, decision-making approach, and expectations for behavior. Ground rules cover the everyday things that cause friction when they are unspoken: how meetings run, how quickly people respond to messages, how decisions are made, and how the team handles disagreement. In agile teams the same idea appears as working agreements, which the team creates and revises itself at the start of the project and updates in retrospectives. The key exam point is that these agreements are created by the team, not imposed by the project manager. A question that offers "the project manager writes the ground rules and tells the team to follow them" against "the team develops ground rules together" has only one PMI-correct answer.
Ground rules also matter for virtual and distributed teams, which the exam treats as normal rather than exceptional. Virtual teams need explicit agreements about working hours across time zones, which communication channels to use for which purpose, and how to make decisions when people are not online at the same time. They also need deliberate relationship-building: without corridor conversations, trust has to be built on purpose, through video calls, shared rituals, and making sure remote members are heard in meetings. When a question describes a virtual team member who feels excluded, the answer is almost always about inclusion and communication, not about technology.
Emotional intelligence and motivation
Emotional intelligence — the ability to recognize and manage your own emotions and to understand and influence the emotions of others — is one of the most tested ideas in the People domain. PMI expects a project manager to notice when a team member is frustrated, anxious, or disengaged, and to respond with empathy rather than with process. A question might describe a team member whose performance has dropped and offer options such as issuing a formal warning, reassigning their work, or having a private one-to-one conversation to understand what is going on. The conversation is the answer: understand before you act, and treat the person as a person before treating them as a resource.
Motivation works the same way. The exam draws on well-established ideas — that people are motivated by autonomy, mastery, and purpose as well as by pay and recognition — and expects you to apply them. Intrinsic motivators (meaningful work, growth, recognition, trust) matter more than extrinsic ones (bonuses, penalties) for the kind of creative, knowledge-based work most projects involve. Practical exam applications: recognize contributions publicly and specifically, give people challenging work that stretches them, and involve them in decisions that affect them. When a question asks how to motivate a team, the answer that gives people ownership and recognition beats the answer that offers a bonus or threatens consequences.
Supporting performance and handling underperformance
Supporting team performance means coaching, mentoring, training, and giving feedback — continuously, not once a year. Feedback should be specific, timely, and focused on behavior and its impact, not on the person. Coaching helps people solve their own problems rather than solving problems for them; mentoring shares experience and guidance over a longer relationship. Training fills skill gaps that coaching cannot. The exam expects you to choose the right tool: a skill gap calls for training, a confidence gap calls for coaching, and a motivation gap calls for a conversation about what is getting in the way.
Underperformance is handled the same way — understand first. The PMI sequence is: have a private conversation to understand the cause, agree on a plan to address it, provide support or training, and monitor progress. Escalation to a functional manager or human resources is a later step, taken only after you have tried to resolve it yourself and documented the effort. Disciplinary action is a last resort, not a first response. Exam questions love to test this sequence by offering an escalate-immediately option alongside an understand-first option; the escalate-immediately option is the trap.
Exam mindset for team leadership
Almost every People-domain question rewards the same instincts: serve the team, understand before acting, involve people in decisions that affect them, resolve issues at the lowest possible level, and protect the team from unreasonable demands. If an option involves the project manager deciding alone, punishing someone, escalating immediately, or ignoring a people problem in favor of a schedule problem, it is very likely wrong. If an option involves a conversation, coaching, a team agreement, or removing an obstacle, it is very likely right. The questions in this guide practise exactly that judgment.
Exam traps to watch for
- Choosing escalation as a first step. PMI expects you to try to resolve team issues yourself first — escalate only after you have tried and documented your own efforts.
- Confusing the stages of team development, especially storming (conflict is normal and the leader facilitates it) with a dysfunctional team that needs intervention.
- Imposing ground rules, a vision, or a decision on the team instead of developing it with them. Ownership comes from participation.
- Treating underperformance as a discipline problem before understanding the cause. The first step is always a private conversation to find out what is going on.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A project manager notices that a senior developer has become quiet in meetings, misses two deadlines, and seems disengaged. The project manager has not spoken to the developer about this yet. What should the project manager do FIRST?
Explanation: The PMI reasoning chain is: understand before you act. A change in behavior has a cause — it could be a personal issue, a conflict with a colleague, unclear requirements, or burnout — and the project manager cannot choose the right response until they know what it is. A private conversation is the servant-leader first step: it shows respect, builds trust, and gathers the facts. Option A is wrong because escalation is a later step, taken only after the project manager has tried to resolve the issue directly. Option B treats the symptom (missed work) while ignoring the person, and it signals to the team that struggling members get sidelined. Option C jumps to discipline before understanding, which is the opposite of the PMI mindset and would damage trust.
Exam objective: PMP ECO Task: Lead the project team (People)
Q2.A newly formed project team has just held its kickoff meeting. Team members are polite, agree with everything, and avoid raising concerns. Which stage of team development is this, and what should the project manager do?
Explanation: Polite agreement and avoidance of concerns are classic forming-stage behaviors: people do not yet trust each other enough to disagree openly. The leader's job at this stage is to set direction and deliberately create psychological safety so that honest discussion becomes possible — for example by inviting questions, admitting what is not yet known, and rewarding people who raise concerns. Option C is wrong: storming is the stage where disagreements surface, and the leader facilitates healthy conflict rather than stopping it. Option B is wrong because norming comes after the team has worked through disagreements and agreed on how to work together, which has not happened yet. Option D is wrong because a performing team works with little supervision and open debate, which is the opposite of what is described.
Exam objective: PMP ECO Task: Lead the project team (People)
Q3.A project team has been working together for three months but team members still seem to pull in different directions, and two members have said they do not see the point of the project. What is the BEST action for the project manager?
Explanation: When people pull in different directions and cannot see the point of the project, the missing ingredient is a shared vision — a common understanding of why the project exists and what success looks like. The vision must be developed WITH the team, because people commit to a vision they helped create and merely comply with one handed to them. Option D is wrong because schedule pressure does not create purpose; it creates stress. Option B is wrong because it treats a leadership failure (no shared vision) as a staffing problem, and replacing people does not fix the underlying issue. Option A is weaker than B: a sponsor message is one-way communication, and it does not create the team's own shared understanding.
Exam objective: PMP ECO Task: Develop a common vision (People)
Q4.A project manager is starting a project with a team spread across three time zones. What should the project manager do FIRST to set the team up for effective collaboration?
Explanation: Distributed teams need explicit agreements about how they will work together — overlapping hours, which channel to use for which purpose, how decisions are made when people are offline — and those agreements work only when the team creates them together, because the team then owns them. Option D is wrong because tools are secondary to agreements about how to use them, and imposing tools without discussion ignores the team's needs. Option A is wrong because a meeting time convenient for one group is inconvenient for the others, which is exactly the kind of exclusion working agreements exist to prevent. Option B is wrong because it tries to design away collaboration instead of enabling it, and it removes the team's autonomy.
Exam objective: PMP ECO Task: Lead the project team (People)
Q5.During a sprint review, a junior team member presents work that contains several errors. A senior team member publicly criticizes the work in harsh terms, and the junior member stops contributing. What should the project manager do FIRST?
Explanation: The project manager's job is to protect psychological safety: people who fear public humiliation stop contributing, and the team loses their ideas. The right first step is a private conversation with the senior team member about the impact of their behavior (not their character), combined with support for the junior member — for example coaching them on the work and encouraging them to present again. Option B blames the victim and ignores the real problem, which is the public criticism. Option D repeats the same mistake in reverse: public correction of the senior member creates the same fear in someone else. Option A punishes the junior member for someone else's behavior and removes a growth opportunity.
Exam objective: PMP ECO Task: Lead the project team (People)
Q6.A team member has the right skills but keeps missing the quality standard on deliverables. The project manager has already discussed the standard with them once, and the problem continues. What is the BEST next step?
Explanation: The PMI sequence for underperformance is: understand, support, monitor — and only escalate after genuine support has been tried. Coaching from an experienced colleague addresses the skill gap directly, and a short improvement plan with checkpoints makes expectations concrete and gives the project manager real evidence of progress. Option D is wrong because escalation is premature: the project manager has only had one discussion and has not yet provided structured support. Option A is wrong because lowering quality standards harms the project and is unfair to the rest of the team. Option C is wrong because silently removing work is neither transparent nor developmental — the team member cannot improve if they do not know there is a problem.
Exam objective: PMP ECO Task: Lead the project team (People)
Q7.A project manager wants to improve team motivation on a long, demanding project. Which approach is MOST aligned with PMI's view of motivation?
Explanation: PMI's view of motivation emphasizes intrinsic motivators — autonomy, mastery, purpose, and recognition — over extrinsic ones. Giving people control over how they work, recognizing their contributions specifically and publicly, and connecting their work to a meaningful purpose all build lasting motivation. Option C is wrong because individual cash bonuses for task volume reward speed over quality and create competition inside a team that needs collaboration. Option A is wrong for the same reason: ranking people against each other damages trust and psychological safety. Option D is wrong because artificial urgency causes stress and burnout, not motivation, and it usually reduces quality.
Exam objective: PMP ECO Task: Lead the project team (People)
Q8.A sponsor demands that the team work weekends for the next month to recover a two-week schedule slip. The team has already been working long hours and two members have mentioned burnout. What should the project manager do?
Explanation: A servant leader protects the team from unsustainable demands while still working transparently with the sponsor on realistic alternatives. The reasoning chain is: (1) the team is already showing burnout, so more overtime will reduce quality and cause more delays; (2) the schedule problem has other solutions — reprioritizing scope, adjusting the deadline, or adding resources; (3) the project manager's job is to bring the sponsor and the team together on one of those options. Option D is wrong because passing on an unreasonable demand without challenge is not leadership, and it will damage the team. Option C is wrong because flat refusal without offering alternatives is unprofessional and ignores the sponsor's legitimate concern. Option B is wrong because it accepts the unsustainable pace and offers compensation later, which does not prevent burnout now.
Exam objective: PMP ECO Task: Lead the project team (People)