SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

Fundamentals

What Is a Feasibility Study? A Practical Guide for Business Analysts

Fundamentals · Published · Updated · 12 min read · By BA Mentorship Editorial (AI-written)

Part of our guide to business analyst roles and responsibilities.

What a feasibility study is

A feasibility study is a short, structured investigation that answers one question before a company commits money and people: can we do this, and should we? It looks at a proposed change, such as a new system, a new process or a new product feature, and checks whether it is realistic from several angles.

It usually happens early. Someone has described a problem or an opportunity, but the project is not yet fully approved. In the business analysis life cycle, it sits close to strategy analysis: you have a problem statement, a rough idea of a solution, and a sponsor who wants to know if it is worth pursuing.

When job descriptions mention feasibility, they mean you can gather facts from the right people, test assumptions and write a clear recommendation. That is core analysis work, and it is one of the reasons the role exists, as explained in what a business analyst does.

The output is normally a short document or slide pack. It describes the options, the findings for each type of feasibility, the main risks and a recommendation: go, go with conditions, or stop.

The four main types of feasibility

Technical feasibility

Can the solution be built with the technology, skills and data the company has or can get? This covers existing systems, integrations, data quality, security and performance needs. A feature can be a good idea and still be impossible on the current platform.

Operational feasibility

Will the solution actually work in daily operations? This asks whether people will use it, whether processes, roles and policies must change, and whether the support team can run it after go-live. Many projects struggle here. The software works, but the way people really work was ignored.

Economic feasibility

Do the benefits justify the costs? You compare one-off costs (build, licences, training) and running costs (support, hosting, maintenance) with expected benefits such as time saved, errors avoided or new revenue. A simple payback period is often enough at this stage, but it only means something when you compare it with a threshold the sponsor or finance team has agreed, for example a maximum payback period. Some teams call this financial feasibility or cost-benefit analysis.

Schedule feasibility

Can it be delivered in the time available? Some deadlines are fixed by the market, a contract or a regulation. If the work cannot finish before the date that matters, the benefit may disappear, so a smaller first release may be the only feasible option.

Some teams also check legal or regulatory feasibility, for example data protection rules. Rules vary by country and industry, so the BA collects the questions and the legal or compliance team gives the answers.

Four types of feasibility at a glance

AspectCore questionWho you askTypical evidence
TechnicalCan we build it with our systems and skills?Lead developer, architects, IT securitySystem constraints, integration options, data checks
OperationalWill people use it, and can we run it?Operations leads, end users, support teamProcess maps, workload estimates, policy impacts
EconomicDo the benefits outweigh the costs?Sponsor, finance, operationsCost estimates, benefit assumptions, payback against an agreed limit
ScheduleCan we deliver before the date that matters?Project manager, delivery teamRough estimates, key dates, dependencies
Each type asks a different question and needs evidence from different people.

Questions to ask for each type of feasibility

Good feasibility work is mostly good questions asked to the right stakeholders. Use these as a starting list and adapt them to your project.

Technical questions

  • Which existing systems does this touch, and do they have APIs or data exports we can use?
  • Is the data we need available, accurate and owned by someone?
  • Are there security, privacy or performance needs that rule out an option?
  • Do we have the skills in-house, or do we need a vendor?

Operational questions

  • Who will use this every day, and what changes in their work?
  • Which policies, rules or handovers block the new way of working?
  • Who supports it after go-live, and do they have capacity?
  • What training or communication will people need?

Economic questions

  • What are the one-off costs and the yearly running costs?
  • Which benefit do we expect, and how will we measure it?
  • What payback period or return does the sponsor need before approving?
  • Which assumption has the biggest effect on the numbers, and where is its break-even point?
  • What happens if we do nothing?

Schedule questions

  • Is there a fixed date, and what happens if we miss it?
  • What is a rough estimate for the smallest useful release?
  • Which dependencies (other teams, vendors, approvals) could delay us?
  • How much buffer is left between the planned finish and the date that matters?

