What problem requires the asset to exist?

What Problem Requires the Asset to Exist?

A facility is a solution, not a requirement. Starting with a building, plant, fleet or data centre narrows the decision before demand, service level and flexibility are defined. The correct first question is which business outcome cannot be achieved reliably without control of a physical or long-lived asset.

Specify the need in output terms: capacity, quality, location, response time, security, control and duration. Forecast the demand range and identify when the constraint binds. Separate permanent requirements from peaks or uncertainty. An asset sized for the optimistic case embeds a costly forecast; one designed around average demand may fail precisely when service matters most.

Generate a real longlist: improve the current process, share, lease, outsource, partner, digitise, reserve third-party capacity, build in stages or own outright. The 2026 UK Green Book recommends business as usual, do minimum, less and more ambitious options so the proposed asset must prove that additional features create worthwhile benefits.

Compare lifetime system economics. Include design, permitting, ramp, financing, maintenance, labour, energy, downtime, compliance, decommissioning and residual value. Price contractual dependence and loss of flexibility in alternatives, but also the risk of stranded capacity under ownership. Test each option across demand, technology, input and regulatory scenarios.

Approve ownership only when control creates a measurable advantage that survives the full comparison: lower structural cost, assured scarce capacity, proprietary learning, resilience or a valuable future option. Define stage gates and an exit route before commitment. The asset should exist because it is the best mechanism for a durable requirement�not because a capital proposal made the requirement appear inevitable.