PRINCE2 and the Structured Governance Approach

PRINCE2 examined: its origins in the UK public sector, its seven principles and seven practices, how it differs from PMBOK, and where its structured governance approach succeeds and faces limitations.

By Kateule Sydney — Researcher and Writer | Last Verified: 2026-10-03 | Published by Kat-Syd Resources Hub

PRINCE2 and structured project governance: principles, practices, and management by exception

Table of Contents

• Chapter 1 — PRINCE2 Is a Method, Not a Body of Knowledge
• Chapter 2 — Seven Principles and Seven Practices Hold the Method Together
• Chapter 3 — PRINCE2 Governs by Exception, Not by Continuous Approval
• Chapter 4 — The Method Assumes Tailoring
• Case Study
• Conclusion
• References

Chapter 1 — PRINCE2 Is a Method, Not a Body of Knowledge

The first thing to understand about PRINCE2 is that it is not the same type of publication as the PMBOK Guide. PRINCE2 is a project management method: it provides a structured approach for directing, managing, and controlling a project. The PMBOK Guide, by contrast, is PMI’s global standard and body of knowledge for project management. The two therefore serve different purposes, although both provide guidance on how projects can be managed effectively.

Definition. PRINCE2 stands for Projects IN Controlled Environments. The method originated in the UK government, evolving from earlier project-management work used for government information-systems projects. PRINCE was developed by the Central Computer and Telecommunications Agency in 1989, and PRINCE2 was released in 1996 as a generic project management method rather than one limited to IT projects. The current version is PRINCE2 Project Management Version 7, released in 2023. PeopleCert, which became the custodian of PRINCE2 following its acquisition of AXELOS, currently presents the method as a globally applicable project management method used across sectors and countries. PeopleCert now states that PRINCE2 is trusted by professionals in more than 200 countries.

PRINCE2 defines a governance and management structure for a project, including roles, responsibilities, management practices, processes, controls, and management products. The distinction from PMBOK matters because the two publications answer different kinds of questions. The PMBOK Guide provides a broad framework and standard for project management, including principles and performance domains. PRINCE2 provides a structured method for applying project management through defined principles, practices, processes, roles, and controls.

The distinction is therefore better described as method versus standard or body of knowledge, rather than simply prescriptive versus descriptive. PMI’s Eighth Edition also includes process guidance, although PMI describes that guidance as non-prescriptive. That distinction is one I explored in my post on the PMBOK Guide.

The method rests on four foundational ideas:

• A project is a temporary organization — PRINCE2 treats the project as a temporary organizational structure created to deliver agreed outputs or products within an agreed business justification
• Just-enough governance — PRINCE2 provides management controls and decision points intended to give the appropriate level of management information and authority
• Management by exception — senior decision-makers establish tolerances, allowing the project manager to manage within agreed limits and escalate when those limits are forecast to be exceeded
• Tailoring — PRINCE2 7 explicitly emphasizes adapting the method to the project’s circumstances rather than applying a single rigid implementation to every project

Why this matters. A reader who understands PRINCE2 as a method is more likely to use its governance structure deliberately and tailor its practices, processes, controls, and management products to the project’s circumstances. A reader who treats PRINCE2 primarily as a collection of documents may focus on producing paperwork instead of using the method to establish accountability, decision rights, controls, and escalation mechanisms.

The central argument of this chapter is that PRINCE2’s contribution lies principally in its structured management and governance approach, rather than in the mere production of documents.

Chapter 2 — Seven Principles and Seven Practices Hold the Method Together

A major terminology change is necessary. The 2017 edition of PRINCE2 used seven themes. PRINCE2 7 uses seven practices. The current method therefore does not describe Business Case, Organization, Quality, Plans, Risk, Change, and Progress as the seven themes. PRINCE2 7 is structured around seven principles, seven practices, and seven processes. The principles guide decisions and behaviour; the practices describe recurring aspects of project management that need continuing attention; and the processes provide the step-by-step management flow from starting to closing a project.

