Principle: focus on value

The second principle in the PMBOK® Guide – Eighth Edition from PMI® is focus on value. A project exists to produce an outcome that is worth more than it costs, not just to deliver a list of things on time and on budget. This lesson separates outputs from outcomes, benefits and value, shows where an owner decides, protects and realizes value on a construction project, and uses a value-engineering proposal on Northgate Distribution Centre, our fictional warehouse, to test it.

Learning outcomes

• Distinguish activities, outputs, outcomes, benefits and value, and give a construction example of each.
• Explain why meeting time, cost and scope targets does not prove a project delivered value.
• Identify when an owner defines, protects and realizes value over a project's life.
• Test a change or value-engineering proposal against the owner's outcome, not only its price.

The lesson

What the principle asks

Lesson 3 put this principle in one sentence: the project exists to deliver an outcome, not just a set of deliverables. PMI's short name for it is "focus on value", and the guide ties projects to organizational strategy through what it calls a system for value delivery. This principle is the one the eighth edition carried over from the seventh edition (2021) with the least change. Lesson 2 gave BRC's reading that the seventh edition's principle about enabling change also feeds it, because a new building delivers nothing until the organization changes how it works to use it.

The principle asks three things of you:

• Know what value means here. Value is defined by the people the project serves, and it differs from project to project. Write it down early.
• Judge work by its contribution. Challenge activities, features and spending that do not move the project toward that value, and look for ways to get more of it.
• Keep checking. What counts as value can shift as the project moves and as the organization's needs change. Revisit it at each major decision.

Outputs are not outcomes

The most useful habit this principle builds is keeping five words apart. Published study material on the eighth edition draws the chain like this, and Figure 1 is BRC's version of it applied to a warehouse:

• Activities are the work done.
• Outputs are what the work produces: the deliverables.
• Outcomes are the changes that happen when people use the outputs.
• Benefits are the gains (or losses) that follow from those changes.
• Value is the overall judgement: was the net result worth the money, effort and disruption?

The point for owners is in the tags. A CCDC 2-2020 stipulated price contract pays the contractor for outputs: a building that meets the Contract Documents, handed over at Ready-for-Takeover. Outcomes, benefits and value are not the contractor's to deliver. A project can finish on time and on budget and still produce weak value, because the building is used badly, or because the wrong building was specified in the first place.

Why on time and on budget is not enough

Time, cost and scope targets are proxies. They matter because they protect the business case, but they are not the business case. Commentary on the eighth edition makes the same point: the real test is whether the value delivered outweighs the money and effort spent. Three consequences follow for owner-side work.

• A saving can destroy value. Cutting a feature the business case depends on lowers the cost and the value at the same time, often by more.
• A cost can create value. Some additions pay for themselves many times over in operation. They need a clear case, not automatic rejection.
• Value is often realized after the project closes. On a building, most benefits arrive over years of operation, long after the general contractor has left. Someone on the owner's side has to keep measuring them.

Define, protect, realize

For an owner, value has a life cycle that runs longer than the construction contract. BRC uses three words for it, shown in Figure 2.

• Define happens before contract execution: the business case, the functional requirements that make the building worth having, the design and the tender. On a warehouse those requirements include clear height, dock count and floor flatness. This is where the owner has the most influence and the lowest cost of change.
• Protect runs through construction. Every change, substitution and value-engineering proposal either keeps the defined value intact or erodes it. The owner's job here is to test proposals against the outcome, not only against the price.
• Realize starts at handover and runs for years. The owner moves in, operates the building and checks whether the benefits in the business case actually arrive.

The eighth edition's Finance and Governance domains connect directly to this. Finance holds the budget, contingency and the value the money buys. Governance decides who can trade one against the other.

Value engineering is not cost cutting

Value engineering, done properly, looks for a way to deliver the same function for less, or more function for the same money. Cost cutting removes cost and accepts whatever function is lost. On a stipulated price contract the contractor may offer value-engineering ideas, and under CCDC 2-2020 any accepted change to the Work is documented by a Change Order or Change Directive. The commercial process is the same either way. What the focus on value principle adds is the test the owner applies before agreeing. Figure 3 is a simple way to sort proposals.

The dangerous quadrant is the bottom left. A false saving looks like good news on the cost report and only shows its price after handover. The top right is where judgement matters most: some added costs are worth paying, and the business case, not habit, should decide.

Northgate worked example

Northgate Distribution Centre is our fictional case study: a 12,000 m² single-storey tilt-up warehouse in Vaughan, Ontario, with 9.75 m (32 ft) clear height, 14 dock doors and ESFR sprinklers. The Contract Price with Halvorsen Builders Ltd. is $34,950,000 under CCDC 2-2020, with a $3,050,000 owner contingency. The full facts are on the Northgate fact sheet.

