Operational Feasibility
Operational feasibility asks one question: will the people who must use this system actually use it once you walk away? Strong operational feasibility evidence keeps your project from joining the long list of shelved capstone projects.
Feasibility Lenses
| Lens | Question | Tools |
|---|---|---|
| Operational | Will users adopt it? | User interviews, training plan, change-readiness survey |
| Technical | Can we build it? | Architecture review, skills audit, prototype |
| Economic | Is it worth it? | Cost-benefit, ROI, payback |
| Schedule | Can we finish on time? | WBS, Gantt, risk log |
| Legal | Are we allowed? | DPA, IP, contracts |
Operational Feasibility Checklist
| Check | Pass Criterion |
|---|---|
| User involvement | Beneficiary signed-off scope and prototype |
| Training plan | Plan exists with audience, materials, hours |
| Change management | Clear who champions adoption |
| Support model | Help-desk, FAQ, or contact person assigned |
| Workflow fit | Use case observed in actual setting at least once |
| Cultural fit | Bilingual UI where the workforce mixes languages |
| Device fit | Runs on the devices users actually own |
Evidence To Collect
- Letter of acceptance or endorsement from the beneficiary.
- Photos of site visits with date stamps.
- Signed minutes of stakeholder meetings.
- Survey results showing baseline pain points.
- Training schedule and material outlines.
Red Flags
A project is operationally infeasible if any of these are true:
- The intended users have never been interviewed.
- The beneficiary cannot describe how the system fits their day.
- There is no plan for who maintains the system after defense.
Discussion
Loading…