How a business analyst runs a feasibility study

You do not need a heavy method. A clear, repeatable sequence is enough for most decisions.

  1. Confirm the problem and the goal. Write down the problem, who has it and what success looks like. If the goal is vague, every feasibility answer will be vague too.
  2. Agree the options and the decision rules. List two or three possible solutions, including do nothing. Ask the sponsor what a project must achieve to be approved, such as a maximum payback period or a fixed date.
  3. Set the boundaries. Agree what the study covers, who takes part and when the recommendation is due.
  4. Gather evidence for each type. Run short interviews or a workshop with developers, operations, finance and the project manager. Record facts, estimates and assumptions separately.
  5. Rate each type and note the risks. For each option, mark technical, operational, economic and schedule feasibility as feasible, feasible with conditions or not feasible, with one line of reasoning against the agreed rules.
  6. Write the recommendation. Summarise the findings on one page, state the conditions, and present it to the sponsor for a decision.

The BA does not need to be the technical or financial expert. Your job is to ask the right people, keep facts and guesses apart, and make the trade-offs easy to see.

Feasibility study in six steps6 steps in order: 1. Confirm problem and goal: Write the problem, who has it and what success looks like, in plain words. 2. Agree options and rules: List two or three solutions, including doing nothing, and the rules a project must meet. 3. Set study boundaries: Agree what the study covers, who takes part and when the recommendation is due. 4. Gather evidence: Interview developers, operations, finance and the project manager. Keep facts and assumptions apart. 5. Rate and note risks: Mark each type as feasible, conditional or not feasible, with one line of reasoning. 6. Recommend: Share a one-page summary with conditions and ask for a go, conditional go or stop decision.1Confirm problem and goalWrite the problem, who has it and whatsuccess looks like, in plain words.2Agree options and rulesList two or three solutions, includingdoing nothing, and the rules a projectmust meet.3Set study boundariesAgree what the study covers, who takespart and when the recommendation is due.4Gather evidenceInterview developers, operations, financeand the project manager. Keep facts andassumptions apart.5Rate and note risksMark each type as feasible, conditionalor not feasible, with one line ofreasoning.6RecommendShare a one-page summary with conditionsand ask for a go, conditional go or stopdecision.
A light process a business analyst can run in days or weeks, depending on the size of the decision.
Diagram in words
  • 1. Confirm problem and goal: Write the problem, who has it and what success looks like, in plain words.
  • 2. Agree options and rules: List two or three solutions, including doing nothing, and the rules a project must meet.
  • 3. Set study boundaries: Agree what the study covers, who takes part and when the recommendation is due.
  • 4. Gather evidence: Interview developers, operations, finance and the project manager. Keep facts and assumptions apart.
  • 5. Rate and note risks: Mark each type as feasible, conditional or not feasible, with one line of reasoning.
  • 6. Recommend: Share a one-page summary with conditions and ask for a go, conditional go or stop decision.

How feasibility findings feed the business case

A feasibility study and a business case are closely linked but not the same. The feasibility study asks can we do it? The business case asks should we invest in it, compared with the other things we could do? Often the feasibility findings become a section of the business case, or the evidence behind it.

  • Options: options that fail technical or schedule feasibility are dropped or reshaped before the business case compares them.
  • Costs and benefits: the economic analysis gives the business case its cost estimates, benefit assumptions and payback period.
  • Risks: every feasible with conditions finding becomes a named risk with an owner and a mitigation.
  • Scope: operational and technical limits shape what goes into the first release.
  • Recommendation: the business case repeats the go, conditional go or stop decision and explains why.

Later, the same assumptions help with benefits tracking. If the business case promised fewer errors or fewer repeat jobs, someone should check after go-live whether that really happened.

Worked example: delivery rescheduling at Marigold Logistics

Marigold Logistics is a fictional courier company. Customers often miss deliveries because they are not home. The sponsor wants a self-service page where customers can move their delivery to another day. You are the BA asked to check feasibility before a business case is written.

