The People domain is not the exam's pastoral wing. It is a family of tasks — lead, conflict, empower, train, unblock — that decide whether a technically sound plan survives contact with actual humans.
A task family, not a personality module
PMI's current exam content is organised by domains, not by the old process-group map. People is the first domain because delivery fails more often in relationships than in Gantt arithmetic. Treat it as a set of jobs you must be able to do: manage conflict, lead a team, support performance, empower others, train, build the team, remove impediments, negotiate, collaborate, create shared understanding, run virtual teams, set ground rules, mentor, and apply emotional intelligence.
That list is not a vibe. Each item is a task you can practise. 'Be a servant leader' is useless until you can name the next action: remove the blocker the team cannot reach, protect a retrospective from becoming a status meeting, or refuse to assign work the person has not been trained to do.
Organisations still call this 'the soft stuff' while missing another deadline caused by an unowned conflict. Plainly put, the People domain is operations. If you cannot run a difficult conversation, you do not have a process problem. You have a People-task gap wearing a RAID log.
What the People tasks look like on a Tuesday
Conflict: two seniors disagree on the design and the stand-up has become a cold war. Your job is not to pick a favourite in the corridor. Facilitate, name the disagreement, and get a decision with criteria. Ignoring it so the schedule 'stays green' is how you inherit an issue with a six-week tail.
Empowerment and training: a stakeholder wants the junior analyst to 'just own the integration.' If they have not been trained and do not have authority, that is not empowerment. That is abandonment with a motivational poster. Train, pair, or change the assignment. Mentoring is a task, not a coffee that never gets booked.
Impediments and virtual teams: the blocker that only the sponsor can move is still your task to surface. Distance does not excuse silence. Ground rules — response times, decision rights, what 'done' means — are how a distributed team stops inventing twelve cultures. Emotional intelligence here is noticing the person who has gone quiet, not writing a longer Slack message.
How to reason when the stem is a people problem
Ask three questions. Is this a relationship, authority, or capability issue? Has anyone spoken to the people involved, or are we leaping to a process weapon? Who actually has the power to act? If the answer is the sponsor, your next action is a clean escalation with a proposed path — not a pep talk in the team channel.
The exam — and the job — punish the nuclear option as a first move. Do not fire, reassign, or write a new RACI before you have talked to the humans. They also punish the opposite: endless listening while the milestone burns. Investigate, then act. Servant leadership is service with a spine.
Ethics sits inside People more than people admit. Favouring a friend in a vendor decision, hiding a team member's mistake from a sponsor, or letting a loud stakeholder rewrite ground rules for everyone else are People failures with Code of Ethics labels: fairness, honesty, respect. We will meet those again when interests compete.
Summary & next steps
People is a task family: lead, conflict, empower, train, unblock, negotiate, align, and use emotional intelligence on purpose. Treat it as work with owners and next actions, not as optional warmth.
Next: the Process domain — the delivery task family, and why it is not a synonym for 'do Waterfall harder.'