Definition. The seven PRINCE2 principles are the commitments the method requires of a project that is genuinely using PRINCE2. The seven practices are the recurring areas of management attention the project must address throughout its life. The seven processes are the management activities that move the project from one stage to the next.

The seven principles are:

• Ensure continued business justification — the project should remain justified as a worthwhile investment throughout its life
• Learn from experience — lessons should be identified, recorded, and applied
• Define roles, responsibilities, and relationships — project governance requires clear accountability and authority
• Manage by stages — the project is divided into manageable stages, with control and decision points between them
• Manage by exception — authority is delegated within agreed tolerances, with escalation when those tolerances are forecast to be exceeded
• Focus on products — the project is planned and controlled around the products and outcomes it is intended to deliver
• Tailor to suit the project — the method is adapted to the project’s context rather than applied mechanically

The seven practices are:

• Business Case — the continuing justification for undertaking the project
• Organizing — the project’s roles, responsibilities, relationships, and organizational structure
• Plans — the planning approach and the plans used to manage delivery
• Quality — the approach to defining, controlling, and assuring the required quality of products
• Risk — the approach to identifying, assessing, and managing uncertainty
• Issues — the approach to identifying, assessing, and managing issues, including changes and other matters requiring management attention
• Progress — the approach to monitoring progress, forecasting performance, and escalating when necessary

Key point. This change matters because describing the current method using the old seven themes makes an otherwise technically strong article look outdated. PRINCE2 7 also gives greater prominence to people management, communication, digital and data management, and sustainability. PeopleCert describes people management as a new integrated element of the seventh edition and highlights sustainability as part of project performance.

The principles, practices, and processes should not be reduced to a documentation checklist. They provide the structure through which PRINCE2 is applied. A project can produce numerous management documents without necessarily demonstrating effective governance. Conversely, tailoring may mean that the form and amount of documentation differ between projects. The important distinction is between using the method’s management controls and merely reproducing its terminology or templates.

The central argument of this chapter is that the principles define the fundamental commitments of the method, while the practices provide recurring areas of management attention and the processes provide the management flow.

Chapter 3 — PRINCE2 Governs by Exception, Not by Continuous Approval

One of PRINCE2’s distinctive governance mechanisms is management by exception. The project board does not need to approve every operational decision. Instead, authority is delegated within agreed tolerances, and escalation occurs when a forecast indicates that those tolerances may be exceeded.

Definition. Managing by exception means that the appropriate level of management establishes boundaries within which delegated authority can operate. The project manager can manage the project within those agreed tolerances and escalates when a forecast indicates that one or more tolerances will be exceeded or when a decision falls outside the delegated authority. This mechanism is intended to prevent senior management from becoming involved in routine operational decisions while retaining control over significant deviations.

The governance model includes three principal project-board roles:

• Executive — accountable for the project’s success and for ensuring that the project remains aligned with the organization’s interests
• Senior user — represents the interests of those who will use the project’s products and focuses on whether the products will deliver the required benefits
• Senior supplier — represents the interests of those responsible for supplying the project’s specialist products or resources

The project manager is responsible for day-to-day project management within the authority delegated to that role. Stage boundaries provide formal points at which the project board can review progress, assess the continuing business justification, and authorize the next stage. This creates a distinction between routine management within a stage and governance decisions at defined control points.

The exception sequence is:

• The forecast — the project manager forecasts that a tolerance will be exceeded
• The escalation — the project manager escalates the situation in accordance with the method
• The report — an exception report can be used to describe the problem, its implications, available options, and the recommended response
• The decision — the project board considers the exception and decides how the project should proceed
• The return — the project returns to controlled operation under the revised or confirmed authority, or the project may be redirected or closed

Why this matters. Management by exception is intended to make governance more efficient by separating strategic oversight from routine operational management. Senior management can concentrate on significant decisions rather than approving every task. However, the effectiveness of the mechanism depends on the quality of the tolerances, forecasting, reporting, and escalation. A project cannot be effectively managed by exception if its tolerances are vague or if significant deviations are not escalated.