Suppose that in the spring of 2027, before the steel and joists are ordered, Halvorsen offers a value-engineering proposal: a lighter, shallower roof structure from a different supplier that saves $180,000 but lowers the clear height to about 9.1 m. On the cost report it looks like an easy win. The owner's PM runs it through the value chain in Figure 1 instead.

She does not simply refuse. She thanks Halvorsen, explains that clear height is a value-defining requirement, and asks whether the same supplier can meet 9.75 m for a smaller saving. That could turn a false saving into a genuine one, like proposal 3 in Figure 3, and it keeps the conversation constructive.

She also records the decision and the reason in the change log, so that the executive can see that a saving was turned down for a stated value reason, and so that the requirement is protected on the next warehouse too. The figures in this example are hypothetical. None of them are part of the Northgate fact sheet.

Owner's move

• Write the value down. Before tender, list the three to five requirements the business case depends on, such as clear height, dock count and handover date, and share them with the design team and the contractor.
• Test proposals against outcomes. Ask what each change or substitution does to the use of the building, not only to the Contract Price.
• Name the value owner. Put someone from operations in the change review, because they understand the outcomes better than anyone on the project team.
• Plan for realization. Agree before handover who will measure the benefits after Ready-for-Takeover, and when.
• Report value, not just variance. Add a line to the monthly report on risks to the value-defining requirements, alongside schedule and cost.

Common mistakes

1. Equating success with on time and on budget. These protect value but do not prove it.
2. Accepting every saving. A saving that removes function the business case relies on is a false saving.
3. Rejecting every added cost. Some additions pay back many times in operation. Decide on the business case.
4. Leaving operations out until handover. The people who will realize the value should help protect it during construction.
5. Stopping measurement at closeout. Most of a building's benefits arrive after the project ends. If nobody measures them, the next business case is guesswork.

Quick quiz

1. On Northgate, which of these is an outcome rather than an output?

   1. The completed tilt-up panels
   2. The warehouse at Ready-for-Takeover
   3. Racking installed and the building in use
   4. The commissioning report

2. Under a stipulated price contract, which links in the value chain is the general contractor paid to deliver?

   1. Activities and outputs
   2. Outcomes and benefits
   3. Benefits and value
   4. All five

3. A substitution saves money but reduces a function the business case depends on. What is it?

   1. Value engineering
   2. A false saving
   3. A benefit
   4. Scope creep

4. When does an owner usually have the most ability to change the value a building delivers?

   1. During commissioning
   2. After final completion
   3. Before the contract, when requirements and design are set
   4. At the monthly schedule review

5. Which statement best reflects the focus on value principle?

   1. Deliver every feature in the specification at the lowest cost
   2. Judge work by whether it moves the project toward outcomes worth more than they cost, and revisit that as things change
   3. Leave value to the sponsor and concentrate on schedule
   4. Value is fixed in the business case and never changes

Show answers and explanations

1. C. Panels, the handed-over building and the report are outputs. The outcome is the change that happens when the building is used.
2. A. The contract pays for the work and the deliverables. Outcomes, benefits and value depend on what the owner does with the building.
3. B. Value engineering keeps the function and lowers the cost. Removing the function is a false saving.
4. C. The define stage has the most influence and the lowest cost of change.
5. B. Value is defined by stakeholders, and what counts as value can shift during the project.

Key terms

Output

A deliverable produced by project work, such as a building handed over at Ready-for-Takeover.

Outcome

The change that happens when people use an output.

Benefit

A gain, or a loss, that follows from an outcome.

Value

The overall judgement of whether a project's net result was worth its cost, effort and disruption.

Value engineering

A structured search for a way to deliver the required function for less cost, or more function for the same cost.

False saving

A cost reduction that removes function the business case depends on, so that value falls by more than cost.

Value-defining requirement

A requirement that the business case depends on, such as clear height in a warehouse, which changes should not erode without an explicit decision.

References

1. Project Management Institute, PMBOK® Guide – Eighth Edition (product page: November 2025, 408 pages, "focus on value" as the second principle, value delivery system linking projects to strategy).
2. Rebel's Guide to Project Management, The Principles of Project Management (PMBOK 8 Guide) (value differs by project and can change; challenge work that lacks value).
3. PM Study Circle, PMBOK Guide 7th vs 8th Edition (success judged by outcomes rather than deliverables).
4. PMExams, PMBOK 8 Outputs, Outcomes, Benefits and Value Explained (the chain from activities to value; independent study material).
5. QRP International, PMBOK® Guide Eighth Edition: What it Means for Project Managers (success judged by value delivered against effort and expense).
6. The PM Podcast, Episode 554: PMBOK 8 six principles (efficiency does not guarantee the intended outcome).

Verified on November 4, 2026.

Next lesson in this trackPrinciple: embed quality