3.3. Lead the Project Team

💡 First Principle: Leadership on the exam means creating the conditions for a team to perform, not directing every task — establishing expectations, empowering the team, and adapting your leadership style to the situation are all tested as active PM responsibilities, not "soft" extras.

Enablers: establish team-level expectations, empower the team, solve problems, represent the voice of the team upward, support the team's varied experience/skills/perspectives, determine an appropriate leadership style, and establish clear roles and responsibilities.

"Determine an appropriate leadership style" is situational-leadership territory: a highly experienced, self-directing team needs a different style (delegating) than a newly-formed team still learning the domain (directing/coaching). PMI expects you to read team maturity and adapt, not apply one leadership style universally.

Choosing a leadership style

Situational leadership matches style to the team's competence and commitment:

A team inherited from a command-and-control manager, which waits for instructions and never offers opinions, needs coaching — and a gradual shift to participative decisions, starting with low-risk ones and publicly recognizing initiative. Adaptive leadership is the same idea over time: you move between styles as conditions change.

Servant leadership is PMI's preferred default because team expertise often exceeds the PM's own, making facilitation and empowerment more effective than direction. Servant leaders approach the work in the order purpose, people, process: clarify why, enable the people, then shape how they work. They shield the team, remove impediments, coach, facilitate, and build psychological safety. Two contrasts are tested. Laissez-faire leadership is passive and absent; servant leadership is active and intentional. And directive or transactional leadership — assigning tasks, managing through rewards and penalties — is the thing servant leadership replaces, which is why "ensuring the team does what you say" is never a servant-leader trait.

Influence without authority comes from expert power (competence) and referent power (relationships), which outlast legitimate (position), reward, and coercive power.

⚠️ Exam Trap: When a team asks you to "just decide" a design debate, deciding for them is usually wrong. The servant-leader move is to facilitate their decision — agree criteria, bring in expertise, time-box the debate — while you stay accountable for the outcome.

Team development

Tuckman's ladder runs forming (polite, avoiding disagreement, decisions made without real debate), storming (conflict over roles and approaches), norming (norms and cohesion form), performing (high, self-directed productivity), and adjourning (deliberate closure — acknowledging contributions, capturing knowledge, preparing people for their next assignment). Each stage calls for a different response: build trust and clarify roles in forming, normalize conflict and facilitate objective debate in storming, reinforce good behaviors in norming. Membership change resets the ladder — a performing team that loses a senior developer and gains a newcomer can regress within weeks, which calls for re-forming activities and refreshed working agreements, not blame.

The Drexler/Sibbet team performance model is a seven-stage sequence: orientation (why am I here?), trust building (who are you?), goal clarification (what are we doing?), commitment (how will we do it?), implementation, high performance, and renewal. Once why and who are settled, the next step is clarifying goals — not planning schedules.

Emotional intelligence

Two framings appear on the exam. The four-quadrant model is self-awareness, self-management, social awareness, relationship management; the older five-component version is self-awareness, self-regulation, motivation, empathy, social skills. Either way, self-awareness comes first: a PM who notices their own defensiveness in a steering meeting can regulate it before speaking. A PM whose frustration has made the team go quiet should own it, apologize, model self-regulation, and reopen communication. EQ outward looks like spotting stress signals and opening a conversation about workload, or helping an upset team member wait before firing back at a stakeholder.

Motivation

⚠️ Exam Trap: Offering a pay rise or bonus to a disengaged team that is already paid fairly. Pay is a hygiene factor — poor pay causes dissatisfaction, but raising pay that is already adequate creates no motivation. Look for career paths, learning, recognition, or linking project goals to personal goals.

Recognition should be public, specific, and prompt, balancing individual and team credit; where no formal program exists, recognize the work anyway and advocate for one. Feedback is the mirror image: specific, timely, about behavior, and private. Protect a sustainable pace — praise from stakeholders alongside falling team satisfaction usually means the pace is unsustainable, and sustained overtime calls for renegotiating scope or timeline, not more pressure.

Empowerment and decision rights

Empowerment is structure, not absence. Define decision boundaries and delegate categories of decisions explicitly; delegation runs on a spectrum — tell, sell, consult, agree, advise, inquire, delegate. When a team defers even trivial choices to you, or a once self-organizing Scrum team starts waiting on the Scrum Master, the likely cause is a leader who has been deciding for them. Self-organizing teams decide how and pull their own work; the product owner decides what.

