Focus on Value: PMBOK 8 Principle 2 Step-by-Step Guide

Have you ever delivered a project on time, within budget, with every scope requirement fulfilled — and yet the sponsor asked: “OK, but what was the actual business result?” If the answer did not come immediately, the problem was not execution. It was a lack of focus on value.

This scenario is far more common than it seems. Projects that meet 100% of technical requirements yet fail to generate measurable business impact are symptoms of a delivery-oriented management approach — not a results-oriented one. PMBOK 8 Principle 2 — Focus on Value — exists to solve exactly this. It demands that every decision, every prioritization, and every deliverable be evaluated through the lens of the value it creates for stakeholders and for the organization as a whole.

In this guide you will find:

• What the “Focus on Value” principle is and what changed from PMBOK 7 to PMBOK 8
• Why this principle matters — and what happens when it is ignored
• Expected behaviors and recommended practices
• A step-by-step guide to applying it in 7 stages
• Practical examples in IT, construction, and marketing
• How to adapt it in predictive, agile, and hybrid environments (tailoring)
• The relationship with performance domains and the other 5 principles
• The 5 most common mistakes — and how to avoid them
• A quick-application checklist you can use today

1. WHAT IS THE “FOCUS ON VALUE” PRINCIPLE

Straight to the point

Focusing on value means ensuring that every project activity — from planning to final delivery — is driven by the generation of real, measurable, and sustainable benefits for stakeholders and for the organization. Instead of measuring success by scope delivered, schedule met, or budget controlled, the project manager measures success by the impact the project generates.

This principle does not deny the importance of schedule, cost, and scope. It subordinates them to a larger question: “Does this deliverable generate value for the people who matter?”

In practice, focusing on value requires the project manager to:

• Define what value means from the very beginning — together with the sponsor and stakeholders
• Establish value indicators (not just operational performance metrics)
• Continuously evaluate whether deliverables contribute to expected outcomes
• Make trade-off decisions (scope, schedule, cost) based on value impact
• Consider value across multiple dimensions: financial, social, environmental, and organizational
• Ensure that value is not limited to the moment of delivery but includes long-term sustainability

Value, in the context of PMBOK 8, is multidimensional. It is not just financial return. It can be risk reduction, increased organizational capability, positive social impact, regulatory compliance, or brand strengthening. The project manager must understand which type of value takes priority in each context.

2. WHAT CHANGED FROM PMBOK 7 TO PMBOK 8

In PMBOK 7 (2021), the concept of focusing on value already existed as Principle 1, titled “Focus on Value”. It was one of twelve principles in the previous edition, centered on value delivery and the connection between deliverables and organizational benefits.

In PMBOK 8 (2025), the concept was promoted to Principle 2 — now one of only six principles. But the change goes far beyond numbering. The scope of the principle was significantly expanded: PMBOK 8 explicitly integrates sustainability, measurable outcomes, and a multidimensional view of value that encompasses financial, social, and environmental aspects.

What this means in practice: If you were already applying the focus on value from PMBOK 7, you have a solid foundation. But in PMBOK 8, the principle gained depth: value is no longer just “delivering what the client asked for.” It is delivering measurable, sustainable results aligned with multiple dimensions of impact. You need to define value indicators from initiation, monitor them continuously, and ensure that trade-off decisions prioritize real value over technical compliance.

3. WHY THIS PRINCIPLE MATTERS

Focusing on value matters because it solves the most fundamental problem in project management: the disconnect between deliverables and outcomes.

Without a focus on value:

• Projects deliver scope but not impact. The team completes every task in the plan, but the sponsor sees no business result. The project becomes a “technical success and strategic failure.”
• Trade-off decisions are suboptimal. When the PM needs to cut scope, extend the timeline, or reallocate budget, decisions are made based on operational constraints — not on value impact. The result: high-value features are sacrificed to preserve low-value ones.
• Stakeholders lose confidence. When the project fails to demonstrate tangible value generated, the organization questions the relevance of project management as a whole.
• Rework increases. Without a clear definition of value, the team builds based on assumptions. When the outcome does not meet real expectations, the cycle of changes and rework begins.
• The sustainability of results is ignored. The project delivers on the target date, but no one assesses whether the benefit is sustained in the months and years that follow. Value evaporates.

