The performance domains and focus areas

If principles describe how to think, performance domains describe what to pay attention to. A performance domain is a group of related activities that are critical to delivering project outcomes. The PMBOK Guide 8th edition organizes its guidance into seven performance domains and reintroduces five focus areas that echo the familiar process groups, with 40 tailorable processes linking the two. This lesson gives an overview of that structure, explains how it differs from the 7th edition's eight domains and the 6th edition's ten knowledge areas, and shows how it relates to the three domains of the 2026 PMP exam content outline. Later courses in this series go deeper into each area.

Three structures you may meet

Project management guidance has been organized in several ways over the years, and you will meet all of them in books, workplaces and older practice questions. The 6th edition (2017) used five process groups and ten knowledge areas with 49 processes. The 7th edition (2021) replaced these with twelve principles and eight performance domains and moved processes out of the main guide. The 8th edition (November 2025) keeps a principles-and-domains structure but brings processes back in a flexible form, organized by focus areas. The exam is based on its own content outline rather than on any single edition, but PMI lists the PMBOK Guide among its references, so understanding the current structure is useful.

The seven performance domains

These names will look familiar to anyone who studied the older knowledge areas: scope, schedule, cost (now finance), stakeholders, resources and risk all appeared there. Governance is new as a domain and gathers ideas that were previously spread across integration management, change control and organizational context. Communication, quality and procurement are not separate domains in the 8th edition; they are addressed within the domains and processes, with procurement given expanded treatment as a topic of its own.

The five focus areas

The 8th edition brings back initiating, planning, executing, monitoring and controlling, and closing, calling them focus areas rather than process groups. The change in name signals a change in emphasis: they describe kinds of work that happen throughout a project, often repeatedly and in overlapping cycles, rather than strict phases that follow one another. An adaptive team, for example, plans, executes and reviews in every iteration.

• Initiating: establish purpose, vision and strategic alignment, and authorize the work.
• Planning: define the approach, scope, estimates, risks and governance arrangements.
• Executing: do the work, lead the team, engage stakeholders and manage resources.
• Monitoring and controlling: track performance, manage changes and correct variances.
• Closing: finalize deliverables, transfer them, capture lessons and confirm value.

The 40 processes are described as non-prescriptive. They are a menu that a team tailors, not a checklist that every project must complete. Commentators reviewing the 8th edition report that planning contains the largest share of processes, close to half; treat exact counts as something to confirm in the guide itself.

The 7th edition's eight domains

Many current study resources still use the 7th edition's eight performance domains: stakeholders, team, development approach and life cycle, planning, project work, delivery, measurement and uncertainty. These were defined around kinds of project activity rather than management disciplines. The 8th edition replaced them with discipline names, partly in response to practitioner feedback that the 7th edition was hard to apply. The ideas did not disappear. Team concerns now sit mainly under resources and the empowered culture principle; development approach and life cycle is treated as part of tailoring and planning; measurement is spread across the domains' monitoring guidance; uncertainty is covered by the risk domain.

How this relates to the exam content outline

The PMP exam is not organized by PMBOK Guide domains. Its 2026 content outline has three domains: People (33 %), Process (41 %) and Business Environment (26 %), containing 8, 10 and 8 tasks respectively. About 40 % of questions reflect predictive approaches and about 60 % adaptive or hybrid approaches, spread across all three domains. The exam domains describe what a project professional does; the PMBOK Guide domains describe areas of project performance. They overlap heavily, and it helps to see the links.

Note how much the Business Environment domain grew. In the 2021 outline it carried only 8 % of the exam; in the 2026 outline it carries 26 %, with tasks on governance, compliance, change control, risk, issues, continuous improvement and organizational change. Those topics align with the governance and risk domains of the 8th edition and with this course's lessons on organizational context. Process remains the largest domain, and People remains substantial.

Using domains in practice

Domains are best seen as lenses. When planning, you look at the project through each lens in turn and ask what it needs: what governance applies, what the scope is, how the schedule will work, how it will be funded and controlled, who the stakeholders are, what resources are required and what risks exist. When something goes wrong, the lenses help diagnose it: a missed date might really be a resources problem, a stakeholder problem or a governance problem. Tailoring, covered in lesson 6, decides how much formality each lens needs on a given project.

Canadian federal guidance uses similar lenses. The Project Complexity and Risk Assessment tool asks departments to rate projects on factors such as project characteristics, strategic risk, procurement, human resources, business and change management, and the result helps decide the level of oversight and documentation required.

Reading questions through the domains

When you read a PMP scenario, it helps to ask which domain the question is really testing. A question about a team member who keeps missing stand-ups looks like a schedule problem but is usually a People question about engagement or conflict. A question about a vendor who delivered late may be about procurement (Process) or about contract compliance and governance (Business Environment). A question about a regulator changing a rule mid-project points to evaluating external business environment changes. Identifying the domain narrows down the kind of answer the question expects: People questions often favour conversation, coaching and collaboration; Process questions often favour following or updating the plan; Business Environment questions often favour governance, compliance and alignment with organizational strategy.

The same lens works in practice. When a project struggles, list the symptoms and ask which domains they touch. Repeated late approvals point to governance; constant rework points to scope or quality; unclear ownership points to resources and stakeholders. Treating the right domain saves time spent fixing symptoms.

Finally, remember that the exam content outline is the authoritative guide to what the exam covers. The PMBOK Guide is one of several references PMI lists, alongside guides such as the Agile Practice Guide, so knowing the structure of the guide helps, but you should study from the outline's tasks.