PMBOK 8: What Shifts When Value Comes First with Mike Hannan

Too many project reviews end with a green dashboard and no serious answer to the question that matters most: Is this investment still creating the value we expected? 

Scope, schedule, budget, and risk still matter. They help us understand whether delivery is under control. But control is not the same as value. A team can execute the approved baseline beautifully while the business case weakens, the environment shifts, or a better use of scarce capacity appears elsewhere. 

That is why the updated definition of a project in PMBOK 8 deserves more than a passing mention. 

In this episode, I’m joined by my longtime friend Mike Hannan, Founder and Principal Consultant at Fortezza Consulting, best-selling author of The CIO’s Guide to Breakthrough Project Portfolio Performance, and a member of the PMBOK Guide Eighth Edition development team. Mike has spent his career helping leaders improve project and portfolio performance, so his perspective belongs in this conversation from both sides: he helped shape the standard, and he knows what it takes to make these ideas useful inside a real organization. 

The definition changed because the job changed 

For years, the familiar definition described a project as “a temporary endeavor undertaken to create a unique product, service, or result.” PMBOK 8 defines it as “a temporary initiative in a unique context undertaken to create value.” 

That final word changes the center of gravity. 

The older definition made the output easy to see. We were creating a product, service, or result. The new definition makes the purpose explicit. The work exists to create value. 

That does not make delivery discipline less important. It gives that discipline a reason. Schedule management matters because time can affect value. Cost management matters because the investment must remain worthwhile. Risk management matters because uncertainty can strengthen or destroy the value proposition. Scope matters because the work should produce the outcome the organization is counting on. 

When the project baseline becomes the destination, the PMO can do everything “right” and still help the organization complete the wrong work. 

The baseline is not the business case 

Mike poses a deliberately simple scenario in our conversation. Imagine that spending 10 percent more on a project could double the value it creates. Should the project manager automatically reject that option because the approved budget is the approved budget? 

Of course not. The sponsor deserves the opportunity to make that decision. 

Now take the same thinking to the portfolio. If one project is producing little value and another has the potential to create significantly more, the right leadership move may be to stop or slow the weaker investment and redirect people, money, or time to the stronger one. 

That is not a failure of project control. It is what responsible investment management looks like. 

The PMO is uniquely positioned to make those tradeoffs visible because it can see across initiatives, constraints, dependencies, and capacity. But that requires the PMO to move beyond reporting whether each project is following its original plan. It must help leaders understand whether the portfolio is still the best use of the organization’s limited resources. 

Put the value proposition into governance 

Mike names a question he says is almost absent from PMO status meetings: “How are we tracking for the target value?” 

He follows it with another: “Is the value proposition getting stronger or weaker?” 

Those questions change the quality of the conversation. A status review can still cover milestones, budget, issues, and risks. The difference is that those signals are interpreted through the value the project is supposed to create. 

A schedule risk is no longer important only because a date may move. It matters because delay may reduce revenue, extend exposure, postpone a mission outcome, increase operating cost, or make the solution less useful. A cost increase is not automatically unacceptable. It should be evaluated against the additional value, avoided loss, or strategic advantage it may create. A scope decision is not just a change-control event. It is a choice about which outcomes matter enough to protect. 

The same logic applies when a risk materially changes the business case. If the expected value falls below the cost, sacrifice, or available alternatives, cancellation may be the most responsible outcome. Finishing the project is not always the same as protecting the investment. 

Projects are investments, even when value is not financial 

Mike wanted the word investment to be even more prominent in PMBOK 8, and I understand why. Every project consumes something the organization cannot use somewhere else. 

We invest money, but we also invest time, energy, leadership attention, focus, credibility, and scarce human capacity. We accept risk and opportunity cost. We ask people to change how they work. Those sacrifices should produce something worth having. 

In a commercial organization, that value may include revenue, margin, cost reduction, speed, customer retention, or risk avoidance. In a nonprofit, public-sector, or mission-driven organization, it may be better service, improved access, safer communities, public trust, or social IMPACT. The measure changes, but the obligation does not. Leaders still need to know whether the outcome is worth the investment. 

This is why business language must come before project-management language. Executives do not need another description of the process. They need decision support that connects the work to the outcomes, tradeoffs, and value they are responsible for delivering. 

PMBOK 8 points toward practical value techniques 

The value shift in PMBOK 8 is not only philosophical. Mike highlights several techniques included in the guide that can help leaders make the idea more concrete, including the value breakdown structure, critical path drag, and critical path drag cost. 

The episode does not turn these techniques into a full training class, and neither should this article. The important point is that each one helps leaders connect delivery choices to value. 

A value breakdown structure can help teams make the expected value more visible rather than treating it as an assumption buried inside a business case. Critical path drag helps identify how much a critical activity is extending the project duration. Drag cost adds the economic or outcome consequence of that delay. Together, these ideas can move schedule conversations from “Are we late?” to “What is the delay costing, and where would intervention create the greatest return?” 

That is a much more useful leadership conversation than treating every task, risk, or variance as equally important. 

The PMO leadership move 

PMO and transformation leaders do not need to abandon the baseline to make this shift. They need to connect the baseline to the business result. 

In your next portfolio or status review, add one question: Is the value proposition getting stronger or weaker? 

Then listen for what the answer reveals. Have the assumptions changed? Is the intended outcome still relevant? Has the cost of delay increased? Is a higher-value option available? Do leaders need to invest more, reduce scope, accelerate a decision, or stop the work? 

The question is simple. The leadership judgment behind it is not. That is exactly why it belongs in the PMO. 

PMBOK 8 makes value part of the definition of the work. For PMO and transformation leaders, the opportunity is to make value part of the operating rhythm, the governance conversation, and the decisions that determine where the organization places its next dollar, hour, and unit of attention. 

Press play above to hear Mike’s inside perspective on PMBOK 8 and what this value shift means for the way you lead projects and portfolios.