Are you solving the business need or developing the first available project?

Are You Solving the Business Need or Developing the First Available Project?

A concept can become inevitable before the requirement is understood. A site is available, a vendor offers a platform or an engineering team has a familiar design; feasibility work then improves that solution rather than testing whether it is the best mechanism. Development effort creates detail, and detail is mistaken for evidence of strategic fit.

Freeze the proposed project and restate the business need as an outcome: capacity, service, quality, resilience, compliance or cost, for whom and by when. Define the counterfactual and the minimum acceptable performance. Identify the constraint causing the gap. This prevents a desired asset from writing its own requirement.

Generate structurally different options before narrowing: change demand, improve the current system, alter process, share, buy a service, lease, partner, digitise, phase or build. HM Treasury�s 2026 Green Book retains business as usual and do minimum in the shortlist so more ambitious solutions must demonstrate that added features produce worthwhile value.

Invest in evidence proportionately. Use market engagement, prototypes, capacity tests and customer experiments to resolve the assumptions that separate options. Keep feasibility teams independent enough to compare alternatives; a supplier paid to develop one design cannot provide neutral evidence that no other model works. Include full lifecycle cost, transition and exit.

Record the need, critical success factors, options rejected, evidence and trigger for commitment. Reopen the choice if the need, market or technology changes before irreversible spend. The objective is not to deliver the first project efficiently. It is to achieve the business outcome through the option that preserves the most value after cost, risk and flexibility are considered.