With a focus on value:

• Every decision is filtered by impact — not by convenience.
• Prioritization becomes objective and defensible.
• Communication with stakeholders gains clarity (“we have generated X in value so far”).
• Strategic alignment is continuous — not limited to the initial business case.
• The project builds credibility and reputation for the project management function within the organization.

PMI positions this principle as the second of six because value is the fundamental purpose of any project. Holistic Thinking (Principle 1) provides the context; Focus on Value defines the objective.

4. EXPECTED BEHAVIORS

A professional who applies the “Focus on Value” principle demonstrates the following behaviors:

• Defines value explicitly at the beginning of the project. Does not assume that everyone knows what value means — facilitates the conversation with the sponsor and stakeholders to document expected outcomes.
• Distinguishes deliverables from outcomes. A deliverable is what the project produces (software, building, campaign). An outcome is the impact the deliverable generates (revenue, savings, satisfaction). The PM focuses on the latter.
• Establishes measurable value indicators. Transforms vague expectations (“improve the process”) into concrete metrics (“reduce processing time by 30% within 6 months”).
• Evaluates value continuously — not just at delivery. At each sprint review, at each phase gate, at each milestone, asks: “Are we generating the expected value? Do we need to adjust?”
• Makes trade-off decisions through the lens of value. When scope needs to be cut, asks “which feature generates the least value?” — not “which one is easiest to remove?”
• Considers multiple dimensions of value. Financial value, social value, environmental value, organizational value. Not all value is monetary.
• Communicates value generated — not just status. Instead of “project 78% complete,” reports “we have delivered $500K in operational savings so far, with an additional $200K projected for next quarter.”
• Thinks about value sustainability. Asks: “Will the value we are generating be sustained after project delivery, or will it deteriorate?”

These behaviors are not optional. They are the practical manifestation of the principle and should be observable in the project manager’s daily work.

5. RECOMMENDED PRACTICES

The most important practices for operationalizing the focus on value include:

• Value Statement in the Project Charter. Include an explicit value declaration in the project charter — not just generic objectives, but measurable expected outcomes with indicators, targets, and timelines.
• Value Metrics Dashboard. Create a value metrics dashboard (separate from the progress dashboard) that shows: planned value vs. realized value, projected future value, and the value gap.
• Value-Based Prioritization. Use techniques such as WSJF (Weighted Shortest Job First), MoSCoW, or Cost of Delay to prioritize the backlog and scope based on value — not on ease of implementation.
• Benefits Realization Plan. Create a formal benefits realization plan that maps: which benefits are expected, when they will be realized, how they will be measured, and who is responsible for each one.
• Value Review at each milestone. Incorporate a value review at each phase gate, sprint review, or significant milestone. Reviewing progress alone is not enough — you must also review whether the expected value is still achievable.
• Stakeholder Value Mapping. Map what each stakeholder group considers “value” — because not everyone values the same thing. The sponsor may value ROI, the end user may value usability, and the regulator may value compliance.
• Documented Trade-off Framework. Establish decision criteria for trade-offs (scope vs. schedule vs. cost) based on value impact. Document the rules before the decision is needed.
• Post-Project Value Assessment. Schedule post-project reviews (3, 6, and 12 months after delivery) to assess whether planned value is materializing.

6. HOW TO APPLY THE PRINCIPLE IN PRACTICE (STEP BY STEP)

Step 1 — Define what value means for this project

Before planning anything, facilitate a session with the sponsor and key stakeholders to answer: “What does this project need to generate to be considered a success?” Do not accept generic answers like “improve efficiency.” Push for specificity: “Reduce order processing time from 48 hours to 12 hours by December 2026.”

Document the result in the Project Charter as a Value Statement — a formal declaration of value with indicators and targets.

Step 2 — Map the dimensions of value

Identify all relevant value dimensions for the project:

• Financial value: ROI, cost reduction, revenue increase
• Operational value: efficiency, productivity, error reduction
• Strategic value: market positioning, organizational capability
• Social value: community impact, accessibility, inclusion
• Environmental value: emissions reduction, efficient resource use
• Regulatory value: compliance, legal risk reduction

For each dimension, define: the indicator, the target, who is responsible for measurement, and the frequency of evaluation.

