“PRINCE2 Explained: Principles, Themes and Processes”

What is PRINCE2 in plain terms?

PRINCE2 is a structured, tailorable method for managing projects, organised around seven principles, seven themes or practices, and seven processes that run from pre-project setup to closure. It assumes a project is a temporary organisation created to deliver a defined product, with a business case that must stay valid for the project to continue.

The name stands for Projects IN Controlled Environments. The method was first published in 1996, and the seventh edition arrived in September 2023 under PeopleCert, which acquired AXELOS in 2021. PeopleCert describes it as held by more than a million certified professionals across 150-plus countries, and it remains the de facto standard in UK public sector delivery.

What separates PRINCE2 from a generic checklist is the division of accountability. A Project Board of three role types — Executive, Senior User and Senior Supplier — owns the project. A Project Manager runs it day to day inside limits the board sets. That is the whole idea: delegated authority with pre-agreed boundaries.

What are the seven PRINCE2 principles?

The seven principles are the non-negotiable rules of the method. If a project breaks one of them, it is not being run as PRINCE2, no matter how many templates it fills in.

Two of these principles were renamed in the seventh edition to make the human side of delivery explicit: “continued business justification” became “ensure continued business justification”, and “defined roles and responsibilities” became “define roles, responsibilities, and relationships”. The words are small. The intent is not.

> Important note: “Focus on products” is the principle most often skipped and the one that saves the most rework. If a plan lists activities but never defines what “done” looks like, the quality review at the end becomes an argument about opinion rather than evidence.

What are the seven PRINCE2 themes, and why are they called practices now?

The seven themes are the aspects of project management that must be addressed continuously throughout the project. In the 2023 edition they were renamed practices, a change that signals they are things you do, not topics you document once and archive.

The seventh edition added a seventh performance target, sustainability, alongside the traditional six of benefits, costs, timescales, quality, scope and risk. It also added three management approaches to the project initiation documentation: commercial, data, and sustainability. For a project manager, that means the sustainability line in a highlight report is now a legitimate place to record a decision, not a paragraph of decoration.

What are the seven PRINCE2 processes?

The seven processes form the lifecycle. They are not phases in the way a waterfall plan uses that word; several run in parallel, and the board’s directing process runs throughout.

The seventh edition kept these seven but rewrote the chapters. Each process now carries a RACI table mapping activities against the key roles, and each chapter ends by naming which practices apply inside that process. That sounds like publishing detail. In practice it is the most useful change for a new practitioner, because it shows how the method’s parts connect instead of presenting them as seven isolated chapters.

How do tolerances work in practice?

Tolerances are the numbers that make delegated authority real. The board sets limits for time, cost, scope, quality, benefits and risk; the project manager works freely inside them and escalates when a forecast breaches one.

Here is the arithmetic on a project with a £1,200,000 budget spread evenly over six stages of £200,000 each:

The stage forecast exceeds the £10,000 stage tolerance by £4,000, so the project manager raises an exception report rather than quietly absorbing it. Because the overspend sits well inside the project-level ±£120,000, the board can decide to continue with a corrective action instead of escalating to the programme. That is the method working as designed: a small problem surfaces early, at the level that can actually fix it.

> Common mistake: Setting tolerances so wide that nothing ever escalates, then complaining that the board is disengaged. A tolerance the project never tests is not a control, it is a formality.

How does continued business justification work with real numbers?

The business case is the only part of PRINCE2 that can stop a project outright. Its job is to keep the question “should we still do this?” alive.

Take a compliance platform with forecast benefits of £2,400,000 over four years and a delivery cost of £1,500,000. The benefit-to-cost ratio is 2,400,000 ÷ 1,500,000 = 1.60. The board approves it.

At the second stage boundary, a regulatory change adds £420,000 of work. The ratio becomes 2,400,000 ÷ 1,920,000 = 1.25. Still above the organisation’s 1.2 threshold, so the project continues, with the payback date moving out by roughly seven months.

At the fourth boundary, a further £300,000 of scope is requested. The ratio drops to 2,400,000 ÷ 2,220,000 = 1.08, below the threshold. The board now has a defensible choice: cut scope to restore the ratio, or close the project and accept partial benefit. Either decision is documented, which is the point.

