The Enterprise Change Office

Main Menu
Knowledge Base

This website provides three ways to explore its underlying body of knowledge: follow the structured framework, read articles that examine and challenge particular ideas, or search across the complete Knowledge Base.

Explore The Framework

Follow the structured concepts, models and principles that underpin this approach to organisational change, from fundamental definitions through to enterprise change capability and the Enterprise Change Office.

Read The Articles

Explore longer-form arguments, critiques and applications that examine established thinking, challenge assumptions and consider particular issues in organisational change.

Search The Knowledge Base

Search and filter across framework topics and articles when you have a particular question, concept or area of organisational change that you want to investigate.
error: Content is protected !!

Ecosystem

The Office of Government Commerce And P3O®

The Office of Government Commerce (OGC) was a UK government body established in 2000 to promote efficiency and best practices in public sector procurement, project management, and programme management. One of its significant contributions was the development of the P3O® (Portfolio, Programme, and Project Offices) framework, first published in 2008. This framework provides principles and guidance on designing and operating effective support structures for delivering change. P3O® was created in response to the growing need for organisations to align their strategies with execution and to standardise the roles of PMOs across different contexts.

In 2014, the stewardship of the OGC’s best practice portfolio was transferred to AXELOS, a joint venture between the UK Cabinet Office and Capita. AXELOS continues to maintain and publish the official P3O® guidance, with the most recent version being “Portfolio, Programme and Project Offices: P3O® Guidance” (AXELOS, 2013).

The guidance outlines a hierarchy of structures, which is summarised in Exhibit 1. It also notes that “projects” can stand alone and do not need to be part of a “programme”.

Exhibit 1: P30® Hierarchy