Step 3 — Create the Benefits Realization Plan

Formally document:

• Which benefits are expected (with quantifiable indicators)
• When each benefit will be realized (timeline)
• Who “owns” each benefit (responsible for realization)
• How the benefit will be measured (data source, calculation method)
• Which risks could prevent the benefit from being realized

This plan is the reference document for all value-related decisions throughout the project.

Step 4 — Implement value-based prioritization

Use formal techniques to prioritize scope, features, and tasks:

• WSJF for scaled agile environments — prioritizes by value divided by the size of the work
• MoSCoW to define what is Must-Have vs. Should-Have vs. Could-Have
• Cost of Delay to quantify the cost of not delivering a feature on time
• Kano Model to differentiate mandatory, desirable, and delighter features

The rule is simple: whenever there is a “what do we do first” decision, the answer must come from value, not from convenience.

Step 5 — Monitor value continuously

Create a Value Dashboard that shows:

• Planned value vs. realized value (per benefit)
• Projected future value (based on current progress)
• Value gap (difference between what was planned and what is being realized)
• Risks to value realization

Present this dashboard at every status review, sprint review, or phase gate. It does not replace the progress report — it complements it with the most important dimension.

Step 6 — Make trade-offs through the lens of value

When the need arises to cut scope, adjust the schedule, or reallocate budget, use the trade-off framework documented in Step 4. Ask:

• “Which option preserves the most value for stakeholders?”
• “Which option protects the most critical benefits of the project?”
• “What is the impact of each option on long-term value (not just the immediate timeline)?”

Document every trade-off decision with its value justification. This creates traceability and credibility.

Step 7 — Assess value post-delivery

Focusing on value does not end at project delivery. Schedule formal reviews at:

• 3 months post-delivery: Are the short-term benefits materializing?
• 6 months post-delivery: Are the medium-term benefits on track?
• 12 months post-delivery: Has sustainable value been achieved?

These reviews feed lessons learned and improve the organization’s ability to estimate and realize value in future projects.

7. WHEN TO APPLY THIS PRINCIPLE

Focusing on value should be applied from the beginning to the end of the project — and beyond. But there are moments when it is especially critical:

• At initiation: when the business case is approved and the Project Charter is developed. This is the time to define expected value with precision.
• During scope prioritization: when the team decides what goes in and what stays out. Prioritization must be driven by value, not by technical preference.
• During change analysis: when a change request arrives, the first question should be: “What is the impact on value?” — before assessing impact on schedule and cost.
• At the sprint review / phase gate: the formal moment to verify whether value is being delivered as planned.
• In trade-off decisions: when it is necessary to cut scope, adjust the timeline, or reallocate budget, the decision should maximize value preservation.
• In risk management: risks should be assessed by their potential impact on value — not just on schedule or cost.
• In stakeholder communication: every status communication should include the dimension of value generated — not just operational progress.
• After delivery: the post-project assessment should verify whether planned value has materialized.

Focusing on value is not an event — it is a management habit that must be present in every project decision.

8. PRACTICAL EXAMPLES ACROSS DIFFERENT PROJECT TYPES

Example 1 — IT Project: Cloud Migration

Situation: A company is migrating its on-premise infrastructure to the cloud. The technical scope is clear: migrate 47 servers to AWS in 8 months.

Without a focus on value: The team measures success by the number of servers migrated per month. By the end of the project, all 47 servers are in the cloud. Success? Technically, yes. But the expected cost reduction did not materialize because no one optimized instance sizing. Availability worsened because the architecture was replicated without redesign. The sponsor is frustrated.

With a focus on value: The PM defines value at the outset: “35% reduction in infrastructure costs within 12 months + 99.9% availability.” At each sprint, the team evaluates: “Does this migration contribute to the cost target? Are we using the right instance sizing?” When they realize that migrating a legacy server would cost more in the cloud, they decide to modernize before migrating. The project runs 6 weeks late, but delivers a 42% cost reduction — above the target.

Result: Value preserved and exceeded. The 6-week delay is irrelevant in light of the financial outcome.

Example 2 — Construction: New Distribution Center

Situation: A retail chain is building a new distribution center to serve a growing region. Budget of $28 million, timeline of 18 months.

