The 6 Principles and 7 Domains of PMBOK 8, Explained with Examples

Before memorizing a list, it helps to understand the idea that holds it together. PMBOK 8 separates two things that are easy to confuse. On one side is how you think, which are the principles. On the other is where you apply it, which are the domains. The cook’s attitude is one thing, the kitchen stations where that attitude shows up are another. With that picture in your head, everything else falls into place.

The 6 Principles (the Mindset)

The principles guide how you behave. They are not rules you either comply with or break, they are underlying standards. PMBOK 8 consolidated the 12 from version 7 into 6, merging some and moving others to different sections, so they are easier to put into practice. Here they are.

• Adopt a holistic view. Look at the whole project and its connections, not the isolated task. If your team is about to rush a delivery, you ask yourself what happens downstream before stepping on the gas.
• Focus on value. Success is not delivering the software, it is the customer working better with it. If you deliver the system but no one uses it, you did not deliver value, you delivered a file.
• Build quality into processes and deliverables. Quality is not inspected at the end, it is built from the start. It is reviewing the blueprint before raising the wall, not after the wall is crooked.
• Be a responsible leader. Take ownership. When two vendors clash over scheduling, you do not hide behind the contract, you sit down to find the real cause of the problem.
• Integrate sustainability across all areas of the project. Think about people, the environment, and the long term, not just closing out the month. This principle is new compared to the version 7 list, and it says a lot about where PMI is looking.
• Build an empowered culture. A team that decides, makes mistakes, and learns is worth more than one that waits for orders. Your job is to clear stones from the path, not to watch every step.

These 6 principles also group into three dimensions of the mindset. The proactive dimension, which gets ahead of things. The ownership dimension, which takes responsibility. And the value-oriented dimension, which never loses sight of why the project exists.

The 7 Performance Domains (the Mechanics)

The domains are the broad areas where the work actually happens. This is where mindset turns into action. PMBOK 8 defines seven.

• Governance. How decisions are made and who answers for them. It is the project’s nervous system, what used to be spread out under the name of integration.
• Scope. What the project includes and what it does not, with quality built into it. This is where you fight the classic “while we’re at it, let’s add this.”
• Schedule. Time. Sequences, dependencies, dates that are realistic and not wishes dressed up as a plan.
• Finance. Money, viewed more broadly than cost alone. Budget, return, viability. We will talk separately about why it stopped being called Cost.
• Stakeholders. The people with something at stake. A good part of communication now lives here too, which used to have its own area.
• Resources. The team and the physical assets. Who does what, with what tools, without burning people out.
• Risk. Uncertainty. Threats you dodge and opportunities you seize, because not every risk is bad.

How Principles and Domains Fit Together

The point is that they cross over. Each principle shows up in several domains. The holistic view, for example, touches them all, because looking at the whole serves governance just as well as the schedule. Focusing on value presses hardest on governance, scope, finance, and risk, where you decide what to spend the effort on.

Do not study them as two separate lists. Study them as a weave. The principle is the thread, the domain is the cloth. When you understand which thread runs through which cloth, you stop memorizing and start understanding.

And understanding, in the end, is the only thing that stays standing on exam day.

Join the waitlist

If you want to see how these same principles played out in PMBOK 7, or how they translated into concrete processes in PMBOK 6, join the waitlist for our two free guides. They will give you context that PMBOK 8 takes for granted. The premium PMBOK 8 guide is in preparation. (Soon.)