Facts gathered: Marigold has about 1,000 failed deliveries a month, and each redelivery costs about $5. The developers estimate a one-off build cost of $36,000, and the page will run on the existing hosting contract with no extra running cost. The team has 16 weeks: the busy festival season starts in week 17, and the sponsor wants the page live for all customers before then. Marigold's investment rule, agreed with the sponsor, is that a project must pay back its build cost within 3 years of go-live.

Checking technical and operational limits

Marigold Logistics, a fictional courier company: the BA checks technical and operational feasibility for a delivery rescheduling page.

  1. You The BA learner

    Mei, can the tracking system let customers change their own delivery date?

  2. Mei Lead developer

    Yes, there is an API for that. It can change the date, but not the address. Address changes would need a new integration, and that is a much bigger job.

  3. You The BA learner

    Sunil, if a customer changes the date late in the evening, can the drivers cope?

  4. Sunil Operations lead

    Not after 6 pm. That is when we lock the route plans for the next day. Any change before 6 pm the day before is fine.

  5. You The BA learner

    So only the date can change, and changes close at 6 pm the day before delivery. I will write both as conditions in the findings.

  6. Mei Lead developer

    Good. With that scope, three two-week sprints is a realistic estimate for the build.

The people and the company in this scene are fictional.

Two short questions uncover a scope limit and a business rule.
  • Technical: feasible with a limit. The tracking system API can change a delivery date but not an address, so address changes are out of scope.
  • Operational: feasible with a rule. Route plans are fixed at 6 pm the day before, so changes must close at that time.
  • Economic: feasible with a condition. If self-service prevents 30% of the 1,000 failed deliveries a month, that is 300 fewer redeliveries a month. 300 times $5 is $1,500 a month, or $18,000 a year. $36,000 divided by $18,000 a year gives a payback of 2 years from go-live, which is inside the 3-year rule.
  • Break-even check: to meet the 3-year rule, savings must be at least $12,000 a year ($36,000 divided by 3), which is $1,000 a month or 200 fewer redeliveries a month. That is a 20% reduction. At 15%, savings would be $9,000 a year and payback 4 years, which fails the rule.
  • Schedule: feasible. Weeks 1 to 6 are three two-week sprints, weeks 7 and 8 are UAT, and week 9 is go-live preparation, so the pilot launches at the start of week 10. A 4-week pilot in one city runs in weeks 10 to 13, and full rollout happens in week 14. Weeks 15 and 16 are buffer before the festival season starts in week 17.

Note what the deadline means. The festival date is about having the page live when failed deliveries matter most, not about paying back the build by then. Payback is counted from go-live. The calculation also uses the normal monthly volume, not the busier festival months, so the estimate is cautious.

The 30% figure is the weakest point, because it is an assumption, not a fact. So the recommendation is a conditional go: build the date-change feature only, run the one-city pilot first, and roll out to all cities only if the pilot city shows at least a 25% drop in failed deliveries compared with its usual month. The break-even point is 20%, so the gate is set 5 points higher. That margin allows for a pilot city that may perform better than the rest of the network. At 25%, savings would be 250 fewer redeliveries a month, $1,250 a month or $15,000 a year, and payback 2.4 years, still inside the rule. If the pilot misses the gate, the sponsor stops or rethinks the project before spending more.

One-page feasibility summary

Feasibility summary: delivery rescheduling

Technical: Feasible with a limit. The tracking API can change delivery dates, not addresses.1

Operational: Feasible with a rule. Changes close at 6 pm the day before delivery.2

Economic: Feasible if 30% holds. $36,000 build, $18,000 saved a year, 2-year payback against a 3-year rule.3

Schedule: Feasible. Build, UAT and prep in weeks 1 to 9, pilot weeks 10 to 13, rollout week 14, buffer weeks 15 and 16.4

