Task 2: Lead a Team
Leadership is not about a title — it's about influence, vision, and the ability to bring out the best in people. The PMP exam tests this distinction relentlessly. Task 2 of the ECO People domain asks project managers to lead a team, which means setting a clear vision, choosing the right leadership approach for each situation, and inspiring team members to perform at their highest level. In PMI's modern framework, this means servant leadership, not command-and-control.
This study guide covers all three enablers for Task 2, the Tuckman model of team development, leadership styles for predictive and agile environments, key motivational theories, and exactly how to recognize correct answers on exam day.
ECO Enablers for Task 2
The Exam Content Outline identifies three enablers that describe what a project manager must do to lead a team effectively:
- Set a clear vision and mission. Leadership begins with direction. The project manager articulates where the team is going and why it matters. This isn't just about project objectives — it's about connecting the team's daily work to a meaningful purpose that motivates them.
- Determine and apply the appropriate leadership style for the situation and for different team members (servant leader, directive, collaborative). PMI explicitly endorses situational leadership. No single style works for every team, phase, or individual. The effective project manager reads the context and adapts.
- Distinguish the management and leadership styles and approaches for the team, determine the appropriate level of support, and inspire, motivate, and influence team members and stakeholders. This enabler captures the full spectrum of leadership — understanding when to manage (process, coordination, control) and when to lead (vision, inspiration, empowerment), and how to adjust your support based on each team member's needs.
These enablers draw heavily from PMBOK 7's Leadership principle, which states that effective leadership promotes project success and contributes to positive project outcomes. They also connect to the Team performance domain, which emphasizes shared ownership, a safe working environment, and continuous growth.
Servant Leadership: The PMI Gold Standard
If you remember one thing from this study guide, make it this: PMI favors servant leadership above all other leadership philosophies. The PMP exam will reward answer choices that reflect servant-leader behaviors and penalize those that reflect command-and-control, authoritarian, or micromanagement approaches.
Servant leadership, as defined in the Agile Practice Guide and reinforced throughout PMBOK 7, is characterized by:
- Putting the team's needs first. The leader's primary job is to remove obstacles so the team can perform.
- Empowering the team to make decisions. Rather than directing every action, the servant leader builds the team's autonomy and decision-making capability.
- Focusing on growth and development. The leader invests in each team member's skills, career, and well-being.
- Leading through influence, not authority. Servant leaders earn followership; they don't demand it through positional power.
- Listening actively and empathetically. Understanding the team's perspective comes before prescribing solutions.
- Building community. The servant leader fosters a collaborative, psychologically safe team culture.
When you encounter a question about how a project manager should interact with their team, scan the answer choices for servant-leadership behaviors: listening, removing obstacles, empowering, supporting growth, facilitating rather than directing. If you see answer choices like "tell the team what to do," "escalate to the functional manager," or "closely monitor every task," eliminate them — these contradict the servant-leadership philosophy that PMI expects.
Leadership Styles: Matching Approach to Context
While servant leadership is the overarching philosophy PMI endorses, the ECO explicitly mentions three leadership styles that the project manager must apply situationally:
| Leadership Style | Characteristics | Best Applied When… | PMI Exam Context |
|---|---|---|---|
| Servant Leader | Focuses on team needs; removes impediments; empowers; listens more than directs; builds consensus | Team is experienced and self-organizing (agile environments); team members are motivated and capable; the project benefits from distributed decision-making | Most correct answer. PMI's default expectation for modern project management, especially in agile and hybrid contexts. |
| Directive | Provides clear instructions; makes decisions unilaterally when needed; sets explicit expectations; closely guides work | Team is new or inexperienced; a crisis requires immediate action; safety or compliance demands unambiguous direction; the project phase has low tolerance for ambiguity | Acceptable in limited contexts. Correct only when the scenario explicitly describes a novice team, a genuine emergency, or a regulatory requirement for firm direction. |
| Collaborative | Facilitates group decision-making; encourages diverse input; builds consensus; leverages collective intelligence | Complex problems benefit from multiple perspectives; stakeholders have strong and legitimate differing views; team buy-in is critical for implementation success | Frequently correct. Collaborative leadership bridges servant leadership and directive styles — it's participatory without being hands-off. |
The Tuckman Model: Team Development Stages
No discussion of project team leadership is complete without Bruce Tuckman's model of group development. The PMP exam frequently presents scenarios that map to a specific Tuckman stage and asks what leadership approach is appropriate. You must recognize the stage from behavioral cues.
| Stage | Team Behaviors | PM's Leadership Approach | Exam Clues |
|---|---|---|---|
| Forming | Team members are polite but uncertain. They look to the PM for direction. Roles and responsibilities are unclear. Low conflict, low productivity. | Directive. Provide clear structure, define roles, set expectations, establish ground rules. The team needs guidance. | "Team members seem unsure of their responsibilities" / "The project has just kicked off" / "People are being careful and polite" |
| Storming | Conflict emerges. Team members push back on roles, challenge the PM's authority, disagree on approach. Different working styles clash. Productivity dips. | Coaching and facilitating. Address conflict directly (see Task 1), reinforce ground rules, mediate disagreements, keep the team focused on shared goals. | "There are disagreements about how to approach the work" / "Two senior team members are arguing" / "The team seems frustrated" |
| Norming | Team settles into rhythm. Roles are accepted. Collaboration improves. Team members begin supporting each other. Trust builds. | Supportive and collaborative. Step back from directive control. Encourage the team's growing autonomy. Recognize progress. | "The team is starting to work together smoothly" / "Members are helping each other" / "Processes are being followed" |
| Performing | High productivity. Team is self-organizing, autonomous, and effective. Members handle disagreements constructively without PM intervention. | Delegating and empowering. Servant leadership at its purest. The PM removes obstacles, provides resources, and stays out of the team's way. | "The team is delivering consistently" / "They resolve issues on their own" / "Minimal oversight needed" |
| Adjourning | Project ends or team disbands. Mixed emotions — pride in accomplishment, sadness at separation. Productivity may drop as members disengage. | Supportive and celebratory. Recognize contributions, facilitate knowledge transfer, ensure smooth transitions, conduct lessons learned, celebrate success. | "The project is winding down" / "Team members are being reassigned" / "Final deliverables are being handed over" |
Notice how the leadership approach shifts as the team matures: from directive (Forming) to coaching (Storming) to supportive (Norming) to delegating (Performing) to celebratory (Adjourning). This progression mirrors situational leadership theory and is a common exam theme.
Motivational Theories Every PMP Candidate Must Know
Leading a team means understanding what drives people. The exam tests several motivational theories, often by presenting a scenario and asking what theory explains the observed behavior. Here are the ones that appear most frequently:
Maslow's Hierarchy of Needs
People are motivated by unsatisfied needs, progressing from basic (physiological, safety) to higher-level (belonging, esteem, self-actualization). On the exam: if a team member's basic needs aren't met (job security threatened, hostile work environment), higher-level motivators like "challenging work" won't be effective.
Herzberg's Two-Factor Theory
Separates factors into hygiene factors (salary, work conditions, job security — their absence causes dissatisfaction but their presence doesn't motivate) and motivators (recognition, responsibility, growth, meaningful work — these actually drive performance). On the exam: if the scenario involves a team member who is dissatisfied, check whether the root cause is a missing hygiene factor or a missing motivator.
McGregor's Theory X and Theory Y
Theory X managers assume people are lazy, need close supervision, and avoid responsibility. Theory Y managers assume people are self-motivated, seek responsibility, and are creative. PMI overwhelmingly endorses Theory Y. If an answer choice reflects Theory X thinking (micromanagement, distrust, punitive approaches), it's almost certainly wrong.
McClelland's Three Needs Theory
People are driven by three needs in varying proportions: achievement (nAch — desire to excel), affiliation (nAff — desire for relationships), and power (nPow — desire to influence). Effective leaders tailor assignments and recognition to match individual need profiles.
You will encounter answer choices that imply the project manager should closely supervise team members, enforce strict rules, punish underperformance, or assume people can't be trusted. These reflect Theory X thinking. PMI's leadership philosophy — grounded in servant leadership, Theory Y, and the PMBOK 7 principles — rejects this approach. Even in difficult situations, the correct answer empowers and supports rather than controls and punishes.
Inspiring, Motivating, and Influencing: Practical Techniques
The third enabler mentions "inspire, motivate, and influence." The PMP exam expects you to know concrete techniques, not just theory. Here's how these concepts translate to project management practice:
- Inspire through vision. Connect daily tasks to the project's larger purpose. Help team members see how their work benefits end users, the organization, or society. A compelling "why" is more powerful than any deadline.
- Motivate through recognition. Publicly and privately acknowledge contributions. Tailor recognition to individual preferences — some value public praise, others prefer a private thank-you or increased autonomy.
- Influence through relationships. Build trust before you need it. Invest time in understanding each team member's goals, concerns, and communication preferences. When you need to influence a decision, the foundation of trust makes it possible.
- Model the behavior you expect. If you want the team to be transparent about risks, share your own uncertainties. If you want collaboration, collaborate visibly and frequently.
- Create psychological safety. Team members must feel safe to raise concerns, admit mistakes, and propose unconventional ideas without fear of punishment. This is explicitly emphasized in PMBOK 7 and the Agile Practice Guide.
Leading in Different Project Environments
| Environment | Leadership Emphasis | PM's Focus |
|---|---|---|
| Predictive (Waterfall) | Structured leadership with clear roles, formal authority, and documented decision-making. The PM plans, directs, and controls within the baseline. | Setting clear expectations, managing the plan, coordinating across phases, formal stakeholder communication |
| Agile (Scrum, Kanban) | Servant leadership is paramount. The PM (or Scrum Master) facilitates rather than directs. The team self-organizes and owns its commitments. | Removing impediments, protecting the team from external disruption, facilitating ceremonies, fostering continuous improvement |
| Hybrid | The PM must flex between directive and servant styles depending on which workstream is involved. Some processes may follow predictive governance while development work follows agile practices. | Tailoring leadership to each context, bridging communication between predictive and agile stakeholders, maintaining coherence across approaches |
| Virtual / Distributed | Intentional leadership is essential. Without physical presence, the PM must over-communicate, build trust deliberately, and use technology to maintain connection. | Ensuring inclusion across time zones, using video for high-stakes conversations, creating virtual water-cooler moments, monitoring engagement |
Key Terms and Concepts for the Exam
- Vision vs. Mission: Vision is the aspirational future state ("what we're building toward"). Mission is the actionable purpose ("what we're doing and why").
- Management vs. Leadership: Management is about systems, processes, and control — doing things right. Leadership is about vision, people, and influence — doing the right things. The exam values both, but leadership skills are weighted more heavily in the People domain.
- Referent Power: Influence derived from being respected and admired. This is the most effective and sustainable form of power for project managers, who often lack formal authority.
- Reward Power vs. Coercive Power: Reward power (ability to provide positive outcomes) is moderately effective. Coercive power (ability to punish) damages relationships and is the least effective long-term.
- Emotional Intelligence (EI): Self-awareness, self-regulation, motivation, empathy, and social skills. EI underpins effective leadership — it's covered in detail in Task 14.
Study Checklist for Task 2
- ✅ Can you describe servant leadership and recognize servant-leader behaviors in answer choices?
- ✅ Do you know the three leadership styles from the ECO (servant, directive, collaborative) and when each applies?
- ✅ Can you identify which Tuckman stage a team is in based on behavioral cues, and what leadership approach is appropriate?
- ✅ Do you understand Maslow, Herzberg, McGregor (Theory X/Y), and McClelland — and which each explains?
- ✅ Can you distinguish how leadership shifts between predictive, agile, hybrid, and virtual environments?
- ✅ Do you recognize that PMI favors Theory Y, servant leadership, and collaborative approaches over command-and-control?
Leading a team is the core of the People domain, and the principles you've studied here carry through every remaining People task. Continue to Task 3: Support Team Performance to learn how to appraise performance and foster growth, or go back to Task 1: Manage Conflict to review conflict resolution fundamentals.
← Back to ECO Study Guide Index | Practice People Domain Questions →