Project Management Foundations and Value Delivery · Lesson 2

Value, Strategy and Governance

7 min read

Lesson objectives

Distinguish an output, outcome and benefit within a defined case.
Specify a measurable benefit, its assumptions and its accountable owner.
Identify a decision requiring escalation under stated governance authority.

An output is not the benefit

Benefits management identifies, defines, plans, tracks and works toward realizing benefits. Realization may occur after outputs enter use. Delivery success therefore needs to be distinguished from benefits that depend on operations and adoption. This prevents a premature conclusion such as “The platform went live, therefore service improved.”

Write the connection as a testable proposition rather than a guarantee: “If learners use online booking and complete information reaches reception, processing time may fall.” Examine the assumptions before claiming the result. Can users finish the form? Is help available? Does integration actually transfer the data? These are not merely deferred technical details; they are logical conditions for the proposed benefit.

Turn “better” into a defined measure

Counterexample: after launch, the average is 11 minutes, but bookings fall by half during a seasonal break. You can report the observed average for that period, but that information alone cannot establish that the system caused the change. Seek more comparable case mix and demand, and record the limitations. A useful report separates measurement, interpretation and unanswered questions.

Why connect a project with strategy?

The current official overview of the PMBOK Guide, Eighth Edition emphasizes value, tailoring and accountability, including connections between project outcomes and organizational objectives. At this stage, the aim is not to memorize domain names or reproduce the standard. Ask a practical question: Which organizational objective does the project serve, and how would its contribution be recognized?

In the case, the organizational objective may be easier access to training rather than owning another application. That changes the discussion: a simple booking form with clear help may serve the objective better than numerous unused features. A fictional centre in another organization may instead face duplicate appointments. Do not copy the first centre’s solution automatically; examine the different need before transferring the design.

Governance: who can decide?

Governance provides the authority and accountability framework for directing work and controlling outputs, outcomes and benefits. Project management operates within that framework. A weekly report is insufficient if nobody knows who can decide on a significant change or variance. Conversely, every small detail need not go to the highest authority; decision rights should be proportionate to consequences.

Concept	Fictional example	Evidence to seek
Output	An accepted booking system	Test results and documented acceptance criteria
Outcome	The system becomes part of reception practice	Usage records and observed changes in work
Benefit	Less processing time or fewer errors	A suitable comparison and stated inference limits

Delivery performance and investment success are related but different questions. A team can meet time and cost limits while delivering a solution that misses the need. A useful solution can also exceed agreed constraints and require explanation and a decision. Define acceptance criteria, broader success criteria and ownership of each. Not every benefit is financial: in this case usability and access may matter, but the evidence still needs to be specified.

Business justification and the decision gate

A business case explains why the work is worth undertaking by comparing benefits, costs, risks and options; it is not merely a list of deliverables. It is revisited as information matures and at relevant decision points. Here a decision gate means a point where an authorized decision-maker considers evidence before permitting progression. The decision can be to proceed, revise, defer or stop. A gate is not a ceremonial signature and need not involve a large committee for every project.

Case

Fictional worked application: before expansion to three branches, user testing identifies conflicting reception responsibilities, not missing system features, as the immediate obstacle. Assume procedures can be revised and a one-branch trial will not put service at risk; expansion costs remain unresolved. Adding features does not address the obstacle, while postponing all work for extensive data collection delays testing a specific identified cause. Recommend that the sponsor consider revised procedures followed by a one-branch trial before expansion. The sponsor reviews justification, future costs and change authority, and requests trial evidence of adoption and processing time. This recommendation is neither spending authorization nor a benefit guarantee. If a safe trial were impossible or the obstacle unverified, a limited verification delay would be stronger. Past spending alone does not justify new spending.

To avoid conflation, governance sets authority and accountability, management organizes delivery within them, and assurance examines evidence objectively and proportionately to risk to support confidence. A manager’s progress report is not automatically independent assurance, and assurance does not replace decision authority. In the network case the manager assembles test results, a function independent of delivery may examine their sufficiency, and the authorized owner decides. These are project roles, not claims about reviewers of this learning program.

Exercise

Exercise 1 — ten minutes: draft a benefit record for online booking covering need, output, changed use, measure, baseline and target, tracking owner and one potentially blocking assumption. Treat the target as a proposition, not a guarantee. Name two kinds of evidence needed before announcing improvement.

Check your answer

Guided benefit record: the need is less duplicate booking-data entry; the output is an accepted booking system; the required change is reception using its data instead of copying it again. Measure average processing minutes per booking, from staff opening a request to confirming it. The fictional baseline is 18 minutes and the target is 12: a target decrease of 6 minutes, about 33.3%. The reception owner tracks trial results and reports to the sponsor under the case governance. Assumptions are complete data transfer and trained staff. Before claiming improvement, obtain evidence of actual use and a time comparison for similar bookings under comparable demand; downloads alone do not establish benefit. Another target is acceptable with an explicit rationale and measure. These figures are not the network’s observed performance.

Exercise

Exercise 2 — ten minutes: reliable case information suggests that the supplier’s extra service does not reduce waiting but may reduce invoice errors. Write four lines for the sponsor: what changed, the required decision, alternatives, and additional evidence needed. Avoid “We recommend it because it is modern.” You may apply the structure to your work, an organization you know or a fictional example, without personal or confidential data.

Check your answer

Possible response: the proposal serves a different benefit from the original justification; request a decision to keep it outside scope or assess it separately. Alternatives include deferral, a limited trial or an approved change. Evidence on invoice errors and implementation and operating costs is needed. Declining an unsupported addition may protect the project rather than represent failure.

Lesson summary

Delivery alone does not establish a benefit. Link need, output, use and effect, and define the baseline, measure and owner. Governance identifies who decides and on what evidence, including when changed justification warrants modification or closure.