Recommendation: Conditional go. Full rollout only if the pilot shows at least a 25% drop (break-even is 20%).5

  1. Scope set by a technical limit. The API changes dates only. Naming the limit early stops anyone promising address changes later.
  2. Operational rule. The 6 pm cut-off comes from how routes are planned. It becomes a business rule and later a test case.
  3. Payback against a threshold. 300 fewer redeliveries times $5 is $1,500 a month, or $18,000 a year. $36,000 divided by $18,000 is 2 years, inside the 3-year rule.
  4. Schedule with buffer. 6 weeks of sprints, 2 of UAT and 1 of prep fill weeks 1 to 9. The pilot runs weeks 10 to 13, rollout is week 14, and weeks 15 and 16 are buffer before the festival in week 17.
  5. Pilot gate with a margin. Break-even is a 20% drop: 200 fewer redeliveries, $12,000 a year. The 25% gate gives $15,000 a year and a 2.4-year payback, leaving room for an unrepresentative pilot city.
The summary the BA shares with the sponsor, with notes on why each line matters.

Common mistakes in feasibility studies

  • Testing only one option. Without do nothing or a smaller option, the sponsor has nothing to compare.
  • Calling something feasible without a yardstick. A payback period or a delivery date only means something next to an agreed limit. Ask the sponsor for the rule before you judge.
  • Setting a test gate exactly at break-even. A pilot is a small sample. If the gate sits right on the limit, a slightly lucky pilot can approve a project that fails at full scale. Leave a margin.
  • Mixing facts and assumptions. Label every estimate and say who gave it. Assumptions are where the risk lives.
  • Ignoring operational feasibility. A system that works technically but breaks the daily routine of the team will not deliver its benefits.
  • Over-precise numbers. Early estimates are rough. Use ranges or round figures instead of false accuracy.
  • Hiding bad news. Not feasible is a valid and useful result. It stops money being spent on the wrong thing.
  • Doing it alone. The BA guides the study, but developers, operations and finance must own their parts of the evidence.

Feasibility habits

Good habit

  • Compare at least two options, including doing nothing
  • Agree the approval rules with the sponsor before rating anything
  • Write each assumption next to the person who gave it
  • Set pilot gates with a margin above the break-even point

Risky habit

  • Present one favourite solution as the only choice
  • Call a result feasible without saying what it was measured against
  • Treat a developer's rough guess as a fixed quote
  • Leave conditions out of the summary to make it look cleaner
Small habits that make a feasibility study honest and useful.

Frequently asked questions

Is a feasibility study the same as a business case?

No. A feasibility study checks whether an idea can realistically work. A business case uses those findings to argue whether the company should invest in it, compared with other uses of its money and people. In smaller projects both may sit in one document, but they answer different questions.

Who does the feasibility study, the business analyst or the project manager?

It depends on the organisation. Often the BA leads the analysis and writes the findings, the project manager supplies schedule estimates, and the sponsor makes the decision. Developers, operations and finance provide evidence for their own areas.

How long does a feasibility study take?

It depends on the size and risk of the decision. A small internal change may need a few conversations and a one-page summary. A large system replacement may need several weeks of interviews, vendor conversations and cost modelling. Match the effort to the cost of getting the decision wrong.

Do agile teams still do feasibility studies?

Yes, usually in a lighter form. Teams may run a short discovery, a technical spike or a prototype to answer feasibility questions before committing to a larger backlog. The four types of feasibility still apply, even when the output is a short page instead of a formal report.

How can I practise feasibility analysis without a BA job?

Pick a simple idea, such as an online booking feature for a local business, and write the four feasibility findings with clear assumptions, an agreed decision rule and a recommendation. You can also practise on a fictional project, such as the business case stage of the BA Lab, and keep the result as a portfolio sample.

This article was written by an AI system and published automatically after automated accuracy, safety and quality checks. All companies, people and numbers in the examples are fictional. BA Mentorship does not issue professional certifications and cannot guarantee any job or interview outcome. Spot an error? Email our support team and we will check and correct it.

Key terms in this article

Browse the full glossary

CHECK BEFORE CONTINUING

Keep your work safe