- ✓Technical feasibility assesses whether the technology needed to build the proposed system exists and is accessible within the project constraints.
- ✓Economic feasibility compares development and operational costs against expected benefits, usually expressed as return on investment or net present value.
- ✓Operational feasibility considers whether the organisation can effectively use and maintain the system once it is delivered.
- ✓Legal feasibility examines whether the proposed system complies with relevant legislation, regulations, and contractual obligations.
- ✓A feasibility report should conclude with a clear recommendation and, where appropriate, outline alternative approaches that were considered.
Listen to the full episode inside the course. Enrol to access all 80 episodes, plus assignments, tutor support and Student Finance funding.
Start learning →Alex: Today we're looking at how to produce a proper systems feasibility study. Sam, we covered feasibility in Unit 7, but at Level 5 you're expected to produce one yourself. What does that require?
Sam: It requires a thorough, evidence-based investigation of all the key dimensions of feasibility, presented in a professional, well-structured report. It's not a superficial checklist; it's a genuine analytical exercise that involves research, evidence gathering, cost-benefit analysis, and reasoned judgement. A good feasibility study demonstrates that you can think analytically about complex, multi-dimensional questions.
Alex: Let's walk through the technical feasibility dimension.
Sam: Technical feasibility asks whether the system can actually be built. This involves investigating whether the required technologies exist and are mature, whether the development team has or can acquire the necessary skills, whether the existing IT infrastructure can support the new system, and whether there are any known technical risks or constraints. For a novel system using cutting-edge technology, technical feasibility may require a proof-of-concept prototype to test key assumptions.
Alex: And economic feasibility? The cost-benefit analysis?
Sam: A rigorous cost-benefit analysis identifies all the costs associated with the system: development, hardware, software licences, training, maintenance, and operational costs. It then estimates the benefits, which might include cost savings from efficiency improvements, revenue generated, risk reduction, or strategic value. The costs and benefits are projected over a defined time horizon, often three to five years, and metrics like net present value, return on investment, and payback period are calculated.
Alex: What makes this challenging in practice?
Sam: Estimating both costs and benefits involves significant uncertainty. Development costs are notoriously difficult to estimate accurately; real projects typically cost more and take longer than initial estimates. Benefits are even harder to quantify, particularly when they relate to strategic positioning, risk reduction, or improved customer experience rather than straightforward cost savings. A good feasibility report acknowledges these uncertainties explicitly and presents ranges or sensitivity analyses rather than single-point estimates.
Alex: What about operational feasibility?
Sam: Operational feasibility assesses whether the organisation can actually use and maintain the system effectively. This involves questions about whether staff have the skills to use it, whether existing processes are compatible with how the system works, whether the organisation has the IT support capacity to maintain it, and whether the organisational culture will embrace the change. A technically excellent system that the organisation can't operate effectively is not a feasible solution.
Alex: How should the recommendation section be written?
Sam: The recommendation should be clearly stated and directly supported by the analysis in the body of the report. 'Based on the analysis above, we recommend proceeding with option 2, the cloud-based solution, because it offers the best balance of cost, technical feasibility, and alignment with the organisation's strategic objectives'. Where there are significant uncertainties or risks, these should be acknowledged and the conditions under which the recommendation holds should be stated.
Alex: Brilliant. Thanks Sam. Next we look at systems analysis methodologies in more depth.