Feasibility sounds like the boring question, and it is routinely confused with the attractive ones: is the project a good idea, is it fundable, is it strategically right. Those questions matter, but they are not this one. Feasibility asks whether the project can actually be carried through to completion by this organization, in this world, under these constraints — a question with its own failure modes, and one that projects pass on attractiveness and fail on quietly. Most large disappointing projects were never infeasible because the idea was wrong; they were infeasible because the carrying capacity was never tested.
The single question decomposes into four, each failing projects for a different reason. Technical: can the result be produced at all, at the required quality, with the methods available — the exam most projects actually prepare for, and the only one. Economic: can it be produced at a cost the value survives — the financial model's territory, and the exam that fails projects whose numbers only close on optimism. Organizational: can this company — these people, this management bandwidth, alongside everything else it already carries — actually execute it; the exam skipped most often, because the honest answer competes with the sponsor's enthusiasm. External: will the surrounding world allow it — permits, partners, dependencies, market timing — the exam that fails projects which assumed the environment was scenery. A project is feasible only where all four overlap; the classic expensive mistake is treating a strong score on one as a passing grade on all.
The organizational exam deserves its own attention, because it fails silently. A project approved in principle by a management team that is already at capacity is not an approved project; it is an approved intention, competing for the same hours as everything else the organization is nominally doing. The same logic scales up: the organization can carry only so many complex efforts simultaneously, and every new flagship project silently downgrades every existing one. This is why killing projects is half of feasibility: a new project is feasible partly in what the organization stops doing to make room for it, and a feasibility verdict that ignores the subtraction is a verdict on a fictional company.
A real feasibility assessment delivers a verdict with a shape — «possible, under these conditions», with the conditions named: this partner secured, this permit obtained, this capacity freed, this phase proving before the next is funded. That shape is what makes the assessment useful rather than merely accurate: the conditions become the project's early gates, the same readiness logic applied to execution. And the verdict works in both directions — an honest «not feasible as scoped» is frequently the most valuable output, because the response is then a redesign (smaller scope, another route, a longer phase) instead of the default response to an approved-but-impossible project, which is to discover the impossibility later, at the point where sunk costs argue for continuing and the calendar argues that there is no longer time to build it another way.
«Possible» is not a mood or a wish. It is the overlap of four exams — technical, economic, organizational, external — and projects are lost exactly at the coordinate where someone assumed the overlap was larger than it was.
Running the four exams honestly — including the organizational one nobody wants to fail — and shaping the verdict into named conditions is standing work in the project and investment practice, performed before commitment, while the verdict can still change the project instead of merely predicting it.
We use cookies to analyse traffic and improve the site. Analytics is enabled only with your consent. Cookie Policy