Overview
This domain covers the importance of people in successful projects, the element the 7th edition made central to the method. It has four parts on this page: leading successful teams, leading change for the people affected by the project, communication with stakeholders, and how people sit at the centre of the method through roles, behaviours and organizational context. Two management products support it: the communication management approach and the change management approach, both part of the project initiation documentation (PID).
The domain exists because a project only creates value when people build its products and others use them. Outputs that nobody adopts produce no outcomes and no benefits, so this domain links directly to the business case practice. It also explains why the organization practice cares about relationships and culture, not only an organization chart.
How it's tested
People questions test understanding of concepts rather than procedure. Expect a short description of a situation, such as a team spread across two suppliers or a user group resisting a new system, and a question about what PRINCE2 says should be considered, which product records it, or which statement about leadership or communication is correct.
-
Which product covers it?
A need is described, such as planning how affected staff will be prepared, and you choose the management product that records it, usually the change or communication management approach.
-
Correct statement about people
Several statements about teams, leadership, culture or change are offered and you pick the one consistent with the 7th edition.
-
Change vs. change control
The stem uses the word change, and you must decide whether it means organizational change for people or the issues practice's control of changes to baselines.
A stem says users fear a new system will remove their discretion and asks what the project should do. Reason from the people element: their concerns are part of leading change, so the project should engage them early and plan support, recorded in the change management approach. Raising a request for change is the tempting distractor, but nothing about the product's baseline needs to change.
Syllabus topics 4
Official syllabus topics from the PeopleCert outline, in outline order.
3.1 Leading successful teamsHow temporary, cross-organizational project teams are formed, led and kept effective.
- What it means
- Project teams are temporary and often drawn from several departments and organizations, so they must be deliberately formed and led to work well together.
- What to understand
- Management covers planning, organizing and controlling; leadership covers setting direction, building trust and motivating, often by influence rather than line authority. Leadership is exercised at every level, by the board, the project manager and team managers, and team members remain accountable to their own organizations.
- How it shows up
- A stem describes a mixed team of internal staff and supplier staff and asks which statement about leading it is correct.
- Common confusion
- Assuming the project manager has line authority over everyone in the team; in a cross-organizational team, influence and relationships do much of the work.
3.2 Leading changePreparing and supporting the people affected by the project so its outputs are adopted.
- What it means
- A project changes how people work, so it must identify those affected, understand the impact on them, and plan how they will be engaged, prepared and supported through the transition.
- What to understand
- Adoption of outputs is what creates outcomes and benefits, so leading change is tied to the business case. The user side and the business typically own adoption, and the change management approach in the PID records how the project will handle it. Resistance is a signal to understand, not something to override.
- How it shows up
- Expect a question on which management product records how affected people will be prepared, or on why leading change matters to benefits.
- Common confusion
- Treating 'change' here as the issues practice's control of changes to baselines; leading change is about people and adoption.
3.3 CommunicationIdentifying stakeholders and planning how information flows to and from them.
- What it means
- Communication is the two-way exchange of information with stakeholders inside and outside the project, planned so that each group gets what it needs and the project hears their concerns.
- What to understand
- Planning starts by identifying stakeholders and analysing their interests and influence, then sets the message, method, frequency and responsibility for each. The communication management approach in the PID records this and is reviewed at stage boundaries.
- How it shows up
- A stem asks which product defines how and how often an external stakeholder group is informed.
- Common confusion
- Thinking the highlight report covers all communication; progress reports serve the project management team, while the communication management approach covers all stakeholders.
3.4 People central to the methodWhy the method depends on people in defined roles, their behaviours, and the organizational context and culture.
- What it means
- The method works through people: the project board, project manager, team managers and others apply the principles, practices and processes using their judgement, within an organizational context that includes culture and commercial relationships.
- What to understand
- Roles define accountability, but the success of the method depends on competence, behaviours and the relationships between the business, user and supplier. Organizational culture affects how far the method must be tailored and how teams and stakeholders behave.
- How it shows up
- Expect a statement-based question asking why people are an integrated element, or how culture influences the project.
- Common confusion
- Thinking that following the processes guarantees success regardless of who does them; the 7th edition stresses that people make the method work.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
People as an integrated element
The 7th edition places people alongside principles, practices, processes and project context as part of the method.
- Remember
- Projects deliver change through people, so people considerations apply throughout the project.
- Tested as
- Questions ask which element was added or emphasised in the 7th edition and why.
- Trap
- Treating people topics as soft extras outside the method.
-
Leadership vs. management
Management plans, organizes and controls; leadership sets direction, builds trust and motivates.
- Remember
- Both are needed at every level of the project, not only by the project manager.
- Tested as
- A stem describes behaviour and asks whether it is leading or managing.
- Trap
- Assuming leadership is a job title rather than a behaviour.
-
Cross-organizational team
A project team combining people from different departments or organizations, often including suppliers.
- Remember
- Members remain accountable to their own organizations, so the project relies on agreement and influence.
- Tested as
- Used in questions about leading teams and commercial relationships.
- Trap
- Assuming the project manager can direct supplier staff as if they were employees.
-
Change management approach
Part of the PID describing how the people affected by the project will be identified, engaged, prepared and supported so the change is adopted.
- Remember
- It is about organizational change for people, not about controlling changes to baselines.
- Tested as
- The product to choose when a stem concerns preparing users for new ways of working.
- Trap
- Confusing it with the issue management approach, which handles requests for change.
-
Communication management approach
Part of the PID describing stakeholders, their information needs, methods, frequency and responsibilities for communication.
- Remember
- Created in initiation and reviewed at stage boundaries.
- Tested as
- The product to choose when a stem asks how stakeholders will be kept informed.
- Trap
- Choosing the highlight report, which only informs the project board.
-
Stakeholder
Any person or group that can affect, be affected by, or perceive itself to be affected by the project.
- Remember
- Stakeholders include those affected by the outputs, not only people working on the project.
- Tested as
- Underpins communication and change questions.
- Trap
- Limiting stakeholders to the project board and team.
-
Stakeholder analysis
Identifying stakeholders and assessing their interest in and influence over the project to plan engagement.
- Remember
- It precedes deciding message, method and frequency.
- Tested as
- A stem asks what should happen first when planning communication.
- Trap
- Choosing to send a general newsletter before identifying who needs what.
-
Resistance to change
Concerns or opposition from people affected by the project, which often reveal real impacts on their work.
- Remember
- Understand and address it through engagement and support.
- Tested as
- Stems describe a reluctant user group and ask for the appropriate response.
- Trap
- Treating resistance as a disciplinary matter or ignoring it until go-live.
-
Organizational culture
The shared values and behaviours of the organizations involved, which affect how people respond to the project and its controls.
- Remember
- Culture is part of the project context and influences tailoring.
- Tested as
- May appear in statements about why the same method is applied differently in different organizations.
- Trap
- Assuming the method should be applied identically regardless of culture.
-
Adoption and benefits
Outputs only lead to outcomes and benefits when people use them as intended.
- Remember
- This is the link between the people element and the business case practice.
- Tested as
- Questions ask why leading change matters to the project's justification.
- Trap
- Assuming handover of products completes the value chain.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Change management approach vs. issue management approach
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Change management approach | How people affected by the project are engaged, prepared and supported | Concerns adoption of outputs and organizational change | Using it to approve requests for change to products |
| Issue management approach | How issues, including requests for change, are captured, assessed and decided | Concerns control of changes to baselines | Using it to plan training and support for users |
Communication management approach vs. progress reports
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Communication management approach | Plan for communication with all stakeholders inside and outside the project | Defines who receives what, how, how often and from whom | Assuming the board reports replace it |
| Highlight report | Regular progress report from the project manager to the project board | Serves the project management team only | Treating it as the channel for informing end users |
Leadership vs. management
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Management | Planning, organizing, monitoring and controlling work | Works through structure, plans and authority | Assuming management alone will gain commitment from a mixed team |
| Leadership | Setting direction, building trust and motivating people | Works through influence and relationships, at every level | Assuming only the project manager leads |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Change means change control
- What candidates pick
- Raise a request for change when users are anxious about a new system.
- Why it looks right
- The word change appears in both the people element and the issues practice.
- Why it's wrong
- Users' concerns about new ways of working are handled by leading change and the change management approach; nothing in the product baseline is being altered.
Clue to watch for If the stem is about people's reactions, training or adoption, think change management approach, not issue register.
-
Reports equal communication
- What candidates pick
- The highlight report as the way to keep a regulator or user community informed.
- Why it looks right
- Highlight reports are the regular communication most candidates remember.
- Why it's wrong
- Highlight reports go to the project board; communication with wider stakeholders is planned in the communication management approach.
Clue to watch for A stakeholder outside the project management team points to the communication management approach.
-
Line authority over the team
- What candidates pick
- The project manager instructs supplier staff directly as their manager.
- Why it looks right
- The project manager is responsible for day-to-day management of the project.
- Why it's wrong
- In cross-organizational teams people stay accountable to their own organizations; the project works through agreed arrangements and influence.
Clue to watch for Mentions of a supplier or another department signal that line authority does not apply.
-
Change at go-live
- What candidates pick
- Plan user training and support after the outputs are handed over.
- Why it looks right
- Training seems to belong at the point of use.
- Why it's wrong
- Leading change starts early by identifying affected people and engaging them; leaving it until handover risks rejection and lost benefits.
Clue to watch for Words such as fear, reluctance or impact on roles point to early engagement.
-
Leadership is the project manager's job
- What candidates pick
- A statement that leadership is the project manager's responsibility alone.
- Why it looks right
- The project manager is the most visible person on the project.
- Why it's wrong
- Leadership is expected at every level: the board, the project manager and team managers.
Clue to watch for Options with 'only' or 'solely' about leadership are usually wrong.
-
Process guarantees success
- What candidates pick
- A statement that applying the processes correctly ensures success regardless of who is involved.
- Why it looks right
- PRINCE2 is known as a structured, process-based method.
- Why it's wrong
- The 7th edition stresses that people make the method work; competence, behaviours and relationships matter.
Clue to watch for Absolute claims that a procedure alone guarantees an outcome are a warning sign.
Answer framework
Use this sequence when a question concerns people, teams, communication or change.
- Decide which people topic the stem is about: leading a team, leading change, communication, or people and culture in the method.
- Check whether 'change' refers to people adopting outputs or to altering a product baseline.
- Identify the stakeholders involved and whether they are inside or outside the project management team, because that decides whether board reports or wider communication planning applies.
- Match the need to its management product: change management approach or communication management approach, both in the PID.
- Reject options that rely on line authority alone, wait until handover to engage affected people, or claim that following the process guarantees success regardless of who is involved.
Practice question
Want more like this? The PRINCE2 7 Foundation practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Give this domain four to five hours and study it after the principles, because it builds on the define roles, responsibilities and relationships principle. Begin with the reason the element exists: outputs create value only when people adopt them. Then cover the four areas in this order: leading teams, leading change, communication, and people central to the method.
High-priority concepts are the two management products, the change management approach and the communication management approach, and the difference between leadership and management. The most commonly underestimated area is the overlap of vocabulary with the issues practice. Write a one-line test for yourself: is the stem about people's reactions and adoption, or about altering an agreed product? That single check resolves most traps here.
Because this content is new in the 7th edition, older practice questions and summaries may not cover it, so check that your materials are written for PRINCE2 7. After reading, answer a set of people-focused practice questions, then move to the organization and business case practices, where the same ideas reappear as roles, commercial relationships and benefits.
FAQ
Is the people element new in PRINCE2 7?
Yes. The 7th edition makes people one of the five integrated elements, with content on leading teams, leading change and communication that earlier editions did not treat as a separate part of the method.
How many questions come from this domain?
It is weighted at 14%, about eight of 60 questions. That is an estimate based on the published weight.
What is the difference between the change management approach and change control?
The change management approach covers preparing people affected by the project for new ways of working. Change control of products is handled by the issues practice through requests for change.
Which products support the people element?
The communication management approach and the change management approach, both part of the PID, created during initiation and reviewed at stage boundaries.
Do I need to memorise leadership models?
Focus on the distinctions the manual draws, such as leadership versus management and leading cross-organizational teams, rather than named external leadership theories.
Why does culture matter in PRINCE2?
Culture is part of the project context. It shapes how people respond to the project and so influences how the method is tailored.
How does this domain connect to the business case?
Benefits come from outcomes, and outcomes only occur when people adopt the outputs, so leading change protects the business case.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- CompTIA Project+ Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Certified Associate in Project Management Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 3 knowledge
Check that you can tell leading change from change control and pick the right management product for teams, stakeholders and affected users.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the PRINCE2 7 Foundation AI tutor Get any concept explained your way