Timedora

4 Technological Change and Project Value

Learn how technological change can alter project value and how to appraise technology options across their costs, benefits, useful life, and uncertainties.

How technology changes project value

can increase or reduce project value before, during, or after implementation. A new technology may improve output, quality, safety, or reliability; lower operating costs; or create new revenue. It may also need additional investment, take longer to implement than expected, become obsolete sooner, or leave the project less competitive than newer alternatives.

A sound appraisal considers technology over the project's full life, rather than focusing only on purchase price. compares costs and performance over time, while tests how changes in assumptions affect results.

Four channels of impact

Technology affects project value through four related channels:

  • Performance: Changes may affect capacity, speed, accuracy, energy use, quality, uptime, and safety. Performance gains create value only when they address a real need and can be achieved in practice. Distinguish demonstrated performance from vendor claims and early-stage projections.

  • Costs: A technology may have high initial purchase or implementation costs but lower maintenance, labor, energy, or replacement costs. Costs may also fall as production scales up and users gain experience. Do not assume this learning effect without relevant historical evidence: observed cost declines may also reflect research, economies of scale, or changing input prices.

  • Useful life: An asset may remain physically functional after its technology is outdated. Specialized equipment, for example, may still work but become costly to maintain, incompatible with new systems, or unable to meet updated requirements. Estimate both physical life and .

  • Competitive position: Technology may enable better service, lower prices, or capabilities competitors lack. A rival's innovation may instead reduce demand for the project's output or make its assets less efficient by comparison. An advantage may be temporary, and adoption may require new skills, infrastructure, or complementary investments.

Compare options across their whole life

Compare feasible options over a consistent appraisal period, including a “do nothing” or baseline case. For each option, estimate relevant capital and operating costs, benefits, delivery time, replacement needs, and residual value. Include likely upgrades, replacements, downtime, and disposal or residual value in whole-life costs.

Discount future costs and benefits to present values when calculating :

NPV=present value of benefits−present value of costs\text{NPV} = \text{present value of benefits} - \text{present value of costs}

The calculation compares the present value of an option's benefits with the present value of its costs. Early estimates should reflect the risk that costs, delivery times, and benefits may differ from forecasts. Use evidence from comparable projects where available.

Test uncertainty and preserve options

Test assumptions that could materially alter the appraisal result. Useful scenarios include faster or slower performance improvement, different adoption rates, higher maintenance costs, shorter useful life, delayed implementation, and early obsolescence. Show which assumptions would make the preferred option cease to be worthwhile.

For uncertain or difficult-to-reverse investments, or a pilot can preserve the option to expand, modify, or stop after new evidence emerges. This can limit exposure while retaining the possibility of future gains.

Example: conventional or automated equipment

A firm is choosing between conventional and automated equipment. Automation costs more initially but may increase output and reduce labor costs. Its value depends on whether the additional output can be sold, whether staff can operate and maintain the equipment, and whether the system will remain compatible with future software.

The appraisal should compare both options' discounted whole-life costs and benefits. It should also test cases in which automation arrives late, costs more to maintain, or becomes obsolete earlier than expected.