A principle is a statement of what a decision should serve, written so that it holds whether the work is a bridge or a mobile application. The eighth edition of the PMBOK Guide carries six of them, and together they form the standard for project management, with the guide sitting beneath the standard as the description of how the work is organised. That distinction matters on the examination. A scenario question rarely carries a rule that settles it, and almost always carries a principle that does.
These six replaced the twelve that the seventh edition introduced in 2021. Overlap was removed and content was kept, so a candidate who learned the twelve will recognise most of what follows under new headings. The sections below set out the six, explain how twelve became six, separate a principle from a rule and describe how the principles are used to read a scenario.
The six principles
| Principle | What it asks | What it looks like when it is missing |
|---|---|---|
| Adopt a holistic view | See the project inside the system that funds it, staffs it and receives its output, including the parts the project does not control | A project delivered exactly as specified into an organisation that has moved on, or a dependency nobody owned because it sat between two teams |
| Focus on value | Judge the work by the benefit it produces, and only then by the deliverables it completes | A green status report on a project whose business case expired two quarters ago |
| Embed quality | Build quality into the process and the deliverable from the start, so that inspection at the end confirms it | A test phase discovering design faults, at the point in the schedule where fixing them costs the most |
| Lead accountably | Own the outcome, make the ownership visible and hold others to the same standard, with no retreat into process | An escalation log that records who was told and never who decided |
| Integrate sustainability | Weigh environmental, social and economic effects over the life of what is being built, well beyond the length of the project | A solution that meets every acceptance criterion and costs more to operate than it saves |
| Build empowered teams | Give the people doing the work the authority and the context to make decisions about it | A team that raises everything, because raising everything is the only safe behaviour when nothing has been delegated |
Two of the six are new emphases. Integrating sustainability arrived as a principle in its own right, and building empowered teams turns into a standing expectation what earlier editions had treated as a leadership style.
Why twelve became six
The other four are consolidations, because genuine overlap ran through the twelve. Stewardship, systems thinking and navigating complexity all asked the reader to look beyond the boundary of the project, and they now sit together under a holistic view. Quality and value each appeared in several places and were consolidated into one.
Tailoring is the interesting case. It was a principle in the seventh edition and it is missing from the six, which reads at first as a demotion. What actually happened is that tailoring moved from being one instruction among twelve to being the way all of them are applied. A principle that holds for every project can only be followed by adapting it to the one in front of the reader.
How a principle differs from a rule
Tailoring is needed because a principle sets a direction and settles nothing on its own. Principles feel slippery in study for that reason. Two project managers may apply focus on value to the same scenario and then act differently, because one of them has a sponsor who will cancel a project and the other does not.
What a principle does is state which considerations belong in the decision. Faced with a change request that adds scope and delay, focus on value asks whether the change moves the benefit, embed quality asks what the compression will do to defect rates and lead accountably asks who is entitled to make the call and whether that person holds what they need to make it. Which answer follows still depends on the project. Which considerations belong on the shortlist does not.
Reading an examination scenario through the principles
The shortlist is what the examination is testing. Scenario questions are usually built so that several options describe defensible activities and one describes the right next move, and the principles are how that distinction is drawn.
Gathering information before acting usually beats acting immediately, because a holistic view asks what else is affected. Taking the decision to the team that owns the work usually beats deciding for the team, because empowered teams is a standing expectation. Protecting the benefit usually beats protecting the schedule, because value is the thing being managed and the schedule is a constraint upon producing it.
Where two options both appear principled, accountability breaks the tie. Escalating without a recommendation, or informing someone where a decision was needed, fails the fourth principle even where it looks diligent.
What the principles do not do
The principles do not authorise ignoring a governance requirement. A principle sits above the method and below the organisation's obligations, so a regulated approval that has to happen still has to happen. The principle shapes how that approval is prepared. Whether it is met is settled elsewhere.
They also carry no order of precedence. None of the six outranks another, and a question that sets two of them against each other is testing whether the candidate can find the option serving both. Such an option usually exists, and it is usually the one that involves talking to someone before deciding.