A leadership style where the leader's main job is to serve the team by removing impediments and enabling its success.
Servant leadership is the mindset PMI emphasizes most strongly, especially in agile and hybrid environments. A servant leader prioritizes the team’s needs over personal authority, removes impediments, facilitates collaboration, and creates conditions for self-organization — acting as a coach and enabler rather than a director. The exam contrasts it with autocratic or directive leadership, where the leader retains decision-making authority; the servant leader pushes decisions to those closest to the work. Applying command-and-control to an empowered team is a classic wrong-answer trap.
The ability to recognize and manage your own emotions and those of others to guide behavior.
Emotional intelligence (EI) is a project manager’s power skill built on competencies such as self-awareness (recognizing one’s own emotions), self-regulation (managing them under pressure), empathy (sensing others’ feelings), and social skill (building relationships). A PM with strong EI detects team friction early, adapts communication to different stakeholders, and fosters psychological safety. The key exam distinction is that EI is not conflict management, though they are linked: conflict management applies specific techniques (collaborating, compromising, forcing) once conflict surfaces, while EI is the underlying capability that helps a PM prevent or navigate it. Scenarios describing a PM “reading the room” signal EI.
A document the team creates to set its ground rules, values, and working agreements.
A team charter is a document the project team creates collaboratively to establish shared norms, working agreements, and behavioral expectations. It typically covers communication preferences, decision-making protocols, conflict resolution approaches, meeting cadences, and accountability standards. Because the team authors it themselves rather than having it imposed by a manager or sponsor, members are more likely to honor its commitments. The exam often contrasts it with the project charter: the project charter formally authorizes the project and names the project manager, while the team charter governs how the team operates internally. Both coexist but serve different purposes — confusing them is a common scenario-question trap.
Clear expectations for the conduct and behavior of team members.
Ground rules are agreed-upon expectations for acceptable team behavior, communication norms, meeting conduct, and decision-making. Establishing them early — typically when the team charter is created during planning — prevents ambiguity and reduces interpersonal conflict later. Recorded in the team charter alongside team values and working agreements, they give the whole team collective ownership over enforcement rather than placing that burden solely on the project manager. The key exam distinction is that ground rules are one component of the charter, not a separate deliverable. This aligns with the proactive leadership emphasis in the ECO’s People domain.
Giving team members the authority and autonomy to make decisions about their own work.
Team empowerment means deliberately granting members authority to make decisions within their area rather than routing every choice through the project manager. In PMI’s Examination Content Outline it sits in the People domain and underpins high-performing, self-organizing teams in agile and hybrid work. The empowering PM removes impediments, secures resources, and sets clear boundaries, then trusts the team within them. Do not confuse it with delegation: delegation transfers a task, while empowerment transfers ongoing decision authority and accountability. Constant check-ins or approving every change describe micromanagement, not empowerment.
A team that decides internally how to accomplish its work rather than being directed by a manager.
A self-organizing team decides internally how to do its work and coordinates among its members rather than receiving task assignments from a project manager or functional lead. This idea is central to agile delivery in PMBOK 7 and the Agile Practice Guide: the project manager or Scrum Master acts as a servant leader, creating an enabling environment and removing impediments rather than directing the work. On the exam, both self-organizing and self-managing are team-level concepts; self-managing teams (2020 Scrum Guide language) extend the idea to also choosing what to work on. Answers showing a manager allocating tasks within a sprint are typically wrong in an agile context.
A model describing how teams progress through forming, storming, norming, performing, and adjourning.
Tuckman’s ladder describes five sequential stages a team moves through: forming (orientation, polite uncertainty), storming (conflict over roles and direction), norming (shared norms and trust emerge), performing (high productivity with minimal oversight), and adjourning (closure as the project ends). On the PMP exam it links leadership style to team maturity — a servant leader coaches heavily during storming, then steps back nearing performing. The key nuance: storming conflict is expected and healthy, not PM failure. Suppressing it tends to stall the team in storming, so the PM facilitates that friction rather than eliminating it.
Developing team members' skills and performance through guidance, feedback, and support.
Coaching and mentoring are related leadership practices project managers use to build team capability. Coaching is performance-oriented and often near-term: the coach asks questions, gives structured feedback, and guides the person to discover solutions rather than prescribing them. Mentoring is a longer-term, relationship-based bond in which a more experienced practitioner shares career wisdom and organizational knowledge. Both align with servant leadership and developing the team. On the exam, helping a member work through a challenge on the current project signals coaching; career guidance or knowledge transfer signals mentoring.
Activities that build the competencies team members need to perform their work effectively.
Training and development encompasses planned activities that build the skills, knowledge, and competencies team members need to meet project performance requirements. In PMBOK terms it is a tool of the Develop Team process within the Executing process group, ranging from formal courses and e-learning to on-the-job cross-training, job shadowing, and stretch assignments. The key exam distinction is that training adds a new competency, while coaching or mentoring refines competencies a member already has. When a skills gap surfaces during planning or performance assessments, training is the corrective action. Costs are typically planned into the project budget proactively.