The principles of project management

Principles are fundamental norms or values that guide behavior. Unlike processes, which describe what to do, principles describe how to think and act whatever approach the project uses. The PMBOK Guide 8th edition, published in November 2025, sets out six principles in The Standard for Project Management. They replace the twelve principles of the 7th edition, which many candidates and practitioners still use, so this lesson explains both: the six current principles in detail, and how the older twelve map onto them. Principles matter on the PMP exam because many situational questions have no single "correct process"; instead, the best answer is the one most consistent with these principles.

Why principles rather than rules

Projects vary enormously. A two-week marketing campaign, a ten-year nuclear refurbishment and a software product with continuous releases cannot all follow the same steps. Principles give a common foundation that works across approaches: they tell you what good looks like without prescribing the method. They also help when the method runs out. When a situation arises that no plan anticipated, a project manager guided by principles can still choose a sensible response.

Principles in the PMBOK Guide are not ranked and are not meant to be applied one at a time. They reinforce each other, and real decisions usually draw on several at once. They also overlap with general management ideas, which is deliberate: project management sits inside organizations and should be consistent with good leadership, governance and ethics generally.

The six principles of the 8th edition

Adopt a holistic view

A holistic view means thinking in systems. A project has many interacting parts, and it sits inside an organization and an environment that also change. Systems thinking helps a project manager anticipate side effects: shortening the schedule may increase cost and risk; adding a feature may increase training needs in operations; a supplier delay may affect a regulatory filing date. It also means recognizing complexity, situations where cause and effect are hard to predict, and responding with experiments, feedback and adaptation rather than pretending the plan can foresee everything. In the 7th edition this idea was spread across the principles of systems thinking, complexity, and adaptability and resiliency.

Focus on value

Lesson 2 covered value in detail. As a principle, it means continually asking whether the project is still worth doing and whether the work being done contributes to the intended outcomes. Value can be financial or non-financial, and different stakeholders may define it differently, so engaging stakeholders to understand value is part of this principle. Focusing on value also means being willing to stop or redirect a project when the case for it weakens.

Embed quality

Quality is the degree to which a set of characteristics fulfills requirements, including stakeholders' stated and implied needs. Embedding quality means designing it into processes and products from the start rather than relying on final inspection. It includes clear acceptance criteria, appropriate standards, prevention over inspection, and continuous improvement. In adaptive teams, practices such as a definition of done, automated testing and frequent reviews embed quality into each increment. The cost of quality concept, covered in later courses, explains why prevention is usually cheaper than fixing defects late.

Be an accountable leader

This principle merges two of the 7th edition's principles: being a diligent, respectful and caring steward, and demonstrating leadership behaviors. Accountability means owning decisions and their consequences. Stewardship means managing the resources entrusted to the project, money, people, materials, data and reputation, responsibly and in compliance with law and policy. Leadership means motivating, influencing, coaching and learning, and it can be exercised by anyone on the team, not only by the person with the title. The PMI Code of Ethics, introduced in lesson 3, gives this principle concrete form.

Integrate sustainability

Sustainability is new as a named principle in the 8th edition. It asks project professionals to consider environmental, social and economic effects across the full life cycle of what the project creates, not just during delivery. Examples include choosing lower-carbon materials, planning for maintenance and disposal, considering effects on local communities and workers, and avoiding solutions that are cheap to build but costly to run. PRINCE2 7 made a similar move by adding sustainability as a performance target, which shows how widely the idea has spread. On the exam, sustainability considerations may appear as one factor in a trade-off decision.

Build an empowered culture

People deliver projects. An empowered culture is one in which team members have the authority, information and safety to make decisions, raise problems and suggest improvements. Psychological safety, the belief that you will not be punished for speaking up, is a key ingredient: teams that feel safe report risks and mistakes earlier, which protects the project. This principle draws together the 7th edition's principles about creating a collaborative team environment and effectively engaging with stakeholders, and it connects closely with servant leadership.

Mapping the 7th edition principles

Because study materials, colleagues and older practice questions often use the 7th edition's twelve principles, it helps to see how they relate to the six. The mapping below is an approximate guide, not an official PMI crosswalk.

Note what moved. Tailoring is no longer a separate principle but is woven into every domain; risk is handled mainly through the Risk performance domain; and sustainability appears for the first time. The underlying ideas are largely continuous, so if you studied the 7th edition you are not starting over.

Applying principles to exam scenarios

Principles help you eliminate wrong answers. Consider an option that hides a problem from stakeholders (violates accountable leadership), one that adds features without checking value (violates focus on value), one that skips testing to meet a date (violates embed quality), one that blames a team member publicly (violates an empowered culture), or one that fixes a local issue while creating a bigger one elsewhere (violates a holistic view). These options are usually distractors.

US organizations often connect these principles to public commitments and rules: for example, state climate and building performance policies for sustainability, accessibility requirements under the Americans with Disabilities Act and Section 508 for quality and stakeholder needs, and plain language expectations for federal communication.

Principles when principles conflict

Sometimes principles pull in different directions. Focusing on value might suggest releasing a feature quickly, while embedding quality suggests more testing. Integrating sustainability might favor a more expensive material, while the finance constraint pushes toward the cheaper one. In such cases, the holistic view helps: make the trade-off explicit, involve the stakeholders who own the consequences, and record the decision and its rationale. The worst response is to resolve the conflict silently, so that nobody realizes a principle was set aside.

On the exam, answers that make trade-offs transparent and involve the right decision-makers are usually stronger than answers that maximize a single principle at any cost.

A practical habit is to name the principle in the decision record: "we accepted a two-week delay to complete accessibility testing (embed quality) after confirming with the sponsor that the benefit timing still holds (focus on value)". Recording the reasoning helps later reviewers understand why a choice was made.