Should you tailor PRINCE2 down for a small project?

Yes, and the method explicitly expects it. PRINCE2 7 removed the concept of universal minimum requirements; what remains is the principles plus agreed tolerances. Tailoring is not a shortcut, it is part of the method.

A twelve-week website rebuild does not need the full management product set. Assume each document takes about six hours of project manager time to draft, review and maintain:

The tailored set might be a combined project brief and initiation document, a single stage plan, product descriptions for the four main deliverables, a highlight report, and a lessons log. The governance still exists. The ceremony does not.

PRINCE2 vs PMP: which one do you actually need?

They answer different questions, which is why comparing them directly produces bad advice. PRINCE2 is a method that tells an organisation how to run a project; PMP is a certification that tells an employer what a practitioner knows.

Many organisations use both: PRINCE2 supplies the governance wrapper, while the delivery team runs Scrum or Kanban inside it. That combination is legitimate and common. What is not legitimate is claiming PRINCE2 certification proves you can lead delivery — it proves you understand the method.

Where PRINCE2 helps and where it hurts

The honest trade-off is between control and speed.

It helps when accountability must be demonstrable. Regulated industries, public procurement, supplier consortia and audit-heavy programmes benefit from named roles, written authorisations and stage gates that create a paper trail by design.

It hurts when the work is genuinely exploratory. If the product direction changes every three weeks, a stage plan built on a stable product breakdown will be obsolete before it is signed. PRINCE2 7 handles this better than earlier editions by treating tailoring as central, but the underlying assumption of a defined product remains.

The cost is real. Stage boundaries consume management time, and boards that meet monthly can add two to three weeks of latency to a decision. On a twenty-four-month infrastructure programme that is noise. On an eight-week campaign it is fatal.

What are the most common PRINCE2 mistakes?

• Producing documents nobody reads. A business case written once at initiation and never revisited is a filing exercise, not a control.
• Confusing roles with job titles. The Executive is accountable for the business case even if they are not the most senior person in the room.
• Skipping the product description. Without defined acceptance criteria, quality review becomes a negotiation.
• Treating the stage boundary as a status meeting. It is a decision point with three real options: continue, change, or stop.
• Over-tailoring into nothing. Dropping the lessons log and the risk register removes the two artefacts that most often prevent repeat failures.
• Certifying the team and changing nothing. Training without a tailored method embedded in the tooling produces vocabulary, not governance.

How do you run PRINCE2 without drowning in documents?

Keep the governance artefacts in the same place as the work. The failure mode is rarely the method itself; it is the method living in a folder while delivery lives in three other tools. When the risk register, the stage plan and the actual task board are separate systems, every highlight report becomes a manual reconciliation.

That is the gap Doitify is built for: tasks, sub-tasks, owners, dependencies, milestones and progress reports in one workspace, with dashboards that show planned against actual without exporting spreadsheets. For a PRINCE2 project, that means the stage plan, the product checklist and the highlight report draw from the same data. Doitify is our product, so treat that as a statement of fit rather than an independent review — a twenty-person team running two stages at a time will get more from it than a large programme that already has an enterprise PPM suite.

If you want to see how progress control looks numerically, the guide to the cost performance index covers the earned-value side that PRINCE2’s progress practice expects you to report. The S-curve explainer shows how to read the cumulative view.

Conclusion

PRINCE2 is best understood as a decision architecture. The principles keep the project honest, the practices keep the important questions visible, and the processes create predictable moments where someone with authority decides whether to continue. Tolerances are what make that delegation real, and the business case is what makes stopping a legitimate outcome rather than a failure.

Use it where the cost of an unexplained decision is high. Tailor it hard, keep the artefacts close to the actual work, and resist the urge to measure compliance by document count. A project with five well-used management products and a board that escalates honestly is running PRINCE2 better than one with fourteen documents and no decisions.

If this post on PRINCE2 was helpful, you might also enjoy Synchronous vs Asynchronous Collaboration: Which Should Your Team Use? and How to Create an Executive Project Summary.