A technique designed to ask what an element is for gets scheduled after the answer has stopped mattering, and then gets judged by how much it removed.
Two documents from the same teaching corpus define value management. The first calls it "the integration of proven and structured problem solving techniques to find the best functional balance between cost, reliability and performance of a product or project", crediting a 1982 source. [SOURCE DETAILS REQUIRED] The second calls it "the process of identifying the required outcome and arriving at the least possible cost".
These are not two phrasings of one idea. The first is a search across three variables in which cost is one term of a balance. The second is a single-variable optimisation with the outcome held fixed. An organisation running the first will sometimes conclude it should spend more; one running the second cannot, because its objective function forbids it.
The interesting question is not which definition is correct. It is how the first becomes the second, and the answer is in the same corpus — in the timetable rather than in the argument.
The Strategic Context
The older document is explicit about timing. Value management, it says, should ideally be implemented "in the very early stages of a project when a commitment has not yet been made", and it explains why: only then can the study clearly identify the expected performance and functions of the thing being built. It concedes that the technique remains effective at any stage of planning or development, which is a real concession and a bounded one — planning and development, not delivery.
The current teaching material places it somewhere else entirely. Value management appears in the implementation phase of the life cycle, in a week concerned with quality assurance and procurement, listed after total quality management as an item that "can be incorporated into the Quality Management Plan".
That relocation is sufficient to produce the change in definition, without anyone deciding to change it. By implementation, function has been fixed — by a business case, a contract, a set of approved drawings, a planning consent. What remains variable is specification: grades, tolerances, finishes, redundancy, spare capacity. A study run at that point can only remove specification, and a study that can only remove specification will, quite reasonably, be defined as a method for arriving at the least possible cost. The definition follows the timetable.
The Distinction the Timetable Destroys
The question a value study exists to ask is not "what does this cost?" It is "what is this element for?" — and the two questions have different answers only while the design can still change.
The structure of the standardised methods makes this visible. The older document lists three job plans, credited to international value associations. [SOURCE DETAILS REQUIRED] The traditional five-phase sequence runs information, creative, judgment, development, recommendation. A six-phase sequence credited to the American Society for Testing and Materials inserts function analysis immediately after information. A seven-phase sequence credited to the Association Française de Normalisation goes further: preparation, needs analysis, function analysis, cost analysis, solution analysis, result implementation, and — alone among the three — follow-up of implementation.
Two structural observations follow, and neither is available from any single method.
The longer sequences do not simply add steps; they add the step that changes what the study is capable of finding. Without an explicit function analysis, a study starts from the elements that exist and asks what each costs. With one, it starts from the functions required and asks what could deliver them. The first can only subtract. The second can substitute, combine, or delete a function nobody can justify.
And only one of the three closes the loop. Two of these methods end at a recommendation or a presentation, which means the discipline's own most common failure — a well-argued study whose recommendations were never implemented — is outside the scope of the method as defined.
The same document offers a sufficiency test rather than a definition: "As long as the value, function, multi-disciplinary team and job plan concepts are present it is value management." Four conditions, and a helpfully unpossessive attitude to the label — a 1995 practitioner is quoted saying that it does not matter whether you call it value management as long as you apply the principles. [SOURCE DETAILS REQUIRED] Read the four conditions against a typical implementation-phase cost review and at least two are usually absent: there is no function step, and the team is drawn from delivery rather than across disciplines.
The Word Doing the Damage
"Value for money" appears three times in this corpus with three different referents.
In the value management material it means the customer's cost outcome. In the procurement material it means the non-price terms of a contract — warranties, payment terms, liquidated damages, reporting access — with price as the starting point rather than the object. And in a third source, a practitioner writing on quality observes that discussions of the subject collide two themes, "perfection" and "value for the money", with technically minded people equating quality with workmanship. [SOURCE DETAILS REQUIRED]
Three meanings: cost minimised, terms secured, and sufficiency against a purpose. A leadership team that has not said which one it means has not set a criterion, and the ambiguity is not neutral. Whichever meaning is cheapest to measure will win by default, and that is always the first. [Related article: The Terms You Cannot Buy Back]
Value Engineering, and the Honest Complication
The older document also describes value engineering, and it is worth confronting because it appears at first to contradict the argument. Value engineering, it says, is a specific application of the value management process aimed at generating a large number of small and simple ideas to improve the initial engineering design, reduce cost, and allow a benefit-to-cost ratio to be developed. That is cost language.
But look at what it is for. The ratio it produces is used "to assist in deciding whether the project will proceed" — this is an input to the investment decision, not a saving extracted after it. The document requires, before the process starts, a description of the problem, the required outcomes, the options considered, a description of the preferred option, an initial scope and a preliminary estimate. And it claims benefits beyond the saving: increased knowledge of the project, and the avoidance of scope misconceptions.
So value engineering is the cost-facing application, deliberately run early enough to change a go decision. It is not a counter-example. It is the same argument in a narrower frame: the cost question is legitimate and productive precisely while the answer can still alter what gets built. Move it downstream and it becomes a negotiation about finishes. [Related article: The Front End Owns the Outcome]
What Kills the Study Before It Starts
There is a second failure mode, and the older document treats it with more seriousness than most management literature manages. It lists twenty-five statements it calls "idea killers" and instructs that they "should not be a part of the value management thinking process". They are the ordinary furniture of a meeting — the observation that something has worked for twenty-five years is a representative example — and every one of them ends analysis without producing evidence.
The temptation is to read this as a comment on culture. It is more useful read as a comment on screening. An enterprise's real improvement capacity is bounded by which objections are permitted to close a conversation, and that boundary is a design choice, not a personality trait. The same corpus lists "eliminating fear" as a strategy for continuous improvement without saying how. This is how: by naming, in advance, the class of statement that may not end an option's consideration, and by giving the session's chair the standing to enforce it.
The document also directs where the effort should go, invoking a proportionality claim — that 20 per cent of the functions or elements of a problem hold 80 per cent of the resource expenditure, so concentrating on the remaining 80 per cent wastes the study. [FACT CHECK REQUIRED] Whatever the ratio, the instruction is rarely followed: studies spend their creative energy on the elements easiest to discuss rather than the ones carrying the money.
The Same Question in Two Buildings
A municipal wastewater treatment upgrade, hypothetically, is approved on a design that includes a covered inlet works. Asked late, during delivery, the only available question is whether the cover can be a cheaper material. Asked early, with the operator and the environmental regulator present, the question becomes what the cover is for — odour containment for a residential boundary four hundred metres away — and whether that function could be delivered by dosing, by a shorter cover over the screens alone, or by a planting buffer. Three of those options change the capital cost by more than any specification decision available later, and two of them change the operating cost as well.
A university campus building, hypothetically, carries a large atrium. During delivery, the atrium's cost is a glazing specification. Before commitment, it is a question about what the atrium does — circulation, informal teaching space, a recruitment asset for open days — and about which of those functions the faculty paying for the building actually requires. Nobody asks, because by the time cost becomes urgent the atrium is in the planning approval.
Decision Framework
The function–cost map. For the largest cost elements of a proposed investment — enough to cover the majority of the estimate — four columns: the function the element performs, who requires that function and why, what it costs, and what else could perform it.
The first column is the one that does the work, and it has a discipline: state the function without naming the element. "Provide a barrier between the plant and the public road" is a function. "The fence" is not. Elements that cannot be described this way are usually inherited rather than required, and inherited elements are where the money is.
The fourth column is where a multi-disciplinary team earns its cost. A single-discipline group will populate it with variants of the same solution.
The expiry date. Record on the investment paper the date after which a value study can no longer change function — normally the point at which design is frozen or the contract is let. After that date the study is a specification review, and it should be called one. This single line prevents the most common institutional deception in this area, which is running a cost exercise late and reporting it as value management.
Three tests read the map.
The function test. Can we state what this element is for without naming the element?
The whose-requirement test. Is the party who requires the function in the room? A function nobody present will claim is a function nobody has justified.
The expiry test. What is the last date on which the answer could still change the design — and is the study scheduled before it?
From Strategy to Execution
Immediate. For the next major investment reaching the approval path, put the expiry date on the paper. Nothing else. It costs nothing and it forces a conversation about sequence that is otherwise never held.
Medium-term. Move the value study to the point at which the options are still open and the preferred option is described but not committed — the position the older document specifies. Staff it across disciplines, including at least one party who will operate the result and one who has no stake in the preferred option. Then decide what the study is permitted to recommend: a study allowed only to reduce is a cost review with a better name, and the organisation will learn that within one cycle.
Long-term. Settle, as a matter of policy, which meaning of "value for money" governs an investment decision, and write it into the approval criteria. This is unglamorous and it removes an ambiguity that currently lets three different arguments be made in the same room without anyone noticing they are different. [Related article: What Does "Critical" Actually Commit You To?]
Signals to Monitor
- Whether any value study in the past two years recommended spending more on anything. A portfolio of studies that only ever subtracts has a single-variable objective, whatever its terms of reference say.
- The interval between the value study and the design freeze. Where it is negative, the study is a specification review.
- Whether studies are staffed across disciplines or from the delivery team.
- Whether recommendations are tracked to implementation — the step two of the three standard methods omit.
- Recurring late-stage disputes about what a facility was supposed to do, which indicate the function question was never asked.
- Whether the elements consuming most of the estimate are the ones the study spent most of its time on.
Questions for the Leadership Team
- For our last major investment, can we state the function of its three largest cost elements without naming the elements?
- When did our last value study run relative to design freeze — and was it capable of changing anything but specification?
- Has any value study of ours ever recommended an increase, and what happened to that recommendation?
- Which meaning of "value for money" do our approval criteria actually use?
- Who in our organisation is empowered to stop an objection from ending a conversation, and do they use it?
- Of the recommendations from our last three studies, how many were implemented, and who checked?
Closing Perspective
The reduction of value to cost is not an intellectual error that better training would correct. It is what happens when a technique built to interrogate purpose is scheduled after purpose has been settled, and then judged by the only variable left to it.
The remedy is a matter of sequence rather than of method. Ask what an element is for while the answer can still change what gets built, staff the question across the disciplines that have to live with the result, and put a date on the paper after which the question is closed. An organisation that does that will still make expensive mistakes. It will make fewer of the specific mistake of building precisely the wrong thing, efficiently. [Related article: From Producer to Orchestrator] [Related article: How Does Work Get Into Your Enterprise Without a Decision?] [Related article: The Clock Starts Before the Project Does] [Related article: Quality Assurance Cannot Tell You the Specification Was Wrong]
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.