Without a focus on value: The manager focuses on schedule and cost. The facility is delivered on time and within budget. But the warehouse layout was designed based on 2024 volumes. By 2026, the growth of e-commerce changed the operational mix. The distribution center requires renovations within 8 months — costing an additional $4 million.

With a focus on value: The PM defines value as “capacity to process 15,000 orders per day with flexibility for 40% growth over 3 years.” During planning, the PM identifies that the layout needs to accommodate both store picking and e-commerce picking. The project is adjusted for a modular layout, at an additional cost of $1.2 million. Construction runs 4 weeks late. But the distribution center operates for 4 years without needing renovation.

Result: A $1.2 million investment avoided $4 million in renovations. Sustainable value.

Example 3 — Marketing: Corporate Rebranding

Situation: A B2B technology company is rebranding to align with its market repositioning. The scope includes a new visual identity, website, sales materials, and launch at an industry event.

Without a focus on value: The team focuses on delivering all materials before the event. Everything is delivered on time. The new brand is attractive, modern, and professional. But the sales team was not trained to use the new materials. Existing clients are confused by the change. The sales pipeline drops 15% the following quarter because messaging became inconsistent.

With a focus on value: The PM defines value as “20% increase in qualified sales pipeline within 6 months + brand recognition in the new positioning (measured by survey).” During planning, the PM identifies that training the sales team is as important as creating the materials. Training sprints and a pilot with 3 strategic clients are included before the broad launch. The launch is delayed by 3 weeks, but the pipeline grows 28% in 6 months.

Result: Value measured, achieved, and exceeded. The rebranding generated real business impact.

9. TIPS, SHORTCUTS, AND TOOLS

• Use the Value Proposition Canvas to define value clearly from the start of the project. It forces the team to articulate: “For whom are we generating value, what is the pain, and what is the gain?”
• Create a Value Dashboard in Power BI, Tableau, or even a spreadsheet. It should contain: planned value vs. realized value, value projection, value gap, and risks to realization. Present it at every status meeting.
• Adopt the WSJF (Weighted Shortest Job First) framework for prioritization in agile environments. It calculates priority by dividing the value of an item by the time needed to deliver it.
• Include the question “What is the impact on value?” in every change analysis. Add a “Value Impact” field to the change request form.
• Use OKRs (Objectives and Key Results) to connect the project to strategy. Each project Key Result should be linked to an organizational OKR.
• Suggested tools: Jira (for value tracking per epic), Monday.com (for value dashboards), Miro (for Value Stream Mapping), ClickUp (for project goals linked to outcomes).
• Hold quarterly “Value Check” sessions with the sponsor and key stakeholders. Format: 30 minutes, 3 questions — “Is the planned value still relevant?”, “Are we on track to achieve it?”, and “Do we need to adjust the value definition?”
• Document trade-off decisions in a Decision Log with the value justification. This creates traceability and protects the PM in audits and retrospectives.

10. TAILORING — HOW TO ADAPT TO YOUR CONTEXT

In predictive (traditional) projects

In predictive environments, the focus on value manifests primarily in the business case, the benefits realization plan, and the phase gate reviews. The project manager connects each deliverable to planned value and verifies alignment at every phase transition.

• Core tool: Benefits Realization Plan — mapping each benefit with indicators, targets, owners, and realization timelines
• Critical moments: Business case development (value definition), phase gates (value verification), project closure (final value assessment), post-project reviews (value realization)
• Frequency: Formal value review at each phase gate; monthly monitoring of value indicators in sponsor status meetings
• Caution: In long predictive projects (over 12 months), the business context can change significantly. The value defined at the start may no longer be relevant at delivery. Revisit the value definition at each gate — not just the progress

In agile projects

In agile environments, the focus on value is native to the approach — but many teams lose this essence. The Product Owner is primarily responsible for defining and prioritizing value; the team delivers value increments every sprint.

