The 7 PRINCE2 Principles, Explained
Seven principles hold PRINCE2 together — miss one and it isn't really PRINCE2. Here's what each means on a real project.
PRINCE2 has a lot of moving parts — themes, processes, management products — but underneath all of it sit seven principles. They’re the non-negotiable bit: the method itself says that if a project doesn’t apply all seven, it isn’t genuinely being run with PRINCE2. Here’s what each one means once you’re off the page and on a real project.
1. Continued business justification
Every PRINCE2 project has to make sense — not just at kick-off, but the whole way through. If the reason for doing it stops stacking up, you stop the project. That sounds obvious, but plenty of projects limp on long after the business case has fallen apart. PRINCE2 forces you to keep asking “is this still worth it?” and gives you permission to pull the plug.
2. Learn from experience
Teams are expected to actively look for lessons — from past projects at the start, from this one as it runs, and to pass lessons on at the end. It’s a deliberate antidote to the habit of repeating the same mistakes on every project.
3. Defined roles and responsibilities
Everyone needs to know who decides what. PRINCE2 sets up a clear structure covering the three interests every project has: the business (is it worth it?), the users (will it do the job?) and the suppliers (can we build it?). When roles are vague, decisions stall — this principle stops that.
4. Manage by stages
Rather than plan the whole thing in fine detail on day one, PRINCE2 breaks the project into management stages — planning the next one in detail and the rest at a high level. At the end of each stage the project board decides whether to carry on. It keeps big projects controllable and gives natural go/no-go points.
5. Manage by exception
Senior managers set tolerances — how far a stage can drift on time, cost, scope and so on — then leave the project manager to get on with it, escalating only when something threatens to break those limits. It saves everyone from endless status meetings and reserves senior attention for decisions that actually need it.
6. Focus on products
PRINCE2 stays relentlessly focused on what the project will deliver — described and agreed up front — rather than just the activities. Define the products and their quality criteria clearly, and the work needed to build them (and how you’ll know they’re good enough) falls into place.
7. Tailor to suit the project
PRINCE2 is meant to be scaled to fit — a small internal project shouldn’t carry the same paperwork as a multi-year programme. This principle is what stops PRINCE2 becoming box-ticking: you apply as much, or as little, of the method as the project’s size, risk and complexity warrant.
Why the principles matter
The themes and processes are the “how,” but the principles are the “why” — and they’re what examiners and employers expect you to genuinely understand, not just recite. Get the principles, and the rest of PRINCE2 stops feeling like jargon and starts making sense. For the wider view, see PRINCE2’s advantages and disadvantages and whether PRINCE2 is worth it.
Learn the full method
If you want to apply this properly — and earn the certification employers recognise — our PRINCE2 courses cover Foundation and Practitioner, online and self-paced, with the principles, themes and processes worked through in full.