Feasibility study: the five angles to examine

A feasibility study answers a question that comes before the business case: can this project actually be delivered? It examines the same idea from several independent angles, each of which can sink it on its own. A project that is economically brilliant and legally impossible is not a project; it is a proposal that has not been instructed.

Technical feasibility

Does the technology exist, is it mature, and does the organization have — or can it acquire — the skills to use it? The honest version of this analysis names what has never been done before in-house. A prototype or a proof of concept on the single riskiest point often costs less than the meetings spent arguing about it.

Economic feasibility

Not the return — that belongs to the business case — but the ability to fund the thing: is the order of magnitude of the cost compatible with the available envelope, over the years it will actually span? A project whose cost is only known to within a factor of three is not ready to be committed, whatever its expected benefits.

Organizational and resource feasibility

The angle that is skipped most often, and the one that kills the most projects. The skills required may exist in the company and already be fully committed to other work. Checking that the profiles needed are genuinely available over the planned period — not on paper, but net of leave, of run duties and of the other projects already promised — is what separates a plan from a wish.

Legal and regulatory feasibility

Personal data, sector regulation, procurement rules, intellectual property, contractual commitments to a client. This angle rarely blocks a project outright, but it routinely changes its cost and its timeline — and it does so much more cheaply at the study stage than during acceptance testing.

Schedule feasibility

A deadline is a constraint like any other and it can be infeasible on its own. Compare the required date against a rough critical path and against the resource availability established above. If the two disagree, the study must say so before anyone commits to the date publicly.

Concluding: go, no-go, or conditional go

A feasibility study is entitled to conclude no. Its most useful output, though, is often the third option: a conditional go — feasible provided two developers are freed up in September, or provided the regulatory point is settled first. That formulation turns a vague doubt into a decision someone can actually take.

Instructing it with FoxPlan

The resource angle is the one you can verify with data rather than opinion: FoxPlan shows the capacity available by skill over the coming months, net of what the committed projects already consume. Testing a candidate project against that picture — before it is approved — is how a portfolio avoids promising the same people three times.