Project Deliverables vs. Outcomes: Value Enablement Focus

PMBOK v8 Definition

A project's output (deliverable) does not automatically enable the intended outcome or value. For example, software is the output of a project, but it does not enable productivity by itself. Adding a new deliverable, such as training in the use of the software, can enable a higher-value outcome. If the project’s output fails to enable the desired productivity, then the value proposition of the project is undermined and may even become more harmful than helpful, given the investment in time and resources. Therefore, project teams, stakeholders, and team members should understand both the deliverable and the intended outcome from the deliverable.

Why It Matters for the Exam

This concept appears frequently in situational questions where the PMI exam tests your ability to distinguish between simply producing a deliverable and actually achieving the intended business outcome. You will see this in questions about project justification, value delivery, and stakeholder satisfaction—often disguised as "what should the project manager do next?" scenarios.

Key Points to Remember (for the Exam)

Core Distinction: Deliverables are outputs; outcomes are the intended business results those outputs must enable.
Value Risk: If the deliverable fails to enable the intended outcome, the entire value proposition is undermined—the project may become harmful rather than helpful.
Team Responsibility: Project teams, stakeholders, and especially team members must understand both the deliverable AND the intended outcome.
Outcome Focus: Shifting focus from deliverables to intended outcomes allows project teams to deliver on the project’s vision or purpose, rather than merely creating a specific deliverable.
Complementary Deliverables: Adding a new deliverable (e.g., training) can enable a higher-value outcome when the primary deliverable alone is insufficient.
Value Chain: Outcomes create benefits (positive effects) or disbenefits (negative consequences); benefits create value, which must meet or exceed target thresholds to justify the investment.
Long-Term Perspective: A reliable evaluation of value should consider the entire context and life cycle of the project as well as its expected payback period, which may extend well beyond project closeout.

Typical PMI Exam Example

A company implements new accounting software to improve processing speed. After deployment, processing speed does not improve. The project manager discovers that staff do not know how to use the advanced features. What should the project manager have done?

Answer: Ensured the project included training as a complementary deliverable to enable the intended outcome of higher productivity.

PMI Exam Traps

Trap: Confusing "project success" with "deliverable completion" Reality: Success is measured by whether the intended outcome is achieved, not just whether the deliverable is produced.
Trap: Assuming the deliverable alone creates value Reality: The deliverable does not enable productivity by itself; complementary deliverables may be needed to achieve the outcome.
Trap: Focusing only on short-term project metrics Reality: Value evaluation must consider the entire life cycle and payback period, which may extend well beyond project closeout.
Trap: Thinking outcomes and benefits are the same Reality: Outcomes create benefits (positive) or disbenefits (negative); benefits then create value.

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Value Delivery System	Complements	Information and feedback must be shared consistently among all components to keep the system aligned with strategy and attuned to the environment
Project Justification	Input to	Expected value (financial or nonfinancial) must meet or exceed target thresholds to justify the investment
Business Case	Supports	The value proposition is undermined if the deliverable fails to enable the intended outcome
Portfolio Management	Output to	Provides key data for decisions on which projects to select or continue based on their value contribution

Quick Review Questions

A project delivers a new CRM system on time and on budget, but sales productivity does not increase. According to PMBOK v8, what is the primary issue?
What is the difference between a project's deliverable and its intended outcome?
When should a project team consider adding complementary deliverables beyond the primary output?
How does a project's value proposition become undermined according to PMBOK v8?
Why must value evaluation consider the entire life cycle and payback period of a project?

PMBOK v8 Reference

Section 3.4.1 - Project Impact (Shift from deliverables to intended outcomes)