Value engineering isn’t cost cutting

Reviewing cost charts and figures at a desk

If your value study started with “where can we cut?”, it started in the wrong place.

One of the biggest challenges in my work has always been awareness. Many people in the industry understand value engineering as a set of ideas generated to reduce cost. A project goes over budget, someone calls for “VE”, and a group of people sit down to find things to remove or make cheaper.

That is cost cutting. It has its place. But it is not value engineering, and the difference matters more than most organisations realise.

How cost cutting thinks

Cost cutting starts with the bill. It looks for the biggest numbers and asks how to make them smaller. Use a cheaper material. Remove a feature. Negotiate harder with the supplier. Push the price down.

This feels logical, and sometimes it works. But it has two weaknesses.

First, it treats every rupee the same. A cost that delivers essential performance gets squeezed just as hard as a cost that delivers very little. Second, it often moves cost rather than removing it. A cheaper part that fails more often shows up later as warranty claims, downtime or rework. The saving on paper becomes a cost somewhere else.

How value engineering thinks

Value engineering starts somewhere else entirely. It does not ask “what does this cost?” first. It asks “what does this need to do?”

That question is the heart of function analysis. Every part of a product, building or process exists to perform a function. A casing contains fluid and resists pressure. A coating protects against corrosion. Packaging protects the product in transit. Once those functions are named, the team can ask two useful questions about each one:

  • What are we spending on this function today?
  • What is the least it could cost to perform this function reliably?

The gap between those two numbers shows where the real opportunity lies. And very often, it is not where anyone expected.

An example

Take a cast metal housing that holds fluid under pressure, costing ₹4,800 a unit and made in large volumes. Material and machining costs are rising, and customers want a lower price. The instinctive move is to attack the biggest line on the bill: the casing itself. Make the wall thinner. Find a cheaper foundry. Try a lighter material.

Now look at it by function. The casing’s main jobs are to contain fluid and resist pressure, and those jobs genuinely need most of what is being spent on them. Make the wall thinner, and it no longer meets the pressure rating. Switch to a cheaper material, and it may not survive the temperature. The biggest cost line turns out to be one of the better-value parts of the design.

The real gaps sit in places that looked minor: protecting against corrosion, and protecting the unit in transit. A three-coat paint system and single-use packaging were costing two to three times what those functions were worth. A single powder coat and returnable crates deliver the same protection for far less.

Cost cutting would have squeezed the casing and weakened the product. Function thinking left the casing alone and found the savings where they actually were.

Value means performance, not just price

This is why value engineering follows a structured approach, the Job Plan, rather than a brainstorm. Value is the relationship between what something does and what it costs. You can improve it by lowering cost, by improving performance, or both. Cost cutting only ever looks at one side of that relationship.

It is also why a good study brings different people into the room. The engineer knows what a function really requires. Procurement knows what the market can supply. Operations knows what fails in practice. No single department can see the whole picture, and no single department should decide alone where the cost goes.

When a project calls for “VE”

The next time a project is over budget and someone suggests value engineering, it is worth asking what is really being requested. If the brief is simply to cut 10%, the team will look for the easiest numbers to reduce. If the brief is to deliver the required functions at the best value, the team will look in very different places, and usually find more.

Value engineering, done properly, is not about spending less. It is about spending well.

If your project needs a fresh look at where its cost really sits, talk to us about a value study.