Feasibility Is a Search for Failure Before It Is a Case for Approval

The most valuable feasibility study is not the one that makes a proposal look convincing; it is the one that reveals the conditions under which the proposal will fail before those conditions become expensive.

A project can be attractive on paper and still be impossible to execute in the organisation that has to live with it. Financial returns may depend on production volumes that the market cannot sustain. A technology may function in a pilot yet be unreliable at scale. A new operating model may require skills the organisation cannot recruit. A facility may be technically buildable but commercially dependent on a fragile supply chain or socially unacceptable in the chosen location.

This is why feasibility should not be treated as a confirmation exercise after a preferred solution has gained momentum.

It is a structured attempt to discover whether reality will defeat the investment thesis.

The Strategic Context

The supplied feasibility material is broader than financial appraisal. It considers technical, market and commercial viability, financial conditions, strategic fit, risks, resource needs, regulatory requirements, data, assumptions, alternatives and the capacity to implement.

Mesly's supplied work adds another useful distinction: pre-feasibility takes a broad early view, whereas a feasibility study moves further into how the project would actually function in day-to-day operations.

That makes feasibility the bridge between strategic intention and operating reality.

This bridge matters most when the commitment is difficult to reverse. New plants, major software platforms, defence capabilities, infrastructure, acquisitions and large automation systems can create years of secondary commitments. Once contracts are signed, organisational structures changed and people mobilised, the cost of discovering a fundamental flaw rises sharply.

Feasibility is therefore a form of pre-commitment risk reduction.

What Leaders Commonly Misread

The first mistake is to ask only whether the proposal can be built. Technical feasibility matters, but a technically sound solution may fail commercially, operationally or institutionally.

The second is to treat a positive market signal as proof of commercial viability. Customers may want a product that cannot be served profitably at the required quality, price and scale.

The third is to analyse only the preferred option. Once the feasibility team is asked “prove whether this design will work”, the organisation has already narrowed the decision too far.

The fourth is precision without evidence. A model with detailed capital cost, payback and NPV can look sophisticated while depending on fragile assumptions about demand, adoption, uptime, labour savings or implementation duration.

The fifth is to hide operating consequences. A project may be deliverable while the resulting capability is unsustainable. Maintenance, training, data quality, support processes, cybersecurity, spare parts, supplier dependency and organisational ownership can determine whether the value survives after project closure.

Reframing the Issue

A feasibility study should be treated as a structured search for failure conditions, binding constraints and unresolved dependencies.

The goal is not to remove all uncertainty. That is impossible. The goal is to make uncertainty visible enough that leaders know what they are accepting.

For each proposed option, feasibility should answer four questions:

1. What must be true for this to work?
2. What evidence supports those conditions?
3. Which conditions are outside our control?
4. What happens if one of the critical conditions fails?

This changes the tone of the analysis. Instead of asking only “What are the benefits?”, leaders also ask “What could invalidate the value mechanism?” Instead of asking only “Can the supplier deliver?”, they ask “What would happen if the supplier cannot?”

Technical Feasibility Is About Performance at the Required Scale

Technical feasibility is not a laboratory question. It must relate to actual operating conditions.

For an engineering investment, that can include throughput, tolerances, reliability, maintainability, safety, integration, energy demand, environmental conditions and the availability of technical support. A machine that meets cycle time in a supplier demonstration may not meet overall line output once changeovers, upstream variation, operator intervention and downstream constraints are included.

For digital investment, technical feasibility includes data quality, interfaces, architecture, security, performance and supportability. A prototype can prove functionality without proving enterprise operability.

The key question is not merely “Does the technology work?” but:

Can the complete system perform reliably enough, at the required scale, inside the constraints of this organisation?

Operational Feasibility Is Often the Hidden Constraint

Many investments fail to realise value because the organisation cannot absorb the new capability.

Operational feasibility examines the people, processes, governance and support model required after the project delivers its output. It asks whether staff can be trained, whether roles are clear, whether work processes will change, whether maintenance is funded, whether capacity exists to manage the transition and whether the organisation can tolerate the disruption.

A hypothetical hospital technology project may be technically excellent and financially funded, yet remain operationally weak if clinical workflows, training, data ownership and support arrangements are unresolved.

A manufacturing automation project may remove manual work from one operation while creating a specialist maintenance dependency that the plant cannot support on night shift.

