What value means and why it is not cost cutting

Value is a relationship, not a price

People often use "value" to mean "cheap" or "good". In value methodology the word has a narrower and more useful meaning. Value expresses how well something performs the functions it is needed for, relative to the resources it consumes to do so. Resources include money, but also time, energy, materials, space, staff effort and risk.

A useful shorthand is: value rises when required function and performance improve, when the resources needed fall, or both. SAVE International's public description of the Value Methodology frames value in a similar way, as the relationship between function and the resources used to achieve it. The shorthand is not a formula you calculate to two decimal places. It is a way of thinking that forces two questions onto the table at the same time: what must this do, and what does it take to do it?

The second question is the familiar one. Most organizations already measure cost. The first question is where value work earns its place. If a team cannot say clearly what a subject must do, it cannot tell whether a cheaper design is a better design or simply a weaker one.

Where the methodology came from and what it is today

Value analysis grew out of manufacturing purchasing work in the 1940s, most often associated with Lawrence D. Miles at General Electric. Material shortages forced buyers to find substitutes, and they noticed that many substitutes performed the required function just as well, sometimes better, at lower cost. The insight was that the function, not the part, is what the customer needs.

Since then the approach has spread to construction, public infrastructure, product design, services, software and organizational processes. Names vary: value analysis, value engineering, value management and value methodology are used in different sectors and countries, sometimes with slightly different emphasis. In this course we use "value methodology" for the overall discipline and "value study" for a single structured application of it.

A value study is a structured, team-based review that follows a defined sequence of phases, often called the Job Plan. It is led by a facilitator, involves people from several disciplines, and centres on function analysis. Those three features, the structured sequence, the multidisciplinary team and the focus on function, are what separate a value study from an ordinary design review or a budget exercise.

Value improvement versus cost cutting

Cost cutting asks: what can we remove or cheapen to hit a lower number? It usually starts from the budget and works backwards. It can be necessary, and sometimes it is the right call, but it carries a specific danger: it can quietly remove a function someone needs, or lower performance below an acceptable level, without anyone recording that decision.

Value improvement asks a different question: what must this achieve, and is there a better way to achieve it? It starts from function and performance. Savings are a frequent result, but they are a result of a better way of performing the required functions, not the starting point.

Three tests help you tell the two apart:

• Function test. After the change, are all required functions still performed? If a required function disappears, the change is not a value improvement, however much money it saves.
• Performance test. Does performance stay at or above the level stakeholders genuinely require? Performance that falls below a mandatory level is a loss, not a saving.
• Whole-life test. Does the change reduce total resources over the life of the subject, or does it simply move cost from the capital budget into operation, maintenance or risk?

A change that passes all three is a value improvement. A change that saves money but fails one of the tests is cost cutting, and a change that fails the function test on a required, safety or mandatory function is unacceptable in ValueLens practice.

Ways value can improve

It helps to recognise the different patterns value improvement can take, because teams that only look for savings miss half of them:

• Same function and performance, fewer resources. This is the classic pattern: a simpler detail, a standard component, a less wasteful process step.
• Better function or performance, same resources. For example, a layout change that improves maintenance access at no extra cost.
• Much better performance for a modest increase in resources. Value can rise even when cost rises, if the improvement in required performance is larger. A slightly more expensive pump that uses far less energy can be better value over its life.
• Removal of unnecessary functions. Some features exist because of habit, an outdated standard or a preference no one has tested. Removing what nobody needs is a genuine value improvement, provided you have checked that it really is unneeded.

Notice that only the first pattern looks like "saving money" on the capital budget. Good practitioners keep all four in mind and report results honestly in terms of function, performance and resources, not only cost.

Required performance is the floor, not a negotiating position

Every subject has some performance that is not open to trade. Safety requirements, legal and regulatory obligations, security, contractual commitments and the basic purpose of the subject belong here. In ValueLens these are treated as a floor. Alternatives that fall below the floor are screened out, not scored lower.

This matters because scoring can hide losses. If a cheaper option scores badly on safety but very well on cost, a weighted total might still rank it first. Treating mandatory performance as a screen, before any scoring, prevents that. Later modules teach weighted evaluation in detail; the principle you need now is that mandatory performance is checked first and separately.

There is a limitation to remember. Teams sometimes label preferences as requirements to protect them from challenge. Part of the value practitioner's job, covered in module 3, is to ask where each requirement comes from. A real requirement survives that question. A preference dressed as a requirement may not, and challenging it respectfully is one of the main sources of value.

Judgment and limits of the method

Value methodology is a disciplined way of thinking, not a machine that produces answers. Its results depend on the quality of information, the right people in the room, honest facilitation and decision makers who actually act on the recommendations. A study held too late, with poor data or with a team that has no authority to change the design, will produce little.

It also does not replace engineering, legal or safety judgment. When a value alternative touches a technical standard, a qualified professional must confirm it. The study identifies and develops opportunities; it does not give the team licence to override competent specialists.

Finally, be careful with the word "savings". A proposed saving is an estimate made under uncertainty. A realized saving is what is actually achieved after implementation. Throughout this course you will be asked to keep those two clearly separated.