The central argument of this chapter is that management by exception is important to PRINCE2’s governance model, but its effectiveness depends on implementation rather than on the existence of the rule alone.

Chapter 4 — The Method Assumes Tailoring

PRINCE2’s seventh principle is tailor to suit the project. The current method explicitly emphasizes flexibility and customization rather than requiring every project to use the same level of documentation or the same management arrangements.

Definition. Tailoring means adapting the application of PRINCE2 to the project’s size, complexity, organizational environment, risk, delivery approach, and other relevant circumstances. PRINCE2 7 is explicitly designed to accommodate different delivery approaches, including predictive, incremental, agile, and hybrid approaches. PeopleCert describes the method as flexible to incorporate different delivery methods within its governance framework.

The important issue is therefore not whether every project uses exactly the same documents. It is whether the project has established an appropriate level of governance, accountability, control, and information.

Three common tailoring problems occur in practice:

• Insufficient tailoring — an organization may apply the same procedures and documentation to projects with very different levels of risk and complexity
• Undocumented tailoring — an organization may make important changes to how the method is applied without clearly recording the resulting governance arrangements
• Poorly justified tailoring — an organization may remove controls simply because they are inconvenient rather than because they are unnecessary or inappropriate for the project’s context

Key point. The first and third problems can create either unnecessary bureaucracy or inadequate governance. It is therefore more accurate to say that poor tailoring can create the bureaucratic experience sometimes associated with PRINCE2, rather than claiming that PRINCE2’s bureaucratic reputation is entirely caused by poor tailoring. The same tension between standardization and fit appears in my post on the project life cycle, where the choice of phase structure and gate criteria has to be matched to the project’s context.

Why this matters. Tailoring is what allows PRINCE2 to be applied to projects of different sizes and contexts. But tailoring does not mean removing governance indiscriminately. It means determining what level of governance and control is appropriate.

The central argument of this chapter is that PRINCE2’s flexibility depends on the quality of the tailoring decisions made by the organization and project team.

Case Study

The UK government provides an important historical context for PRINCE2 because the method originated within the UK public sector. PRINCE was developed by the Central Computer and Telecommunications Agency for government IT projects before PRINCE2 was developed as a generic project management method in 1996.

The National Programme for IT in the NHS, launched in 2002, provides a useful case for examining project and programme governance in a large public-sector environment. The programme encountered substantial difficulties. The House of Commons Public Accounts Committee reported delays in developing and deploying detailed care-record systems and stated that the government decided in September 2011 to dismantle the National Programme while retaining its component programmes under separate management and accountability arrangements. The Committee also reported a forecast cost of £9.8 billion, while noting that this figure did not include certain future costs. The Committee reported estimated benefits of £3.7 billion to March 2012 and noted that this represented approximately half of the costs incurred by that point.

These findings demonstrate significant governance and delivery problems, but they do not by themselves establish that PRINCE2 caused or failed to prevent those problems. It is therefore too strong to state that the programme was a failure because PRINCE2’s principles were not enforced. The available Public Accounts Committee evidence supports conclusions about problems with costs, delivery, complexity, contracts, oversight, and benefits realization; it does not provide sufficient evidence to attribute those problems specifically to non-compliance with particular PRINCE2 principles.

A more defensible interpretation is that the case illustrates an important limitation of structured project-management methods: having a governance framework does not guarantee effective governance. Organizational capability, decision-making, contracting, stakeholder management, programme complexity, leadership, and the quality of information available to decision-makers can all affect outcomes. This distinction is important. A method can define escalation mechanisms and business-justification controls without guaranteeing that an organization will use them effectively. That distinction is also central to my post on why large projects fail, where governance weakness is one of four interacting mechanisms rather than a single cause.

The NHS case therefore supports a more cautious conclusion: PRINCE2 can provide a governance structure, but the existence of the structure is not sufficient to ensure successful governance.