• Core tool: Product Backlog prioritized by value (WSJF, MoSCoW, or Cost of Delay), Sprint Goal linked to a specific value outcome, and a Definition of Done that includes value criteria
• Critical moments: Sprint Planning (verify that selected stories maximize value), Sprint Review (assess value delivered with stakeholders — not just demonstrate features), Retrospective (evaluate whether the team is focusing on value or on velocity)
• Frequency: Every sprint — value is assessed incrementally. Broader value reviews at each PI (Program Increment) or quarterly
• Caution: The agile trap is confusing “delivering faster” with “delivering more value.” Teams that measure only velocity (points per sprint) may be delivering a lot of low-value scope. Monitor value delivered, not just speed

In hybrid projects

Hybrid projects face the challenge of maintaining a focus on value across two different cadences: the predictive phases (planning, procurement, construction) and the agile cycles (development, testing, iteration). Value can be broadly defined during predictive planning and incrementally refined in agile cycles.

• Core tool: Integrated Value Map — connecting business case benefits (predictive view) to incremental sprint outcomes (agile view). Each agile increment should be traceable to a benefit in the realization plan
• Critical moments: Integration points between predictive phases and agile sprints (when an agile increment feeds a predictive phase, value must be verified); phase gates (to adjust the value definition based on agile learnings)
• Frequency: Agile sprint reviews every 2–4 weeks + predictive value reviews at each phase gate. A value synchronization session between the predictive PM and the agile Product Owner at least biweekly
• Caution: The greatest risk in hybrid projects is that the predictive value definition and the agile value definition become disconnected. The PM must ensure that both sides are working with the same value definition — and that changes on one side are reflected on the other

11. RELATIONSHIP WITH PERFORMANCE DOMAINS

The “Focus on Value” principle influences all performance domains in PMBOK 8, but in distinct ways:

• Stakeholder Domain: Value is defined by the stakeholders. Without understanding what each group values, it is impossible to focus on the right value. This domain provides the “who” and the “for whom” of value.
• Scope Domain: Scope must be driven by value — every requirement, feature, or deliverable needs to be justified by the value it generates. Scope prioritization is the direct application of this principle.
• Governance Domain: Project governance must include value verification mechanisms (gates, reviews, dashboards). Governance decisions (continue, pause, cancel) should be based on value.
• Schedule Domain: The sequence of deliverables should prioritize realizing value as early as possible. “Deliver value early and often” is the temporal application of this principle.
• Finance Domain: The budget is not just a spending limit — it is an investment to generate value. Financial decisions should consider ROI, not just cost.
• Risk Domain: Risks should be assessed by their potential impact on project value — not just on schedule or cost. A risk that threatens the core value is more critical than a risk that threatens a secondary deadline.
• Quality Domain: Quality exists to protect and amplify value. Quality criteria should be derived from the value definition — not defined in isolation.

Interactions with the Other PMBOK 8 Principles

Focus on Value does not operate in isolation. It connects to, reinforces, and is reinforced by each of the other five principles:

12. COMMON MISTAKES WHEN APPLYING FOCUS ON VALUE — AND HOW TO AVOID THEM

The principle seems simple in theory. In practice, it is one of the most difficult to apply consistently. These are the 5 most frequent mistakes:

Mistake 1 — Confusing deliverables with value

Why it happens: The project management culture was built over decades around the “triple constraint” (scope, schedule, and cost). Many PMs were trained to measure success by completed deliverables. When the project charter says “deliver module X by March,” the PM focuses on delivering module X — without asking: “Will this module generate the outcome that justified the investment?”

How to avoid it: Add a Value Statement to the Project Charter. For each major deliverable, document: “This deliverable exists to generate [measurable outcome].” Monitor the outcome, not just the deliverable. If the module was delivered but the outcome did not materialize, the project has not yet generated value.

Mistake 2 — Defining value only at the start and never revisiting it

Why it happens: The PM builds an excellent business case, defines value with precision, obtains approval — and treats that definition as immutable. Six months later, the market context has changed, the organizational strategy has been adjusted, but the project’s value definition remains the same as on day one.

How to avoid it: Include a value review at each phase gate or every quarter (whichever comes first). Ask: “Is the value we defined at the beginning still the most important value? Do we need to adjust priorities, indicators, or targets?” The value definition is a living document — not a sealed contract.

Mistake 3 — Measuring value only in financial terms

Why it happens: ROI, payback, NPV, and IRR are the easiest metrics to calculate and present. Many organizations require financial justification for every project. The PM, out of convenience or pressure, reduces “value” to “financial return” — ignoring strategic, social, environmental, or organizational value.

