People: Leading, Developing, and Empowering the Team
The People domain is about the human side of projects: building trust, leading without heavy authority, resolving conflict, and creating the conditions in which a team can do its best work. It is roughly two-fifths of the exam, and the questions almost always ask what a project manager should do when people, not tasks, are the problem. The reliable mindset is servant leadership: the leader serves the team by removing obstacles, growing people, and empowering decisions, rather than commanding and controlling. As you study each section, practice reading a scenario and choosing the response that supports the team, addresses issues directly and early, and keeps people accountable without blame.
Leading vs. Managing and Servant Leadership
Managing is about handling the work: planning, coordinating, and administering tasks so things get done. Leading is about influencing people: setting direction, building trust, and motivating the team toward a shared goal, and a project manager must do both but leans on leadership for the People domain. Servant leadership inverts the traditional hierarchy: the leader's job is to serve the team by clearing impediments, providing resources, protecting focus, and enabling self-organization, which builds intrinsic motivation and accountability. This is not passive or soft; a servant-leader sets a clear vision, holds high standards, and gives honest feedback, but does so in service of the team's success rather than personal control. On the exam, favor answers where the project manager coaches, facilitates, and enables the team to solve its own problems over answers where the manager dictates the solution or bypasses the team.
Building the Team: Charter, Ground Rules, and Skills
A high-performing team is built deliberately, not assumed. Early on, the project manager assesses the skills the project needs, negotiates for the right people, and identifies gaps to close through training or mentoring. The team co-creates a team charter that captures its shared values, working agreements, and ground rules, such as how decisions get made, how meetings run, and how members treat one another; because the team writes these together, they own and enforce them. Clear ground rules prevent many conflicts before they start and give the team a fair, shared reference when behavior slips. The project manager also defines roles and responsibilities clearly, often using a responsibility assignment matrix, so everyone knows who does what and who decides. Investing in team formation up front pays back in fewer misunderstandings and faster, more autonomous execution later.
Developing the Team: Tuckman's Stages
Teams develop through predictable stages, described by Tuckman as forming, storming, norming, performing, and eventually adjourning. In forming, members are polite and dependent on the leader as they orient to the goal; the leader provides clear direction and structure. In storming, differences and power struggles surface as people push against roles and approaches; the leader coaches, facilitates conflict resolution, and keeps the team focused rather than suppressing the friction. In norming, the team settles into shared norms and starts to self-organize, and the leader can step back into a supporting role. In performing, the team is autonomous and highly productive, and the leader mostly removes obstacles and delegates. Recognizing which stage a team is in tells you how to lead: a storming team needs active facilitation, while a performing team needs space, and reorganizations or new members can push a mature team back into earlier stages temporarily.
Managing Conflict: Thomas-Kilmann Modes
Conflict is natural and, handled well, can strengthen decisions and relationships; handled poorly, it corrodes trust and slows delivery. The project manager addresses conflict early, directly, and in private, and seeks to understand each side before guiding a resolution. The Thomas-Kilmann model describes five conflict-handling modes along the axes of assertiveness and cooperativeness: collaborating (problem-solving to find a win-win, generally the most durable outcome), compromising (each side gives something, a lose-lose or partial win used under time pressure), accommodating (smoothing by yielding to preserve harmony), competing (forcing your position, appropriate only in emergencies or on principle), and avoiding (withdrawing, which leaves the underlying issue unresolved). The exam strongly favors collaborating and problem-solving as the default because it resolves the root cause and keeps both relationship and outcome intact, while forcing and avoiding are usually wrong unless the scenario is a genuine emergency. Always aim to confront the problem, not the person, and keep psychological safety intact.
Motivating the Team
Sustained performance comes from motivation, and the project manager tailors support to what actually drives each person. Classic theories give useful vocabulary: Maslow's hierarchy notes that basic needs must be met before higher ones like esteem and self-actualization; Herzberg distinguishes hygiene factors (salary, conditions) that only prevent dissatisfaction from motivators (achievement, recognition, growth) that truly energize people; McGregor's Theory Y holds that people are intrinsically motivated and will self-direct when trusted, versus Theory X's assumption that they must be controlled. Modern practice, echoed by frameworks like intrinsic motivation, emphasizes autonomy, mastery, and purpose over purely external rewards. Practically, the leader gives meaningful work, recognizes contributions genuinely and specifically, provides growth opportunities, and removes demotivators such as unclear goals or constant firefighting. Understanding individual drivers lets the leader match assignments and recognition to the person, which is far more effective than one-size-fits-all incentives.
Negotiating and Reaching Agreements
Project managers negotiate constantly: for people and resources, over scope and priorities, with vendors, and among stakeholders with competing interests. Effective negotiation is principled rather than positional: focus on underlying interests (what each side truly needs) instead of stated positions, separate the people from the problem, and seek options that create mutual value before dividing it. Preparation is decisive: know your objectives, your priorities, and your walk-away alternative before you enter the room. Aim for durable, win-win agreements that preserve the relationship, because on projects you will work with the same people again and a coerced deal breeds later resistance. When negotiating internally, the project manager relies on influence, data, and the project's business value rather than formal authority, which is why credibility and relationships built earlier pay off at the negotiating table.
Emotional Intelligence
Emotional intelligence (EQ) is often the difference between a competent project manager and an exceptional one, and it comprises self-awareness (recognizing your own emotions and triggers), self-management (regulating your reactions), social awareness including empathy (reading others' emotions and the room), and relationship management (handling interactions to guide people constructively). A leader with high EQ notices rising tension in a standup, understands the human cause behind a missed commitment, and responds with support and a plan rather than blame. EQ enables the leader to give difficult feedback without damaging the relationship, to stay calm under pressure, and to adapt their style to what each person and moment needs. It underpins nearly every other People skill: conflict resolution, motivation, negotiation, and stakeholder engagement all depend on accurately reading and responding to emotions. The exam rewards responses that show empathy and self-control while still moving the work forward.
Supporting Virtual and Distributed Teams
Distributed teams add challenges of time zones, culture, language, and the loss of informal, hallway communication that co-located teams take for granted. The project manager compensates deliberately: establishing shared communication norms and response-time expectations, choosing the right tools for synchronous versus asynchronous work, and making information transparent and accessible to everyone regardless of location. Meeting times are rotated fairly so the same region is not always inconvenienced, and the leader invests in relationship-building and virtual team ceremonies to counteract isolation and build trust. Cultural awareness matters: norms around directness, hierarchy, and feedback differ, and an inclusive leader adapts and sets explicit ground rules so no one is disadvantaged. Done well, a virtual team can reach the cohesion and output of a co-located one, but it requires intentional structure rather than assuming communication will just happen.
Empowering the Team and Decision-Making
Empowerment means pushing authority and ownership down to the people closest to the work, which speeds decisions and increases engagement and accountability. The project manager delegates not just tasks but the authority to decide, and clarifies the boundaries within which the team is free to act. Self-organizing teams decide how to accomplish the work and, in agile, pull their own tasks and estimate their own capacity, while the leader focuses on the what and the why and on removing obstacles. Empowerment requires trust and psychological safety: people must feel safe to make decisions, raise problems, and even fail without blame, or they will defer everything upward. The leader supports empowered teams by providing context, coaching, and air cover, and by resisting the urge to take back control when things get hard. On the exam, prefer answers that let a capable team own its decisions over answers where the project manager solves everything personally.
Removing Blockers and Shielding the Team
One of the servant-leader's most concrete daily jobs is to remove impediments so the team can keep flowing. Blockers surface in standups, retrospectives, and one-on-ones, and the leader tracks them visibly (for example on an impediment log or board) and drives each to resolution, whether that means chasing a decision, unblocking a dependency, or escalating a cross-organizational obstacle to the right level. The leader also shields the team from disruption: buffering unnecessary interruptions, pushing back on scope thrash mid-iteration, and protecting focus time so the team can sustain a healthy, productive pace. When a blocker is outside the project's authority, the correct move is to escalate it promptly and specifically to whoever can act, not to let the team sit stuck. Consistently clearing the path signals that the leader's role is to enable the team, which in turn builds the trust that makes empowerment and high performance possible.