Feasibility Is a Learning Gate, Not a Project Approval Ritual

The purpose of feasibility is not to make an idea look investable. It is to learn, cheaply and early, whether the organisation should keep investing in the idea at all.

A proposal can look compelling long before it is ready for commitment. The problem may be real, the sponsor may be influential, the technology may be available and an indicative financial case may appear attractive. Yet none of those conditions proves that the proposed intervention is the right response, that the organisation can execute it, or that the benefits will survive contact with operational reality.

This is where feasibility is often misunderstood. In weak governance environments, a feasibility study becomes another document on the road to approval. The question quietly changes from “Should we continue?” to “What evidence do we need to get this approved?” Once that happens, the organisation has already surrendered much of the value of the exercise.

A better view is to treat feasibility as a learning gate. The organisation spends a limited amount of time and money to expose uncertainty before it spends much more. The output is not necessarily permission to proceed. It may be a redesigned concept, a smaller experiment, a request for better evidence, a deliberate delay, or a decision to stop.

The Strategic Context

Project selection is a commitment of future organisational capacity. The MPM416 teaching material makes this connection directly: selection is not only about whether an individual project appears worthwhile, but also about objectives, resource constraints, strategic alignment, stakeholder effects, technological readiness, market potential and financial return.

That portfolio perspective matters because every approved initiative consumes more than its stated budget. It uses scarce specialists, leadership attention, governance capacity, operational tolerance for change and the organisation's ability to absorb disruption. A project that is feasible in isolation may be infeasible inside the actual portfolio.

Feasibility therefore sits between strategic intent and investment commitment. It should reduce uncertainty enough for leaders to decide whether further analysis is justified. Mesly's 2016 treatment of prefeasibility is useful because it deliberately separates a broad early examination from the more detailed feasibility work that may follow. His approach looks at a proposed project from several angles to uncover “points of vulnerability”, rather than assuming that more detail automatically produces more confidence.

The deeper strategic principle is durable: before asking how to deliver an initiative, test whether its logic deserves to survive.

What Leaders Commonly Misread

The first mistake is treating feasibility as a technical test. Technical feasibility matters, but it is only one dimension. A system can be engineered successfully and still fail commercially, socially, operationally or politically. The MPM416 material explicitly broadens feasibility to economic, financial, legal, environmental, social, risk, sustainability and political considerations.

The second mistake is confusing affordability with value. An organisation may be able to fund an initiative that should not be funded. Conversely, an initiative may create substantial value but require a financing model or timing decision that makes immediate execution impractical.

The third mistake is treating sponsor enthusiasm as evidence. Strong sponsorship can accelerate valuable change, but it can also make weak assumptions harder to challenge. Once a proposal acquires a name, a team and an announced timetable, stopping it becomes psychologically and politically more difficult.

The fourth mistake is assuming that uncertainty should be eliminated before a decision is made. That is rarely possible. The real task is to identify which uncertainties matter enough to change the decision and whether the cost of resolving them is justified.

Finally, leaders often treat the feasibility report as the decision. It is not. It is evidence for a governance choice.

Reframing the Issue

A useful feasibility process answers four different questions.

Is the problem or opportunity real? The organisation needs evidence that the trigger is material rather than anecdotal, transient or politically convenient.

Is the proposed response causally credible? A genuine problem does not make the preferred solution correct. Leaders need to understand why this intervention should produce the desired outcome.

Can the organisation make it work? Capability, interfaces, approvals, suppliers, data, operating constraints, workforce behaviour and implementation capacity must be considered alongside technical design.

Is further commitment justified now? Even a credible concept can be premature if key assumptions remain unresolved or if a more valuable alternative competes for the same resources.

This reframing changes the tone of the analysis. Feasibility becomes less about proving that an idea can be done and more about determining the conditions under which it would be sensible to proceed.

Strategic Analysis: Search for Failure Before It Becomes Expensive

Mesly's prefeasibility work is distinctive because it encourages the analyst to look at the same proposal from multiple perspectives and to search deliberately for vulnerabilities. ERANORTH should not reproduce his proprietary frameworks or numerical thresholds, but the underlying logic is powerful.

A proposal should be examined as a system.

The problem-solution link

Start with the causal chain. What is happening? Why is it happening? Why does it matter now? Why should the proposed action alter the underlying system rather than simply treat a symptom?

The “five whys” sequence in the MPM416 material is useful here because it moves from motivation to evidence, urgency, intervention logic and unintended consequences. The important executive move is not mechanically asking “why” five times. It is refusing to let the proposal advance while its causal logic is ambiguous.

The constraint environment

Projects operate inside constraints that are often treated as background information: available capital, specialist labour, plant capacity, regulatory permissions, environmental limits, customer tolerance, data quality, supplier capability and transition windows.

These are not secondary planning details. They determine whether the initiative is executable.

A manufacturing automation project, for example, may have a credible technical design and attractive labour savings. Yet if it requires a shutdown window the business cannot tolerate, depends on a single overseas integrator, or transfers maintenance complexity to a team without the necessary skills, feasibility has changed.

The vulnerability structure

