Picture this. The project finishes on schedule. It lands on budget. Every deliverable passes acceptance.
Six months later, nothing in the business has improved.
Was that project a success?
The PMBOK Guide, Eighth Edition, says: not necessarily.
Table of Contents
The habit: success means hitting the baseline
Most of us learn project management through constraints. Scope, schedule, cost, quality. Deliver within them, and you have succeeded.
That view is useful. It is also incomplete.
The Eighth Edition defines a project as a temporary initiative undertaken to create value. It defines project success as a shared view among stakeholders that the value was worth the effort and expense. Delivering the work is not enough.
Two kinds of success
The guide asks you to assess success in two dimensions:
Project outcomes. Did the project realize the value it was meant to create?
Project management processes. Did the team deliver within cost, scope, time, and quality?
Both matter. They can point in opposite directions.
The guide gives two examples:
The Sydney Opera House cost about 14 times its original budget and took 14 years instead of 4. Its management is generally seen as a failure. Its result exceeded expectations many times over.
A newly built overpass in Montreal was demolished a year after a well-managed construction effort, because it did not fit the plans for the bridge next to it.
One project was managed badly and succeeded. The other was managed well and failed.
Output is not the outcome
The principle behind this is called Focus on Value.
An output is what you produce. An outcome is what changes because of it.
Take a new scheduling tool for an operations team. The tool is the output. The outcome the sponsor wants is fewer delays. If people do not know how to use the tool, or it does not fit how they work, the output exists and the outcome does not.
The guide makes a similar point. Adding training to a software project can be what turns a deliverable into a result. Sometimes the highest-value change is a deliverable nobody put in the original scope.
This applies in every approach:
In predictive projects, the baseline defines the outputs. Value still decides whether the baseline is right.
In agile projects, the team and customer decide which features are worth the time and money.
In hybrid project delivery, different parts of the project may carry different value, so they may need different attention.
What changed in the 8th Edition
Three things make this hard to ignore:
Value is in the definitions. The guide updated its core terms because marketplace expectations moved from efficient delivery to the project's value proposition.
Every performance domain ends with a value check. The guide states that a project schedule does not add value by itself. Its importance is that it aligns stakeholders around when value arrives.
Stopping is an option. If the project is unlikely to deliver the intended value, the guide says it may be best to end it.
That last point is uncomfortable. It is also honest.
A scenario
You are three months into a project. Schedule and budget are on track. Then a stakeholder tells you the business need has shifted. The current deliverable will still be completed, but it will solve a smaller problem than planned.
The weak response: "We are on track. We keep going."
The stronger response asks:
What outcome did the sponsor approve this project for?
Does the current plan still deliver it?
Who has the authority to change direction, pause, or stop?
What should we say to stakeholders now, before the gap grows?
That is stakeholder management and governance working together, guided by value.
Four habits for busy professionals
You do not need a new tool. You need four small changes:
Add an outcome line to your status report. Next to schedule and cost, write one sentence: "Intended outcome, and are we still on course for it?"
Ask what each deliverable is for. If nobody can answer in one sentence, ask the sponsor.
Review value at every gate or iteration. Use the same rhythm your project already has: a phase gate in a predictive project, a review in an agile one.
Practice the stop conversation. Learn to say, calmly, "This may no longer be worth it." That is servant leadership toward the organization.
The insight to keep
On-time, on-budget delivery is the professional standard. It is not the purpose.
The purpose is the change the project was created to make. The Eighth Edition asks you to keep both in view at once.
P.S. Planning your PMP study plan? The PMP Study Plan Calculator breaks your preparation down by domain weights and available study time. https://vandersonbaril.com/products/pmp-study-calculator/
That's it for this week—thank you for reading, and see you next Saturday.
