Amin Terouhid, Ph.D., CVS
Executive Takeaway: Industry practitioners sometimes mischaracterize Value Engineering (VE) as an aggressive, late-stage cost-cutting tool deployed only when a project faces budget overruns. In practice, treating VE as an exercise in price-slashing degrades the actual value that VE exercises provide and the main purposes it serves. VE is a function-oriented methodology used by a multidisciplinary team aimed at improving the value of a project, product, process, service or organization [1]. Correcting these misconceptions is essential for those who seek to maximize returns on their investments and enhance the value of their projects, products, processes, services, or organization.
Key Misconceptions
- Misconception: “Value Engineering Is Just a Fancy Term for Cost-Cutting”
When a capital project exceeds its baseline estimate, project managers often announce a “Value Engineering phase.” In practice, this phase usually degenerates into a reactive exercise where designers, contractors, and owners meet to slash line items, eliminate scope, or downgrade finish standards to meet an immediate budget cap. Because these budget-clearing drills are labeled as “VE,” industry professionals have come to assume that value engineering is simply a euphemism for cheapening a design.
Value Engineering, however, as established by international standards bodies such as SAVE International, does not begin with a dollar target; it begins with an analysis of Function [1]. Function analysis forces project teams to strip away specific physical solutions and ask fundamental questions: What must this asset or system actually do?
Traditional cost-cutting focuses strictly on reducing upfront capital expenditures (CapEx) by removing components. VE, by contrast, identifies alternative, often innovative ways to fulfill the required function at equal or superior performance levels.
When a team simply removes scope or specifies inferior materials without re-evaluating the underlying function, they are not performing VE. Instead, they are executing an unvetted scope concession that often compromises the project’s core intent.
- Misconception: “VE Inherently Compromises Project Quality”
Designers, architects, and end-users sometimes resist VE proposals because they operate under the assumption that “value” is a code word for compromise. Such a narrative suggests that any modification proposed during a VE workshop will inevitably result in a second-tier facility: thinner walls, less reliable equipment, degraded architectural aesthetics, or shortened asset service life. This misconception stems from a fundamental misunderstanding of the mathematical definition of Value, which is performance achieved based on the resources used. In a formal value study, value is defined as the quotient of functional performance divided by resource expenditure. This formulation underscores how effectively a design transforms invested assets into results. As such, value can be enhanced in several ways that have nothing to do with sacrificing quality. Examples include:
- Increasing Performance while holding Resources constant: Introducing higher-efficiency equipment or a more flexible layout for the same capital investment.
- Maintaining Performance while reducing Resources: Fulfilling the exact technical and operational requirements through an alternative layout or modular construction technique that requires less material and labor.
- Significantly increasing Performance with a minor increase in Resources: Investing slightly more capital upfront to eliminate a chronic operational bottleneck, which yields significant long-term reliability gains.
VE actively protects baseline performance standards. For example, if an alternative proposal reduces safety margins, degrades required capacity, or accelerates material failure rates, it fails the fundamental test of functional equivalence.
- Misconception: “Value Engineering Is a Late-Stage Emergency Intervention”
On some capital programs, VE is treated as an emergency brake, a process invoked only at 90% design completion or after construction bids come in significantly over budget. The team rushes through a high-pressure workshop to identify immediate design rollbacks so the project can move forward to award or groundbreaking.
Treating VE as a late-stage rescue mechanism severely diminishes its effectiveness. The ability to influence total project value follows an exponential decay curve across the project lifecycle, while the cost of implementing changes increases dramatically over time. Therefore, when VE is delayed until the end of design:
- Redesign Costs Multiply: Architectural and engineering revisions require extensive rework of calculated drawings, calculations, and specification packages, which erodes the net financial gains of proposed changes.
- Schedule Delays Cascade: Re-evaluating major systems late in the design phase may cause disruptions.
To capture maximum strategic value, owners must deploy Value Engineering during the conceptual and schematic phases—when fundamental decisions regarding footprint, structural framing, system selection, and spatial relationships are still fluid.
- Misconception: “VE Focuses Purely on Initial Construction Costs (CapEx)”
Financial management on capital projects is often structured in silos: the project management team is evaluated solely on delivering the asset within the initial construction budget (CapEx), while the facility operations team inherits the ongoing operational costs (OpEx). Because of this split, VE workshops frequently fall into the trap of evaluating alternatives based exclusively on upfront installation prices.
Evaluating capital decisions solely on initial contract pricing creates a distorted picture of asset economics. A lower upfront purchase price frequently conceals costs such as higher energy consumption, complex maintenance requirements, or expensive replacement parts. It is important to note, however, that VE evaluates proposals through the lens of Total Cost of Ownership (TCO) by assessing complete asset lifecycles and factoring in the time value of money.
- Misconception: “The Design Team Can Facilitate Its Own VE Process”
Project owners looking to streamline administrative overhead often ask their primary design firm to lead the internal VE review. The rationale seems straightforward: the original engineers and architects understand the facility requirements better than anyone else, so they should be best positioned to optimize it. This approach overlooks two critical human and organizational factors: confirmation bias and disciplinary isolation.
- Confirmation Bias: Design teams often invest hundreds of hours developing specific technical solutions. Expecting them to objectively critique their own assumptions, challenge their own design choices, or propose alternatives that render their previous work obsolete is unreasonable.
- Siloed Perspectives: Designers often lack real-world insights into daily facility maintenance, constructability bottlenecks, current supply chain realities, and specialized trade labor availability.
A VE workshop requires independent process leadership provided by a certified facilitator (such as a Certified Value Specialist) [1]. An independent facilitator brings no emotional attachment to the baseline design, enforces strict adherence to the formal VE Job Plan, encourages cross-disciplinary debate, and ensures that facility operators, cost estimators, and contractors have an equal voice in shaping project outcomes.
Conclusion
In conclusion, VE is not a late-stage emergency exercise, a superficial cost-slashing exercise, or a compromise on project quality, nor is it a self-assessment best left to original design teams or limited to upfront CapEx line items. Far more effective than these reactive, price-focused missteps, VE is a function-oriented methodology used by a multidisciplinary team aimed at improving the value of a project, product, process, service, or organization. By deploying a multidisciplinary team early in the design phase, VE aims to optimize the true performance-to-resource ratio, to preserve or enhance functions and enhance the overall value provided by the project, product, process, service, or organization.
References
- [1] SAVE International. Value Methodology Standard and Body of Knowledge.
- [2] Federal Highway Administration (FHWA). Value Engineering Policy and Job Plan Guidelines.