5.1 Project Organization Overview

What the Organizing Practice Covers

In PRINCE2 7th edition the theme historically called Organization is now one of the seven practices and is called Organizing. The practice answers a single governance question: who is accountable, who decides, who manages, and who delivers? PRINCE2 establishes a temporary project management team that draws people from one or more permanent organisations — often in a customer/supplier relationship — and gives each a clearly defined role.

A core idea you must internalise for the Foundation exam is that PRINCE2 defines roles, not jobs. A role is a set of responsibilities. One person may take several roles, and one role may be shared by several people — with two strict exceptions. The Executive and the Project Manager must each be a single, named individual, and these two roles must never be combined with each other. Almost everything else in the structure is flexible to fit the size and risk of the project.

The Four Levels of Organization

PRINCE2 separates direction from management and management from delivery using four levels. The top level sits outside the project; the lower three form the project management team.

The top level is not part of the project. It commissions the work, defines what success means, and sets the project tolerances within which the Board may operate. The three lower levels each manage by exception: each works within tolerances set by the level above and escalates only when those tolerances are forecast to be exceeded. This layered delegation is what links the Organizing practice directly to the principles manage by stages, manage by exception, and defined roles, responsibilities and relationships.

Directing, Managing, Delivering

The three project levels map cleanly onto activities you will recognise from the processes:

• Directing (Project Board): owns Directing a Project (DP). The Board does not manage day to day — it authorises initiation, authorises the project, authorises each stage or exception plan, gives ad hoc direction, and authorises closure.
• Managing (Project Manager): owns the Initiating, Controlling a Stage, and Managing a Stage Boundary processes. The Project Manager plans stages, assigns work, monitors progress, and reports upward.
• Delivering (Team Manager): owns Managing Product Delivery. The Team Manager accepts Work Packages, oversees their creation, and reports progress via checkpoint reports.

What the 7th Edition Added: People

PRINCE2 7 deliberately broadens Organizing beyond a role chart. It introduces an explicit people dimension — covering leadership, project culture, change management, and team wellbeing. The guidance reminds project managers to design the project ecosystem, onboard people, manage transitions and capability gaps, and lead the human change that the project's products will cause. Sustainability and longer-term social and environmental impacts also enter the Executive's governance remit.

For the Foundation exam, remember the four levels, the named roles, and the people emphasis; the deeper leadership techniques are tested more heavily at Practitioner level.

Why a Customer/Supplier Structure Matters

PRINCE2 assumes a customer/supplier environment: a customer who specifies what is wanted, pays for the project and uses the result, and a supplier who provides the skills and resources to build the products. This assumption shapes the whole organisation. The Senior User speaks for the customer's user community, the Senior Supplier speaks for the supplier community, and the Executive balances the two to protect the business interest.

Even on an internal project with no external vendor, PRINCE2 keeps these interests distinct, because users and builders naturally want different things — users want capability and ease of use, suppliers want feasibility and protected effort. Keeping them as separate voices on the Board surfaces those tensions early, where they are cheap to resolve.

This is also why the Organizing practice is the practical expression of the principle defined roles, responsibilities and relationships. PRINCE2 lists seven principles, and an effective organisation directly supports several of them: roles are defined and agreed up front; the project is managed by exception through tolerances delegated down the four levels; and the business justification is continuously owned by the Executive.

A project that cannot say, on day one, who its Executive is and which business interest each Board member represents has not yet satisfied PRINCE2's organisational requirements, regardless of how detailed its plans look.

The Organisation Is Established Early and Reviewed Often

The initial team is appointed during Starting up a Project (the Executive and Project Manager first), refined during Initiating a Project, and reviewed at every stage boundary. People may join, leave or change roles as the project moves through its stages, so the structure is living rather than fixed. Recording these appointments — including the agreed role descriptions — is part of the project's governance and is something an auditor or the Project Board can inspect at any time.