Budget, Value, and Benefits (VAL)

Most projects are judged on cost and delivery timeline; almost none on the value achieved afterward. A project delivered on budget that no one uses is an invisible failure…

Guide≈ 6 min readCheckedReading

On this page

Why this theme
What this theme measures
The five levels
Milestones by level
Detailed reading by level
Partial achievement and rating
Move to the next level
See also

Level: 🟢→🔴 · Code: VAL · Matrix: PI

Why this theme#

Most projects are judged on cost and delivery timeline; almost none on the value achieved afterward. A project delivered on budget that no one uses is an invisible failure. This theme reconciles three questions often handled separately: how much it costs (build and operations), what it returns, and whether we really know afterward. The cost of ignoring it: funding projects with no return, underestimated operating costs (licenses, cloud capacity, maintenance), inability to make trade-offs.

What this theme measures#

Axis: from cost discovered at the end to investment steered by actual return.
Key indicator: planned/actual budget variance and planned/actual benefit variance; total cost of ownership (build + operations).
Unit: % cost variance; % of realized benefits vs announced; annual operating cost per user or per report.

The five levels#

Level	Short name	Promise	Typical indicator (orders of magnitude)
1	Cost discovered	Cost is known at the end, when the bill or time spent arrives.	Cost variance: ± 50% or more; no measured benefits
2	Initial budget	An initial budget exists; we approximately know what was spent.	Variance: ± 30%; monthly tracking
3	Tracked budget, declared value	The budget is tracked by line item, expected value is written and tied to scoping; operating costs are estimated.	Variance: ± 15%; declared value for 100% of projects
4	Measured value	Benefits are measured after delivery against criteria defined during scoping; total cost of ownership is tracked.	Cost variance ± 10%; benefits measured on ≥ 70% of projects
5	Steered investment	Investment decisions rely on observed return; resources are reallocated to what delivers, what does not deliver is stopped, and the cost of value is optimized.	Realized benefits ≥ 80% of planned, or variance explained; documented reallocations

Milestones by level#

ID	Milestone	Verifiable evidence
PI-VAL-1.1	Time spent per project is approximately known.	Timesheet or team estimate.
PI-VAL-1.2	External spending (licenses, services) is inventoried.	Project purchase list.
PI-VAL-1.3	A manager approves expenses.	Name of approver.
PI-VAL-2.1	An initial budget (internal effort, purchases, foreseeable operations) is written at kickoff.	Dated budget document.
PI-VAL-2.2	Actual spending is compared with the budget at least quarterly.	Budget/actual table.
PI-VAL-2.3	Significant variances are reported to the sponsor.	Messages or meeting minutes.
PI-VAL-3.1	The budget is broken down by line item (team, licenses, infrastructure, training, operations).	Line-item table.
PI-VAL-3.2	Expected value (gains, cost avoidance, reduced risks) is written with its assumptions, tied to scoping success criteria.	Value sheet linked to CAD.
PI-VAL-3.3	Recurring costs (cloud capacity, per-user licenses, maintenance, support) are estimated before go-live.	Annual operations estimate.
PI-VAL-3.4	Budget changes go through a tracked decision.	Budget decision log.
PI-VAL-3.5	The budget includes a risk reserve (see RSK).	Reserve line and usage rule.
PI-VAL-4.1	Benefits are measured 3 to 12 months after delivery against defined criteria.	Benefits report for ≥ 70% of projects.
PI-VAL-4.2	Total cost of ownership (build + operations) is tracked by product.	Per-product table over ≥ 12 months.
PI-VAL-4.3	Planned/actual variances (cost, value) are analyzed and fed back into subsequent estimates.	Annual analysis; calibration of future business cases.
PI-VAL-4.4	Actual usage (active users, viewed reports) is reconciled with cost.	Cost per active user.
PI-VAL-5.1	Resources are reallocated from low-return products to higher-return ones.	At least one documented reallocation per year.
PI-VAL-5.2	End-of-life products are formally retired to free up their cost.	Retirement decisions and observed savings.
PI-VAL-5.3	The cost of value is optimized (capacity sized to usage, licenses adjusted).	Periodic sizing review.
PI-VAL-5.4	Measured benefits are independently audited (finance or management control).	Countersignature by a third-party function.

Detailed reading by level#

Level 1. Signs: “How much did it cost?” remains without a precise answer; no one has looked at what the project returns. Gain: no administrative overhead. Does not guarantee viability. Difficulty: 1/5. Effort: 1/5.

Level 2. Signs: a written budget, a quarterly comparison. Gain: no more invisible overruns. Does not guarantee operating cost or value. Difficulty: 2/5. Effort: 1/5.

Level 3. Signs: no project is launched without knowing what it will cost to operate; expected value has a number. Gain: more honest decisions, fewer recurring-cost surprises. Does not guarantee that value will materialize. Difficulty: 3/5. Effort: 3/5.

Level 4. Signs: benefit reports, cost per active user, calibration. Gain: we know which projects worked. Does not guarantee that measurements are neutral (attribution is difficult). Difficulty: 4/5. Effort: 4/5.

Level 5. Signs: reallocations, retirements, adjusted sizing, external audit. Gain: investment guided by results. Does not guarantee strategic vision. Difficulty: 5/5. Effort: 5/5. A full 5 assumes mature management control, rare for small teams.

Partial achievement and rating#

Common rule: see README.

0.5: value declared for large projects only; benefits measured once, on one project.
1: three randomly selected projects show their budget, expected value, and tracking.
A partial 5: operating cost per product tracked, benefits measured on most projects, one product retirement decided; no independent audit. Score ≈ 4.5.

🧪 Example

A set of 60 Power BI reports uses cloud capacity sized for end-of-month peak. Annual capacity cost divided by number of active users: €1,200 per user (fictional figure). After retiring 12 rarely viewed reports and adjusting off-peak capacity, cost drops to €800 per user. See Cost, Licensing, and Capacity (BI) and Cost and Value Management (Data FinOps).

⚠️ Pitfall

Phantom benefits. Symptom: the business case announces productivity gains that no budget reflects. Cause: benefits expressed as “freed-up time” never converted into decisions. Remedy: tie each benefit to an observable indicator and to an owner who commits to it.

⚠️ Pitfall

Goodhart's law: if zero budget variance is rewarded, teams overestimate upfront (hidden buffer) or shift costs to the operations budget. Track total cost of ownership, not just project cost.

✅ Good practice

Write the annual operating cost during scoping; it is the most underestimated line item in reporting and data platform projects.

Move to the next level#

Possible means (optional)

1 → 2: simple time entry, one-page initial budget.
2 → 3: line-item budget, value sheet linked to scoping criteria, operations estimate; see Project Management Fundamentals and Project Planning and Tracking Tools: Overview.
3 → 4: benefit review at 3 and 12 months, cost-by-product table, reconciliation with usage; Project Metrics and Reporting.
4 → 5: investment committee, formal product retirement, audit by management control; see Choosing and Hybridizing Methods.

🤖 AI

Can help build a cost model, reconcile usage logs and costs, and spot underused resources; it cannot certify a benefit, nor decide in your place what counts as value. See AI for Project Management (General, Then Data).