Risk lists often focus on external events: supplier failure, market change, regulatory delay or technology obsolescence. Mesly distinguishes such external pressures from internal vulnerability. That distinction is strategically useful.

A supply disruption is a threat. Sole-source dependence is a vulnerability.

A cyberattack is a threat. Weak identity controls and poor recovery capability are vulnerabilities.

A market downturn is a threat. A business case dependent on one aggressive demand assumption is a vulnerability.

Leaders should therefore ask not only “What might happen?” but also “What about our design would make that event damaging?”

The stakeholder and authority system

An initiative can be technically and economically credible while lacking the authority, legitimacy or operating cooperation needed to implement it.

Who can block the work? Who must change behaviour? Who bears the disruption? Who owns the benefits? Which decisions cross organisational boundaries? Which stakeholder has an incentive to delay, resist or optimise locally?

These questions are especially important in programs, public-sector initiatives and enterprise transformations where the delivery team does not control all of the conditions required for success.

Decision Framework

A decision gate should distinguish between evidence that is sufficient to continue learning and evidence that is sufficient to commit.

A practical executive test is:

Test	Core question	Possible decision
Problem validity	Is the problem or opportunity material and evidenced?	Stop, clarify or continue
Intervention logic	Is there a credible mechanism linking action to outcome?	Redesign or continue
Multi-dimensional feasibility	Is the concept technically, operationally, financially, legally and socially workable?	Resolve constraints, stage or stop
Portfolio fit	Can the organisation absorb the initiative alongside existing commitments?	Sequence, defer or reprioritise
Evidence maturity	Are decision-critical assumptions sufficiently tested?	Experiment, analyse further or proceed
Reversibility	Can we learn through a smaller commitment before making a larger irreversible one?	Pilot, prototype or stage
Governance legitimacy	Are decision rights, affected stakeholders and benefit ownership clear?	Rework governance or proceed

The test should not produce a decorative score. It should produce a decision.

Four outcomes are usually enough:

Proceed to deeper analysis. The concept is credible but not yet ready for full commitment.

Proceed conditionally. Specific evidence, approvals or capability must be secured before the next tranche.

Redesign or stage. The idea has value, but the current configuration concentrates too much uncertainty or irreversible commitment.

Stop. The problem, solution logic or enterprise value is too weak to justify further organisational attention.

Stopping is not project failure. It can be evidence that portfolio governance is working.

From Strategy to Execution

Immediate action

Before approving the next substantial commitment, require the sponsor to state the problem, alternatives, key assumptions, major constraints and evidence that would invalidate the preferred option.

Separate “known”, “assumed” and “to be tested”. This simple distinction often reveals that a confident proposal is resting on a surprisingly small evidence base.

Make a named executive accountable for the gate decision, not merely for sponsoring the project.

Medium-term capability building

Standardise the questions, not the answers. A feasibility process should be consistent enough to create discipline but flexible enough for different investment types.

Develop access to engineering, financial, operational, commercial, legal, risk and stakeholder expertise. Feasibility is cross-functional by nature.

Build a portfolio view of constrained resources so that feasibility includes organisational capacity, not just project viability.

Create a record of assumptions that can flow into the business case, program plan and benefits governance rather than being recreated at each stage.

Long-term strategic positioning

The strongest organisations learn to make smaller irreversible commitments and faster reversible tests.

That means designing investment pathways in tranches where possible, deliberately preserving options and making evidence maturity part of capital allocation. Over time, this reduces the cost of being wrong while increasing the speed at which promising opportunities can be proven.

Feasibility then becomes part of strategy execution rather than a preliminary administrative step.

Signals to Monitor

Leaders should be concerned when:

feasibility activity begins after a preferred solution has already been publicly committed;
alternatives disappear from the analysis without a documented reason;
the same people who designed the proposal are the only people challenging its assumptions;
all major assumptions move in the direction needed to support approval;
project feasibility is assessed without reference to portfolio capacity;
“technical feasibility” becomes shorthand for total feasibility;
benefits depend heavily on behaviour or operating change that has not been tested;
decision gates routinely approve further spending without identifying what was learned since the previous gate;
teams cannot state what evidence would cause them to stop.

These are signals that the organisation is performing approval rather than learning.

Questions for the Leadership Team

What evidence would make us decide not to proceed with this initiative?
Which assumption, if wrong, would most damage the investment logic?
Are we testing the proposed solution, or merely confirming that the underlying problem exists?
What portfolio capacity will this initiative consume beyond its stated budget?
Which part of the commitment is difficult or expensive to reverse?
Could a smaller experiment resolve the most important uncertainty before we commit at scale?
Who has the authority and incentive to challenge the sponsor's preferred answer?

Closing Perspective

Feasibility is valuable precisely because the organisation has not yet committed itself to being right.

Leaders should use that window aggressively. Search for weaknesses while they are still cheap to find. Test the causal logic before building the delivery machinery around it. Distinguish technical possibility from enterprise viability. Preserve alternatives until the evidence is strong enough to justify closing them.

The strongest feasibility process does not maximise the number of projects that pass. It improves the quality of the commitments that survive.