For years, the Project Management Body of Knowledge (PMBOK) Guide taught a generation of practitioners to think in processes: five process groups, ten knowledge areas, and the inputs, tools, and outputs that connected them. This year, the Project Management Institute (PMI) published the 7th edition of A Guide to the Project Management Body of Knowledge, and it takes a different shape. It’s built on principles and performance domains, not on processes.

What changed

The 7th edition describes 12 principles that guide behavior on a project, and eight performance domains: groups of related activities that matter for delivering results. It doesn’t tell you which process to run next. It asks you to understand the intent and to tailor your approach to the situation. It also gives more weight to delivering value than to following a prescribed sequence, and it recognizes predictive, adaptive, and hybrid ways of working as equally legitimate.

This isn’t a rejection of the past. The earlier material on scope, schedule, cost, and risk remains useful. The difference is that the guide no longer presents it as a single method you apply in every case.

What it means for practitioners

If you hold a PMI credential or manage projects for a living, expect the conversation to shift from “did we follow the process?” to “did we choose a sensible approach, and did it deliver value?” That asks more of your judgment. You’ll need to explain why you chose a lifecycle, how you’ll govern it, and what you’ll measure. Those are good questions to answer anyway.

What it means for PMOs

Many organizations built their project management method around the older process model: templates for every process, stage gates that mirror the knowledge areas, and audits that check whether every document exists. That structure may still serve you well for some work, but treat it as a starting point, not a rulebook.

Consider a regional bank whose method requires the same 20 documents for every project. A small internal improvement and a major core system change get identical paperwork. A principles-based view would ask what each project needs, and drop the rest. Here, the project management office (PMO) can lead by defining a small set of mandatory outcomes and a menu of optional practices, then helping teams choose.

We’d suggest three steps:

1. Read the new edition with your PMO and senior project managers, and note where your method matches its intent.
2. Mark the parts of your method that exist out of habit.
3. Pilot a lighter, tailored approach on two or three projects and compare results.

Principles don’t make decisions for you, and that is the point. If you want help adapting your method, we can work through it with you.