Six PMBOK 8 Principles You Can Actually Use
Principles have a presentational problem. Nobody disagrees with them, which makes them easy to print on a poster and hard to use on a Tuesday. A project manager under pressure does not stop and ask whether they are adopting a holistic view. They decide whether to tell the sponsor about the slippage now or at the review on Thursday.
The test worth applying to any principle is whether it ever changes a decision. On that test the six in the Eighth Edition hold up better than most, provided each one is translated into a question specific enough to answer. Section 3 of The Standard for Project Management carries them, and they earn their keep at the moment a decision could reasonably go either way.
The six, and the decision each one is for
Adopt a holistic view asks what else moves when you move this. Compressing a schedule by running two workstreams in parallel changes cost, resource contention, defect risk and the sponsor's exposure at the same time. The question it forces is which of those you have actually looked at, and the answer on a bad day is one of them.
Focus on value asks whether the work still deserves to be done. It applies hardest to a project that is running well against its plan and delivering something the business has stopped needing, which is a failure mode no variance report will ever surface. The question is whether the value proposition has changed since the business case, and it is worth asking out loud at every stage boundary.
Embed quality into processes and deliverables asks where the defect will be found. Quality built into how the work is performed is cheaper than quality inspected at the end, and the practical question is whether your acceptance criteria are written well enough that somebody could disagree with you using them. Criteria nobody could fail are not criteria.
Be an accountable leader asks who carries this if it goes wrong. It covers the unglamorous obligations: naming the problem while it is still small, recognising when the team needs an answer from you and giving them one, and staying answerable for the result of a delegation. The question is whether the person who will carry the consequence is the person taking the decision.
Integrate sustainability within all project areas asks what this leaves behind. Environmental effect is part of it, and so are resource choices, supply chain decisions, and whether what you build can be operated and maintained by the people inheriting it. The question is what the whole-life consequence of this choice is, and it belongs in the decision itself, at the point where the option is still open.
Build an empowered culture asks whether the team has enough authority to do what you are holding them accountable for. Empowerment without clear boundaries produces anxiety, and boundaries without authority produce a team that checks everything. The question is whether the people closest to the work can decide the things they understand best.
Where two of them pull against each other
Principles presented as a list imply they can all be satisfied at once. In practice two pairs regularly conflict, and noticing the conflict is more useful than reciting the list.
Value and sustainability collide whenever the cheaper option is worse over the whole life of the thing being built. A cladding specification, a battery chemistry, a hosting arrangement: the option that protects this project's budget can impose a cost on the organisation that outlasts everybody involved. Sustainability is one legitimate factor among several and does not automatically override feasibility, safety or a stakeholder commitment. The useful move is to write the trade into the decision record, with both figures on it, so the choice is made in the open.
Empowerment and accountability collide whenever a delegated decision goes badly. A project manager who has genuinely empowered a team and then intervenes at the first poor outcome has withdrawn the empowerment and will not get it back cheaply. One who never intervenes has abandoned the accountability. The workable position is to set the boundary in advance, in terms of consequence rather than subject matter, so that everybody knows which decisions come back and why. Working out where that line sits on a particular project, with a particular team, is the sort of judgement a structured PMP exam preparation course can take you through repeatedly before it matters.
Using them when you are stuck
The practical application is diagnostic. When a decision will not resolve, run it past the six questions in order and see which one it fails. A defence integration programme fitting a communications suite into an existing platform spent three weeks unable to choose between two antenna configurations, with both engineering teams entrenched and the cost difference marginal.
Run through the questions, the deadlock came apart quickly. Nothing failed on value or quality, because both options met the requirement. It failed on the holistic view: one configuration required a structural modification that pushed the platform outside an existing maintenance agreement, which nobody in the room owned and nobody had costed. It also failed on accountability, because the decision had been delegated to two teams that between them had no authority over the maintenance contract. The answer was not a better technical argument. It was that the decision belonged one level up, with the cost of the modification attached to it.
For a PMP® candidate, the thing to carry is that the principles are guides for judgement and never a checklist to be satisfied in order. In a difficult situation, asking which principle is under pressure usually identifies what the decision is really about.
Putting one question into a meeting you already hold is the least effortful way to make these real. At each stage boundary, ask whether the value proposition has changed. At each delegation, ask whether the team can decide what they are accountable for. Two questions, asked consistently, do more than a laminated card ever will, and neither of them adds a meeting to anybody's week.
Interested in going further?
Principles are simple to state and awkward to apply when two of them point in opposite directions on the same decision. Omega's PMP® Exam Preparation works through those conflicts in realistic situations, where the six have to be weighed against each other.
The six principles sit in The Standard for Project Management, published inside the PMBOK® Guide Eighth Edition.
Ad · Amazon affiliate link.
References
A204: How to Think Through an AI or Sustainability PMP Scenario
A055: The Stewardship Lens: Connecting AI, Sustainability and Ethics
A007: The Standard for Project Management vs the PMBOK Guide
A043: When Should a Project Manager Escalate?
A044: Analyse Before You Act: A Better Way to Read PMP Scenarios
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
