Why people are central to PRINCE2 7

This is an independent course. PRINCE2 is a registered trade mark of the PeopleCert group. The scenarios, questions and examples in this course are original and are not taken from any PeopleCert exam or from the official manual. Amounts in the examples are in US dollars unless stated otherwise.

Projects are delivered by people, for people, and they change what people do every day. That sounds obvious, yet earlier editions of PRINCE2 said comparatively little about it. The method described roles, processes and controls in detail but left leadership, culture, communication and the human side of change largely to other bodies of knowledge. The seventh edition, published in 2023, changed that. It made people one of five integrated elements of the method, alongside the principles, the practices, the processes and the project context. This course is about that people element and about the context in which every project sits.

In this first lesson we look at why the change was made, what the people element covers, how it connects to the rest of PRINCE2, and how this course fits with the others in the PRINCE2 track. We also introduce a simple idea that runs through the whole course: a project can deliver every product on time and on budget and still fail, because the people who were meant to use those products never changed how they work.

The five integrated elements

PRINCE2 7 describes the method as five elements that work together. The principles are the foundation: seven universal obligations that every PRINCE2 project must honor, covered in depth in PRIN-110. The practices are the aspects of project management that must be addressed continually, such as the business case, organizing, plans, quality, risk, issues and progress. The processes describe the journey from starting up to closing. The project context recognizes that every project is different and must be tailored. And people sit across all of them, because every principle, practice and process is carried out by people and affects people.

The diagram is a reminder that the people element is not a new process step or a new management product. You will not find a single document called the people plan. Instead, people considerations appear in how the project board is formed, how plans are made with the people who will do the work, how risks are discussed openly, how progress is reported honestly and how products are handed over to the people who will use them.

What changed from the sixth edition

The sixth edition, published in 2017, organized PRINCE2 around seven principles, seven themes and seven processes, with tailoring as a separate topic. The seventh edition kept the sevens but renamed the themes as practices, made the people element explicit, gave the project context a more prominent role and added sustainability as a performance target. It also put more emphasis on digital and data management and on agile ways of working. For exam candidates, the practical consequence is that questions now ask about change management, team leadership, communication and organizational context as part of PRINCE2 itself, not as general knowledge.

Why projects fail on people

Studies of failed projects, from public inquiries to industry surveys, return to the same causes again and again: unclear ownership, weak sponsorship, resistance from the people affected, poor communication, unrealistic expectations and teams that did not trust each other enough to raise bad news. Very few failures are caused only by a missing template. A project with excellent documents and a disengaged executive will struggle; a project with modest documents and an engaged, honest leadership team will usually find its way.

PRINCE2 has always had controls that depend on people behaving well. Management by exception only works if team managers and project managers report forecast breaches early. Continued business justification only works if the executive is willing to stop a project. Learning from experience only works if people feel safe admitting what went wrong. The people element makes this dependency explicit and gives project managers language and techniques for creating the conditions in which the controls actually work.

Outputs, outcomes and benefits

PRINCE2 distinguishes three things a project produces. Outputs are the specialist products the project delivers, such as a new system, building or procedure. Outcomes are the results of change that occur when people use those outputs, such as staff processing applications faster. Benefits are the measurable improvements that result from outcomes and that someone values, such as lower cost per application. The chain from output to benefit passes through people. If nobody uses the new system, or if they use it while keeping their old spreadsheets on the side, the outcomes do not occur and the benefits do not arrive.

The example also shows why the people element belongs inside the method rather than after it. If the project had planned adoption from the start, it would have included training, support, process redesign and leadership communication as products in its plans, with quality criteria and owners, instead of treating them as an afterthought once the system went live.

The four topics of the people element

In this course we organize the people element under four headings that reflect how PRINCE2 7 treats the subject. The first is context: the organizations involved, the layers of management and the relationships between them. The second is leading successful change: helping the people affected move from how they work today to how they will work in future. The third is leading successful teams: forming and sustaining the temporary team that delivers the project. The fourth is communication: the planned, two-way flow of information between the project and everyone with an interest in it.

Two ecosystems

A useful way to picture the context of a project is as two overlapping ecosystems. The organizational ecosystem is the permanent world: the commissioning organization, its business units, its customers, its suppliers, its regulators and the communities around it. The project ecosystem is the temporary world created for the project: the board, the project manager, the team managers, the teams and the people who support and assure them. The project ecosystem sits inside the organizational one and borrows people from it. Most people on a project still have line managers, performance reviews and loyalties back in the permanent organization.

This overlap explains many of the tensions project managers feel. A specialist may be committed to the project on paper but pulled back to operational work whenever there is a crisis. A senior user may support the project in board meetings but face resistance from their own staff. A supplier's team manager may want to help but be bound by a contract that rewards different behavior. Understanding both ecosystems, and where they meet, is the starting point for everything else in this course.

Delegation, trust and management by exception

Management by exception allows each level of management to delegate authority to the level below within agreed tolerances. How much a board can delegate depends on how much it trusts the project manager, and how much a project manager can delegate depends on trust in team managers and teams. Trust is built through competence, honesty and reliability over time. A new project manager with an unfamiliar board may start with tight tolerances and frequent reports; as trust grows, tolerances can widen and reporting can lighten. PRINCE2 7 explicitly links the extent of delegation to the quality of relationships.

This is an important exam point. When a scenario asks why a board has set very tight tolerances, or why highlight reports are weekly rather than monthly, one valid explanation is that trust has not yet been established. The remedy is not simply to argue for wider tolerances but to build the relationship: deliver what was promised, report honestly and involve the board early when risks emerge.

How this course relates to others

This course assumes you have met the PRINCE2 basics in PRIN-101 and the principles in PRIN-110. It does not repeat the general theory of leadership styles, motivation, conflict and emotional intelligence; those are covered from a PMI perspective in PMP-120 and from an organizational behavior perspective in BUS-130. Here we keep a PRINCE2 lens. We ask how the people element shows up in PRINCE2 roles, management layers, management products, tolerances and tailoring, and how it is likely to be tested in Foundation and Practitioner exams. Where general theory helps, we summarize it briefly and point you to the deeper course.