Feasibility Is More Than Financial Viability

An investment can produce an attractive spreadsheet and still be impossible to execute under the conditions the organisation actually faces.

Feasibility is often reduced to a narrow question: will the numbers work? That is necessary, but incomplete. A project can be financially attractive and technically immature. It can be technically sound but commercially unsupported. It can make strategic sense but depend on capabilities the organisation does not possess. It can be viable in isolation yet infeasible once regulation, workforce, supply chain or operating-model constraints are considered.

The supplied study material treats feasibility more broadly. It asks whether a proposed concept is financially, ethically and technically viable, whether it fits organisational strategy, what strategic risks it introduces, what alternatives exist, what assumptions underpin the analysis and whether decision-makers have enough evidence to commit capital.

That broader framing is more useful to executives because feasibility is not a single test. It is a system of conditions that must hold together.

The Strategic Context

Feasibility sits between ambition and commitment.

Strategy identifies what an organisation wants to become. Investment proposals translate that intent into possible actions. Feasibility determines whether those actions can work in the real operating environment.

This is particularly important when the proposed investment is difficult to reverse. A new manufacturing facility, enterprise platform, defence capability, hospital redevelopment or major automation system may create years of follow-on commitments. The cost of discovering a “make or break” constraint after approval can be far greater than the cost of testing the assumption early.

The purpose of feasibility is therefore not to predict the future perfectly. It is to expose the conditions under which the proposal can or cannot succeed before commitment becomes expensive.

What Leaders Commonly Misread

The first misread is to treat feasibility as a technical sign-off. Engineering may confirm that a solution can be built, but that does not prove customers will adopt it, suppliers can support it, operators can use it safely or the organisation can finance the transition.

The second is to confuse market demand with commercial viability. A market may exist while the economics of serving it remain poor.

The third is to assess feasibility only for the preferred option. That turns feasibility into validation rather than comparison.

The fourth is to hide assumptions inside financial models. Discount rates, utilisation, productivity, pricing, service life and implementation duration may drive the conclusion more than the apparent precision of the calculation.

Reframing the Issue

A decision-grade feasibility assessment should answer at least six questions.

Is it technically feasible?

Can the product, service or operating model perform as required? Is the technology mature enough? Are reliability, safety, quality and integration risks understood? What specialist skills, plant, data or infrastructure are required?

Technical feasibility should also consider scale. A concept that works in a prototype, pilot or low-volume environment may not operate reliably at full production or enterprise scale.

Is it operationally feasible?

Can the organisation absorb the change? This includes workforce capability, training, maintenance, process redesign, support systems, change saturation and ongoing ownership.

A solution that creates a new capability without an operating model to sustain it is not fully feasible.

Is it commercially feasible?

Can the organisation procure, contract, sell, support or otherwise sustain the solution within realistic market conditions? Are suppliers capable? Is the proposed sourcing model viable? Are there dependencies on a single vendor or immature ecosystem?

Is it financially feasible?

Can the organisation afford both the investment and the transition? Financial feasibility includes capital requirements, operating costs, working capital, cash flow, financing constraints and the timing of returns.

An attractive long-term return may still be unaffordable if cash is required before the organisation can support it.

Is it strategically feasible?

Does the proposal fit the direction of the enterprise and its future operating model? A technically excellent project can be strategically wrong if it strengthens a capability the organisation intends to exit or locks the enterprise into an obsolete architecture.

Is it institutionally and ethically feasible?

Can the proposal operate within legal, regulatory, social and ethical expectations? Is stakeholder acceptance material? Does the initiative create consequences that would make the nominal business value unacceptable?

Assumptions Are Part of the Design

The supplied study notes emphasise that economic assumptions and their sources should be stated. That principle should extend beyond finance.

A feasibility study is only as strong as its critical assumptions.

For a manufacturing investment, assumptions might include future product mix, sales volume, scrap rates, labour availability, machine uptime, energy cost and supplier lead times. For a public infrastructure project, assumptions may include population growth, demand patterns, environmental approvals, community acceptance and inter-agency dependencies.

Leaders should identify which assumptions are merely uncertain and which are structurally decisive.

A decisive assumption deserves evidence, sensitivity testing or staged validation before full commitment.

Feasibility Should Compare Alternatives

The source material notes that alternatives should be comparable on dimensions such as size, capacity and service life. This is an important discipline.

An alternative is not meaningful if it is evaluated under different assumptions or at a different level of maturity.

Consider a hypothetical automation proposal. Option A is a fully integrated high-speed cell; Option B is modular automation added to an existing line; Option C is process redesign with limited automation. A superficial comparison may favour the integrated cell on labour savings. A feasibility comparison may reveal that the modular option is easier to maintain, less dependent on specialised support and more adaptable to changing product mix.

The best option is not necessarily the one with the highest theoretical return. It is the one with the strongest value under realistic conditions.

Decision Framework

A practical feasibility gate can use a six-domain test:

An initiative does not need zero uncertainty in every domain. It needs uncertainty to be visible, proportionate and governed.

From Strategy to Execution

Immediately, feasibility work should identify the top “make or break” questions before teams spend time refining lower-value details. If regulatory approval is uncertain, proving a detailed five-year maintenance cost may not be the first priority.

In the medium term, organisations should use staged commitment. Pilot, prototype, proof-of-concept or market testing can convert uncertainty into evidence. The objective is not to make every project agile; it is to preserve reversibility where uncertainty is high.

Over the long term, feasibility should become connected to portfolio learning. Actual outcomes should improve future assumptions about implementation time, adoption, reliability, demand and operating cost.

Signals to Monitor

Warning signs include feasibility studies written after the preferred solution has already been chosen, repeated use of untested assumptions, technical assessments that exclude operating teams, commercial models that ignore supplier fragility, and investment cases that assume adoption without identifying behaviour change.

Also watch for studies that answer “can it be done?” without asking “can it be done here, now, by this organisation, at this scale and with these constraints?”

Questions for the Leadership Team

1. What would make this concept infeasible even if the financial return appears attractive?
2. Which assumptions are most sensitive to scale, demand or organisational capability?
3. Are we testing the preferred option or genuinely comparing alternatives?
4. What evidence can we obtain cheaply before making an irreversible commitment?
5. Who will own the capability after project delivery?
6. Which feasibility domain currently has the weakest evidence?

Closing Perspective

Feasibility is not an obstacle placed in front of ambitious ideas. It is the discipline that separates credible ambition from expensive optimism.

The strongest organisations test whether strategy can survive contact with engineering, markets, finance, operations, regulation and human behaviour before they lock in capital. That is not caution for its own sake. It is how leaders preserve the ability to invest boldly where the conditions are genuinely favourable.