Conclusion

PRINCE2 is a structured project management method rather than a body of knowledge. Its contribution lies in the way it organizes project governance and management through defined principles, practices, processes, roles, responsibilities, tolerances, stages, and controls. PeopleCert’s current PRINCE2 7 framework also places greater emphasis on people, communication, digital and data management, and sustainability.

The seven principles provide the fundamental commitments of the method. The seven practices identify recurring aspects of project management that require continuing attention, while the seven processes provide the management flow through the project lifecycle. Management by exception is an important feature of the governance model because it allows authority to be delegated within agreed tolerances. Stage boundaries provide additional opportunities for senior management to review progress and continuing justification. Tailoring is equally important: PRINCE2 7 is explicitly designed to be adapted to different projects and delivery environments rather than applied as an inflexible template.

My position is that the strongest criticism of PRINCE2 is not necessarily that the method requires excessive documentation. A more precise criticism is that organizations can implement structured methods bureaucratically, particularly when they treat templates and procedures as ends in themselves rather than as tools for governance and decision-making. At the same time, it would be equally misleading to dismiss all criticism of PRINCE2 as a tailoring failure. Documentation, governance overhead, role complexity, and the suitability of a method for a particular organizational environment are legitimate issues that should be evaluated against the project’s context.

The strongest counterargument to my position is that PRINCE2’s document load and governance overhead still make the method impractical for small or fast-moving projects, and that firms are right to prefer lighter methods. I take that objection seriously, and the tailoring principle is the method’s own answer to it. PRINCE2 does not require the same document set on every project. It requires the project manager and project board to decide what the project actually needs. The criticism is valid when firms skip tailoring. It is not valid against the method itself.

My recommendations follow from that analysis:

• Treat PRINCE2 as a governance and project-management method, not merely a document framework — the management products are tools and evidence supporting the method; they are not the method itself
• Set meaningful tolerances and enforce escalation — management by exception depends on clear boundaries and reliable forecasting
• Tailor the method deliberately — the seventh principle is intended to ensure that the method is appropriate to the project’s context rather than mechanically standardized
• Reconfirm the business justification throughout the project — continued business justification is intended to prevent a project from continuing without sufficient reason to remain a worthwhile investment
• Use the current PRINCE2 7 terminology — in particular, distinguish the seven practices from the seven themes used in the 2017 edition
• Do not confuse PRINCE2 with PMBOK — they are different kinds of project-management resources, although they overlap in subject matter and can be used together

The final argument of this post is that PRINCE2 provides a structured approach to project governance and management, but the value of that structure depends on how appropriately and effectively an organization applies, tailors, and enforces it.

References

• AXELOS. (2017). Managing Successful Projects with PRINCE2, 6th Edition — The Stationery Office
• PeopleCert. (2023). PRINCE2 Project Management: Version 7 — PeopleCert
• PeopleCert. (2023). PRINCE2 7: A Process of Evolution — PeopleCert
• PeopleCert. PRINCE2 Project Management Foundation (Version 7) — PeopleCert
• Public Accounts Committee. (2013). The Dismantled National Programme for IT in the NHS — UK Parliament
• Project Management Institute. (2025). A Guide to the Project Management Body of Knowledge (PMBOK Guide), Eighth Edition — PMI

Read Also on Kat-Syd Resources Hub

PMBOK Guide: Origins, Structure & Limits — The PMI standard, the Eighth Edition’s principles and performance domains, and the criticisms of rigidity.

Project Life Cycle: Phases, Gates, and Transitions — Phases, the PMI Process Groups, phase-gate decision models, and how predictive, adaptive, and hybrid structures distribute project risk.

Why Large Projects Fail: The Structural Causes — Optimism bias, strategic misrepresentation, governance weakness, and complexity, tested against megaproject research and documented cases.

Written by Kateule Sydney — Researcher and Writer

© 2026 Kat-Syd Resources Hub. All rights reserved.

Kat-Syd Resources Hub — Educational case studies and analytical reference