Focus on Value: The Principle Behind Better Trade-offs

Most project managers accept without argument that a project exists to create value. The difficulty shows up when a real trade-off arrives. Funding tightens, a supplier slips six weeks, a regulator moves a date, and within minutes the conversation is entirely about the constraint. Value appears later, in the paper explaining why the decision was sensible. Used that way it settles nothing, because a value statement broad enough to justify one option is almost always broad enough to justify the opposite one.

Focusing on value in practice means something narrower and considerably more useful. It means holding an answer specific enough to three questions, what this work is meant to change, for whom, and how anyone would know it had happened, that the answer can actually choose between two options when something has to give. That is the working skill. Everything else is maintenance of it.

Value only becomes usable when it is specific

A value statement that cannot rule anything out cannot help you decide anything. "Improve the customer experience" survives every possible outcome, including doing nothing. "Reduce the number of repeat visits an engineer has to make to the same fault, because a second visit is what tenants complain about" rules things out immediately. It tells you which part of the scope carries the change and which part is supporting work.

Three habits make the difference. The first is naming the change rather than the deliverable. A new scheduling system is an output; engineers arriving with the right part is the outcome; fewer repeat visits and lower overtime cost are the benefits that follow. Collapsing those into one word is how a project ends up defending a delivery it can no longer justify. The second habit is naming who receives the change, because value is rarely uniform. The finance director, the operations manager and the person waiting at home are not agreeing to the same thing when they agree the project is worthwhile. The third is agreeing, early, what observation would count as evidence, even when it is rough. A number you agreed in advance and half trust is worth more in a trade-off than a perfect measure designed after the argument has started.

This is the substance of the Focus on Value principle described in Section 3.4 of The Standard for Project Management, which treats value as a continuing test of whether the work remains worth doing rather than a statement made once at approval. The principle is not asking for more benefits paperwork. It is asking whether anyone on the project could answer the three questions today without going to look for a document.

The trade-off is where the principle is tested

When the pressure lands, the instinct is to protect what is easiest to defend: the baseline, the contract, the thing already half built. A value-led response reverses the order. Re-establish what the work is meant to change, then ask which of the available options still produces it, then look at cost, schedule and commitments as the constraints on that choice rather than the choice itself.

Consider a maintenance programme replacing an ageing job-scheduling system. Phase one, back-office reporting, is nearly finished and running slightly over. Phase two, the mobile application that puts job history and parts availability in the engineer's hand, has not started. A cut is required. The easy cut is phase two, because nothing is sunk in it and nobody has to admit that finished work was wasted. Yet almost all of the intended change sits there. Better reports let the organisation see the repeat visits more clearly; only the mobile work reduces them. The value-led option is uncomfortable: stop refining phase one at the point where it is good enough to be useful, and protect the slice that carries the outcome.

The mirror image is equally common, and worth guarding against. Sometimes the value answer really is to stop. Three units of a six-unit replacement have delivered most of the available reliability improvement, conditions have changed, and completing the plan would buy very little. Money already committed is not an argument for spending more, and neither is the tidiness of a fully closed baseline. A useful discipline here is to ask what you would choose if the work in front of you were being proposed today, at today's remaining cost, with today's information. If you would not start it, continuing needs a reason beyond momentum.

Two cautions keep this honest. Focusing on value is not the same as choosing the cheapest option, and it is not the same as giving the loudest stakeholder what they asked for. It is also not a licence to bypass agreed change control. A value argument tells you what to recommend; the governance route tells you how the change gets decided and by whom.

Keeping the question answerable

Most of the tailoring work sits here, because a principle you cannot answer under pressure is decoration. Three adjustments do most of the lifting on a live project.

Put the value question inside a rhythm you already have. A monthly steering meeting, an iteration review, a phase gate or a supplier review can each carry one standing question: is the change we described still the change we expect, and is the remaining work still the best way to get it? Inventing a separate value forum tends to produce a well-attended meeting nobody acts on.

Tailor the artefacts around the decision rather than the template. If the benefits measure lives in a document nobody opens between gates, move the two figures that matter onto the report people actually read. If the backlog is ordered by who asked first, reorder it by the change each item produces and record why. Where scope is baselined, make sure the change assessment includes an effect-on-value line, not only cost and schedule impact. None of this is extra machinery. It is the same machinery pointed at a different question.

Finally, keep the ownership question visible. Delivery usually ends before the change matures, so someone in operations, product or the business needs to hold the benefit afterwards. Naming that person early changes how the trade-off conversation goes, because there is somebody in the room whose interest is the outcome rather than the delivery.

For a PMP® candidate, this principle shows up as applied judgement rather than recall. The current Examination Content Outline includes a Process domain task on helping ensure value-based delivery, with enablers covering identifying value components with stakeholders, prioritising work by value and feedback, examining business value throughout the project and verifying that a benefits measurement system exists. Scenario questions in that territory tend to reward the response that re-establishes what the work is for before choosing an action, and to penalise responses that defend a plan or escalate reflexively. Practising the reasoning against situations other than your own, which is a large part of what structured PMP® Exam Preparation provides, is usually what exposes the trade-off habits you did not know you had.

On a real project, the payoff is quieter than the principle sounds. You spend less time arguing about constraints in the abstract, you can explain a recommendation to a sponsor in one sentence, and you stop being the person who delivered exactly what was agreed to an organisation that no longer needed it. The projects that go wrong on value rarely fail loudly. They finish, on time, and change nothing.

Andre Malowney

Interested in going further?

Trade-off decisions are where value thinking either works or quietly disappears, and they are difficult to practise alone because your own projects only offer a handful of them a year. Structured preparation puts a much wider range of situations in front of you and makes you commit to an answer.

The Focus on Value principle and its place among the other five is set out in the PMBOK® Guide Eighth Edition alongside The Standard for Project Management.

Ad · Amazon affiliate link.

References

A203: How to Handle Competing Constraints in a PMP Scenario
A014: Intended Value vs Realised Value
A013: Value Delivery in Project Management: What It Means in Practice
A005: PMBOK 8 Focus Areas vs Process Groups: What Changed?
A012: Outputs, Outcomes, Benefits and Value: What's the Difference?

PMP and PMBOK are registered marks of the Project Management Institute, Inc.