These are feasibility questions, not post-implementation surprises.

Commercial and Market Feasibility Test the External System

Commercial feasibility asks whether the investment can be sourced, contracted, sold or sustained under realistic market conditions.

It should examine supplier capability, pricing, contracting structure, market maturity, customer behaviour, competitive response, working capital, distribution, service arrangements and the ability to access critical inputs.

Market feasibility is related but different. It asks whether sufficient demand exists at a sustainable value proposition.

Leaders should be wary of demand estimates that assume the organisation will capture the market simply because the market exists. Total market size is not the same as reachable demand, and reachable demand is not the same as profitable demand.

Financial Feasibility Is About Affordability as Well as Return

An investment can have a positive long-term return and still be financially infeasible.

The organisation may not be able to fund the peak cash requirement. Working capital may be underestimated. Transition costs may arrive before benefits. Debt covenants, capital limits or competing commitments may make the timing unacceptable.

Financial feasibility should therefore separate two questions:

Is the investment economically attractive?

and

Can the organisation actually carry the cash and funding burden required to reach that value?

The supplied material also stresses that assumptions such as discount rates, inflation, tax treatment and risk adjustments should be explicit. Where current policy values or mandated rates are required, they should be independently verified before publication or decision use. [FACT CHECK REQUIRED]

Strategic and Institutional Feasibility Test Permission to Succeed

A proposal can be technically, commercially and financially viable yet still be strategically wrong.

Strategic feasibility asks whether the investment strengthens capabilities the organisation actually intends to own. It tests alignment with future business model, portfolio direction and operating architecture—not merely whether a sponsor can connect it to a broad strategic phrase.

Institutional feasibility considers regulation, ethics, legitimacy, stakeholder acceptance and policy constraints. For public or infrastructure investments, these issues may determine whether the project is implementable at all. For private firms, community expectations, workforce acceptance, environmental consequences and customer trust can also become binding conditions.

Decision Framework

A decision-grade feasibility review can be structured around seven domains.

For each domain, classify the evidence as proven, plausible, weak or unknown. The purpose is to show where the decision still depends on belief rather than evidence.

From Strategy to Execution

Immediately, feasibility teams should identify the top five conditions most capable of killing the proposal. Investigate those first. It is wasteful to refine secondary cost detail while a fundamental regulatory, demand or technical uncertainty remains unresolved.

In the medium term, use staged commitment. Pilots, prototypes, market tests, supplier trials and limited deployments can convert assumptions into evidence while preserving reversibility.

In the longer term, connect feasibility forecasts with actual performance. If the organisation repeatedly underestimates implementation time, training effort, maintenance cost or adoption difficulty, future feasibility models should be adjusted. Feasibility becomes stronger when it incorporates organisational memory rather than starting from optimistic first principles each time.

Related article: Before Feasibility: The Executive Decision That Determines Whether an Idea Deserves Further Investment

Related article: Risk Is Not Vulnerability: Why Strong Projects Survive Shocks That Weak Projects Cannot

Signals to Monitor

Warning signs include feasibility work beginning after the solution has effectively been selected; technical specialists assessing the proposal without operators; benefits built on untested behaviour change; supplier quotes treated as evidence of long-term commercial resilience; and risk registers that list events without identifying the internal weaknesses that make those events consequential.

Also monitor language. A feasibility study that repeatedly says “will” where evidence supports only “may” is signalling confidence beyond the source material.

Questions for the Leadership Team

1. What are the three conditions most capable of invalidating this investment?
2. Which critical assumption currently has the weakest evidence?
3. Are we genuinely comparing alternatives, or testing only the sponsor's preferred design?
4. What evidence can be obtained before the next irreversible commitment?
5. Can the resulting capability be sustained operationally after the project team exits?
6. What is outside our control, and how exposed are we to it?
7. If this proposal were wrong, where would the first signs appear?

Closing Perspective

Good feasibility analysis does not make investment slower. It makes irreversible mistakes less likely.

The purpose is not to construct a persuasive case around an attractive idea. It is to expose the constraints, dependencies and failure conditions that strategy must survive before capital is committed. When a proposal emerges stronger after that challenge, leaders can invest with greater confidence. When it does not, the organisation has learned something valuable before the lesson became expensive.