People, the project context and tailoring

Two of the five integrated elements of PRINCE2 7, people and project context, were made explicit for the first time in the seventh edition. They address a long-standing criticism of earlier editions: that PRINCE2 described processes and documents well but said little about the humans who actually deliver projects or about how the method should change from one environment to another. This lesson gives an overview of both elements, introduces the guidance on digital and data management, and shows how tailoring brings everything together. PRIN-120 studies people and context in depth, and PRIN-150 returns to tailoring.

Why people became an integrated element

Projects are delivered by people, for people, and they change what people do. A project can have an excellent plan and still fail because the team does not trust one another, the sponsor communicates poorly, users resist a new system or a supplier relationship turns adversarial. PRINCE2 7 places people at the center of the method and describes several areas that project managers and boards must pay attention to:

• Leading successful change: projects create change, and the people affected need to understand, accept and adopt it for benefits to be realized.
• Leadership: the behaviors of the board, project manager and team managers shape how the project works, from setting direction to supporting the team.
• Culture: organizational and team culture influences decision-making, risk appetite and openness about problems.
• Teams and relationships: a project brings together people who may not have worked together before, often from different organizations and with different incentives.
• Communication: effective, two-way communication with the team, stakeholders and those affected by change.

For the exam, you should be able to explain why people matter to project success and how the people element connects to the principles and practices. For example, the principle of defined roles, responsibilities and relationships depends on people actually working well in those roles, and the organizing practice now explicitly covers relationships and communication.

The project context

The project context is the environment in which the project operates. It includes the organization or organizations involved, their policies and governance, the commercial relationships, the relationship to any program or portfolio, the delivery approach, the scale and complexity of the project, the regulatory environment, and expectations about sustainability. Context determines how PRINCE2 should be tailored. PRINCE2 7 discusses several common contexts:

Digital and data management

PRINCE2 7 also gives guidance on managing digital and data aspects of projects. Most project information now lives in digital tools, and many projects deliver digital products or rely on data. The guidance encourages projects to think about how project information is created, stored, shared and protected, how data quality affects decisions, and how automation and analytics can support project management. It also recognizes risks such as poor data quality, information overload and security or privacy breaches.

In the United States, data management on projects must respect a patchwork of privacy and security rules: sector laws such as HIPAA for health information and GLBA for financial information, the federal Privacy Act and FISMA requirements for federal agencies, and state privacy laws such as California's. Projects that collect or move personal information may need a privacy impact assessment or security authorization, which becomes a product to plan and quality-check.

Tailoring: bringing it together

Tailoring is the seventh principle, but it is also the thread that connects the people and context elements to the rest of the method. To tailor well, you look at the context and the people involved and then adapt the practices, processes, roles, management products and terminology, while keeping all seven principles. The manual encourages tailoring at the level of the organization, for example through a standard approach for all projects of a certain type, and at the level of each project, recorded in the PID.

Tailoring is where experience shows. A new practitioner tends either to apply everything in the manual, burying a small project in paperwork, or to drop parts of the method without thinking about which principle they support. A skilled practitioner asks what level of control this project needs, given its context and people, and adjusts accordingly.

Common tailoring mistakes

Three patterns cause trouble. The first is "PRINCE2 in name only", where an organization claims to use the method but has no real business case reviews, no board decisions at stage boundaries and no tolerances. The second is excessive bureaucracy, where every template is filled in regardless of value. The third is inconsistent tailoring, where decisions are made silently and different people have different ideas about how the project is being run. Recording tailoring decisions in the PID and reviewing them at stage boundaries addresses all three.

Leadership styles across the project

PRINCE2 7 recognizes that each management level needs a different kind of leadership. The project board provides direction and sponsorship: it sets the vision, makes timely decisions, secures resources and champions the change in the wider organization. The project manager leads day to day: building a team, creating clarity about priorities, resolving conflict, keeping stakeholders informed and protecting the team from unnecessary disruption. Team managers lead specialists, often with a strong focus on coaching, problem-solving and quality. Good leaders at every level adapt their style to the situation, being more directive in a crisis and more facilitative when the team has the expertise to solve a problem itself.

Culture interacts with leadership. In an organization where bad news is punished, forecasts drift optimistic and exceptions arrive late, undermining manage by exception. In a culture of openness, people raise risks and issues early, and tolerances work as intended. Project managers cannot change an organization's culture alone, but they can shape the culture of their own project by rewarding early warnings, running honest lessons sessions and modeling the behavior they want.

Communication and stakeholder engagement

Communication in PRINCE2 7 is planned through a communication management approach developed during initiation. It identifies stakeholders, their interests and influence, the information each needs, the frequency and channel of communication and who is responsible. Effective project communication is two-way: it listens as well as broadcasts, and it adapts the message to the audience. Senior executives may need a one-page dashboard, end users may need demonstrations and training, and suppliers may need detailed technical updates. The approach should be reviewed at each stage boundary, because stakeholders, their concerns and the project itself change over time.

Taken together, people, context and tailoring are what make PRINCE2 7 feel less like a rulebook and more like a way of thinking. The principles provide stable anchors; the practices and processes provide structure; and an understanding of the people and the environment tells you how much of that structure each project actually needs. Practitioner questions that ask whether a tailoring choice is appropriate are really testing whether you can hold all three in mind at once.

When you review a tailoring decision, ask which principle it supports, which people it affects and whether the context still justifies it; if you cannot answer, the decision probably needs revisiting.