How to avoid it: Use a multidimensional value matrix. For each project, identify and document value in at least 3 dimensions (financial, operational, strategic, social, or environmental). Assign weight to each dimension based on the project context. Present total value — not just ROI.

Mistake 4 — Focusing on value for the sponsor and ignoring other stakeholders

Why it happens: The sponsor is the one who approves the budget and makes the decisions. It is natural for the PM to prioritize what the sponsor values. But a project’s value is rarely unidimensional. If the system satisfies the sponsor but frustrates end users, the value will not be sustained.

How to avoid it: Conduct a Stakeholder Value Mapping at the beginning of the project. Identify what each stakeholder group considers “value” — sponsor, users, team, regulators, community. Find the points of convergence (where the same outcome generates value for multiple groups) and the points of conflict (where generating value for one group reduces value for another). Prioritize with transparency.

Mistake 5 — Not measuring value post-delivery

Why it happens: The project ends, the team is disbanded, the PM moves on to the next project. No one goes back to verify whether the planned benefits materialized. The organization invests millions in projects but does not know how much real value was generated.

How to avoid it: Include post-project reviews in the Benefits Realization Plan. Define owners (who do not need to be the PM — it can be the sponsor or the benefit owner). Schedule formal reviews at 3, 6, and 12 months. Use the results to calibrate value estimates for future projects.

13. QUICK-APPLICATION CHECKLIST

Use these 7 items as a quick reference before every decision or project milestone:

1. Have I explicitly defined value in the Project Charter — with measurable indicators, targets, and owners?
2. Have I mapped what each stakeholder group considers “value” — not just the sponsor?
3. Is scope and backlog prioritization based on value (WSJF, MoSCoW, Cost of Delay) — or on convenience?
4. Do I have an updated Value Dashboard that shows planned value vs. realized value?
5. In trade-off decisions, did I assess the impact on value before assessing the impact on schedule or cost?
6. Have I revisited the value definition at this gate/sprint/milestone — or am I still using the same definition from day one?
7. Have I scheduled post-delivery reviews (3, 6, and 12 months) to verify whether planned value has materialized?

CONCLUSION

PMBOK 8 Principle 2 — Focus on Value — transforms how we measure success in projects. Delivering on time and within budget is not enough. What truly matters is the real impact the project generates for stakeholders and for the organization.

The three essential takeaways for practice:

• Value is not a deliverable. Deliverables are the means; value is the end. Measure success by the impact generated — not by the scope completed.
• Value is multidimensional and dynamic. Do not reduce value to ROI. Consider financial, operational, strategic, social, and environmental dimensions — and revisit the value definition continuously.
• Value must be measured before, during, and after the project. Define indicators at initiation, monitor at every milestone, assess post-delivery. Without measurement, focusing on value is just rhetoric.

Next step: Open the Project Charter for your current project. If there is no Value Statement with measurable indicators, schedule a 1-hour session with the sponsor this week to define: “What is the real value this project needs to generate — and how will we measure it?” Document the result and share it with the team.

Free resources to apply now

• → Template: Project Canvas (PMBOK 8) — includes a Value Statement section to map your project’s value on a single page

Did you find this guide helpful? Subscribe to the biweekly newsletter to receive the next articles in the PMBOK 8 series with ready-to-use templates and checklists.

This focus on value covers everything you need to know. See all PMBOK 8 articles in the Complete Index

🇧🇷 Leia este artigo em português

Leia em Portugues: Versao em Portugues deste artigo

Call to Action:

References

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Eighth Edition. Newtown Square, Pennsylvania, USA: Project Management Institute, 2025.

PMBOK Guide 8: The New Era of Value-Based Project Management. Available at: https://projectmanagement.com.br/pmbok-guide-8/

Disclaimer

This article is an independent educational interpretation of the PMBOK® Guide – Eighth Edition, developed for informational purposes by ProjectManagement.com.br. It does not reproduce or redistribute proprietary PMI content. All trademarks, including PMI, PMBOK, and Project Management Institute, are the property of the Project Management Institute, Inc. For access to the complete and official content, purchase the guide from Amazon or download it for free at https://www.pmi.org/standards/pmbok if you are a PMI member.