Clear roles prevent both gaps and overlaps. A RACI matrix maps who is Responsible, Accountable, Consulted, and Informed for each deliverable. When vendor contractors and internal staff clash over who has final say, or client members defer business decisions to the delivery team, the fix is explicit decision rights communicated to both groups.

For group decisions, fist of five exposes the level of support and reservations rather than leaving a minority unheard after a majority vote. Dot voting or weighted scoring brings closure to a stalled debate once options are compared against agreed criteria. When a senior voice dominates, use silent brainstorming or anonymous polling before discussion to prevent groupthink, and actively invite quieter members in. Psychological safety — the belief that people can speak up, ask for help, and admit mistakes without punishment — is the foundation; a team that has gone mechanical in standups, or a member whose concerns keep getting reframed away, is a team that has lost its early-warning system. Rebuild it by modeling vulnerability, and correct a disrespectful remark in a meeting immediately and calmly, reinforcing the ground rules in the room.

Roles, expectations, and the team charter

The team charter sets team-level expectations: values, working agreements, communication norms, decision-making process, and the Definition of Done. It answers why we are doing this, who benefits, what done means, and how we will work together — performance indices such as SPI and CPI do not belong in it. Revisit it when a new team is slow and quarrelsome, and enforce it evenly: a long-tenured member who bypasses agreed processes gets a private conversation explaining that agreements apply to everyone.

Agile teams are small — the Scrum Guide recommends 10 or fewer — and cross-functional, built from T-shaped people (generalizing specialists: one deep skill plus broad general ones) using a whole team approach in which the team holds every skill needed without handoffs. When expertise sits in a silo, negotiate to dedicate that person to the team, at least partially. The Agile Practice Guide names three role types: cross-functional team members, the product owner (maximizes value, owns and continuously prioritizes the backlog), and the team facilitator (Scrum Master or coach, a servant leader). There is no "risk manager" role in Scrum, and neither prior agile experience nor any particular degree is a prerequisite for these roles.

Scrum events filed under this task

Retrospectives run at the end of each iteration, at milestones, or whenever the team needs one — not before any work exists. Formats such as starfish (keep doing, less of, more of, start doing, stop doing) structure the discussion; anonymous input helps a team that only reports good news. Watch for mechanical agile — ceremonies adopted without the values of collaboration and transparency — and for improvement items that fix symptoms while root causes persist.

⚠️ Exam Trap: Letting a manager or executive use the standup as a status meeting, or letting stakeholders assign work directly to developers. Redirect requests to the product owner, and offer the executive a separate briefing — protecting the team's focus is part of leading it.

Representing the voice of the team

You advocate upward. If a sponsor wants someone removed for underperformance you trace to unclear requirements, present the evidence. Negotiate with functional managers for qualified people — by understanding their constraints and proposing part-time or phased release — rather than accepting whoever is least busy. Remove blockers fast, and escalate only after direct attempts fail, bringing data on impact and a proposed solution. Reduce knowledge concentration through pair programming, knowledge-sharing sessions, and collective ownership.

Diverse, virtual, and global teams

Rotate meeting times so one region does not always carry the late call, gather input asynchronously before meetings, create informal "virtual water cooler" time, and guard against proximity bias on hybrid teams. When cultural norms may explain a behavior — agreeing in public but not following through, or treating self-set deadlines loosely — talk privately first to understand, then agree a communication approach together. Handle accommodations such as religious observance privately and respectfully.

Ethics in leading the team

The PMI Code of Ethics and Professional Conduct binds PMP holders to responsibility, respect, fairness, and honesty; violations can cost the credential. Falsified inspection reports or harassment are reported through the organization's formal channels — HR, an ethics hotline — not handled informally or ignored. When a sponsor pushes a costly late change or wants to skip testing, present the full impact honestly and let the authorized decision-maker decide through change control. Keep a team member's personal confidence, while quietly rebalancing their workload.

⚠️ Exam Trap: Choosing "empower the team to decide" as the answer even when the scenario describes a low-maturity or newly-formed team that needs more direct guidance — empowerment is the right instinct generally, but not the right answer for every team-maturity stage.

Reflection Question: Think of two different teams you've led with genuinely different maturity levels. How did (or should) your leadership style have differed between them?