A feasibility analysis (or feasibility study) is a structured assessment of whether a proposed project is viable — technically, financially, and operationally — before committing significant resources. It answers a fundamental question: "Should we do this project?"
This analysis typically happens during the pre-project or initiation phase, before the project charter is finalized. Its output directly feeds the business case and the go/no-go decision.
The Five Dimensions of Feasibility
A thorough feasibility study evaluates the project across multiple dimensions, commonly remembered as TELOS:
Technical Feasibility
"Can we build it?"
Does the required technology exist? Does the team have the skills? Are there proven solutions, or would this require unproven innovation? What are the integration challenges with existing systems?
Economic Feasibility
"Is it worth the investment?"
Do the benefits outweigh the costs? What's the ROI, payback period, and NPV? Can the organization afford the upfront and ongoing costs? What are the opportunity costs?
Legal Feasibility
"Are we allowed to do it?"
Are there regulatory, licensing, or compliance constraints? Does it conflict with existing contracts? Are there intellectual property concerns? Data privacy implications (GDPR, HIPAA)?
Operational Feasibility
"Will it work in practice?"
Will the organization adopt the solution? Does it fit existing workflows? Is there management support? Will users accept the change, or is resistance likely?
Schedule Feasibility
"Can we deliver it in time?"
Is the required timeline realistic given the scope and available resources? Are there hard deadlines (regulatory, market windows) that cannot move?
Financial Analysis Tools
Economic feasibility is usually the most scrutinized dimension. Common financial tools used in the analysis:
| Tool | What It Measures | How to Use |
|---|---|---|
| Cost-Benefit Analysis (CBA) | Total costs vs. total benefits over the project's life | If benefits > costs, the project is economically justified |
| Return on Investment (ROI) | Percentage return relative to the investment | ROI = (Net Benefit / Cost) × 100%. Higher is better |
| Net Present Value (NPV) | Today's value of future cash flows minus the investment | NPV > 0 means the project adds value. Accounts for time value of money |
| Payback Period | How long until the investment is recovered | Shorter payback = lower risk. Simple but ignores cash flows after payback |
| Internal Rate of Return (IRR) | The discount rate at which NPV equals zero | If IRR > required rate of return, the project is worthwhile |
How to Conduct a Feasibility Study
01
Define the Problem
Clearly articulate the business need or opportunity. What problem are we trying to solve? What happens if we do nothing?
02
Identify Alternatives
Don't evaluate just one option. Consider at least 2–3 alternatives, including "do nothing." Each alternative gets assessed independently.
03
Assess Each Dimension
Evaluate each alternative across Technical, Economic, Legal, Operational, and Schedule feasibility. Use data, not assumptions.
04
Identify Risks
What could go wrong? For each alternative, list the key risks and their potential impact. High-risk options need stronger justification.
05
Recommend
Present findings with a clear recommendation. Include the rationale, assumptions, and conditions under which the recommendation holds.
Feasibility Study vs. Business Case
These are related but distinct documents:
- The feasibility study asks: "Can we do this? Should we?" — it evaluates options and viability.
- The business case asks: "Here's why we should invest" — it justifies the selected option to decision-makers.
The feasibility study feeds into the business case. If the study says "not feasible," no business case is written. If it says "feasible," the business case uses the study's financial analysis, risk assessment, and recommendation as its foundation.
Common Mistakes
- Confirmation bias: Conducting the study to justify a decision that's already been made. If the conclusion is predetermined, the study is theater, not analysis.
- Ignoring operational feasibility: A technically brilliant solution that users refuse to adopt is still a failure.
- Underestimating costs: Optimistic cost estimates are the most common error. Include contingency reserves and consider total cost of ownership, not just development costs.
- Skipping alternatives: Evaluating only one option isn't a study — it's a sales pitch. Always compare against doing nothing and at least one other approach.
- Not revisiting: Feasibility can change as the project progresses and more information emerges. In long projects, revisit the analysis at major stage gates.
A feasibility study that kills a bad project before it starts is one of the highest-value activities in project management. It's far cheaper to spend a few weeks analyzing viability than to spend months (and budget) discovering mid-execution that the project was never going to work. The courage to recommend "don't proceed" when the data says so is a mark of a mature project organization.