Gap Analysis vs. Feasibility Study: What’s the Difference, What They Actually Tell You (and Why You Need Both)?

Technology Roadmap

A gap analysis and a feasibility study solve two different problems, even when they are tied to the same "business problem". A gap analysis begins with a summary of your current state, your desired future state, and the specific gaps between the two. It provides clarity on the movement and changes needed. A feasibility study can begin with the gap analysis, analyzing what it takes to make the changes successfully. A feasibility study asks the following questions:

• How realistic is it to close that gap, and at what cost?
• What resources are needed?
• What tools will you need to engage?

We use both gap analyses and feasibility reviews when developing a client's technology roadmap. Each provides a different perspective and delivers the greatest value when used together, complementing one another rather than being viewed as substitutes.

Jump to What they tell you Our process When you need them FAQ

60 Seconds on Gap Analysis vs. Feasibility Studies

A gap analysis and a feasibility study answer two different questions, in a specific order. The gap analysis names what's missing between your current and future state; the feasibility study evaluates how realistic it is to close that gap, including the resources and tools it takes.

In other words, the gap analysis identifies where change is needed, while the feasibility study evaluates what it will take to make that change successful. Used together, they feed directly into a technology roadmap.

Featured: Holly Clark at Business Consulting Leader.

What Do Gap Analysis and Feasibility Studies Tell You?

They answer two different questions, in a specific order.

Gap Analysis

What's actually missing

A gap analysis establishes a clear understanding of where the organization is today and where it wants to go.

• Defines the current state: how processes, systems, and technology operate today
• Defines the future state: what the organization is working toward and what success should look like
• Names the specific gap between the two
• Answers: "What's missing between where we are and where we want to be?"

Feasibility Study

How realistic closing it is

A feasibility study builds upon the identified gap and evaluates what it will realistically take to close it.

• Looks at the named gap: uses the desired outcome as the basis for evaluating potential solutions
• Evaluates required resources: considers the people, expertise, budget, effort, and time needed
• Identifies technology requirements: determines which existing or new systems, tools, integrations, or capabilities are needed
• Considers practical constraints: evaluates dependencies, risks, timing, and other factors that could influence the approach
• Answers: "What will it realistically take to get there?"

1. Gap AnalysisCurrent state, future state, and the gap between them get defined.

→

2. Feasibility StudyThe gap gets tested against real resources, tools, and timeline.

→

3. Technology RoadmapBoth feed directly into the plan for closing the gap.

This is exactly what our Feasibility & Gap Analysis service is built around. See How It Works

Our Process

Six steps, from goals to a purchase-ready plan.

1Identify the goals

We start by identifying the implementation or optimization goals driving the conversation, so the analysis has a clear target from the outset.

2Understand the current state

A full understanding of current processes and requirements gets documented, the baseline everything else gets measured against.

3Map the future state

We help construct the desired future state, mapping out the new processes and workflows the business is working toward.

4Identify the technology needed

The specific features and technology needed to support that future state get identified, tied directly to the gap rather than a generic feature list.

5Identify the gaps and a plan to close them

This is the gap analysis itself: naming exactly what's missing between current and future state, and drafting a plan to address it.

6Develop the purchase and implementation strategy

This is where feasibility gets tested directly: what it actually takes, in resources and tools, to execute the plan, before any purchase decision gets made.

When You Need These Tools

1

You're evaluating a new ERP or major feature and the sales process hasn't dug deep enough to confirm fit

2

You know something isn't working, but can't name exactly what's missing

3

Leadership wants a realistic resource and timeline estimate before approving budget

4

You're building a multi-year technology roadmap and need to know what's actually achievable first

5

A previous purchase didn't deliver what was expected, and you want to avoid repeating that

Related Reading

Planning

7 Critical Components of an Effective ERP Feasibility Study

Implementation

ERP Isn't All or Nothing: Smart Phased Rollouts Protect Your Project

Strategy

What Is Strategic Technology Planning?

Service

Functional Specification

Frequently Asked Questions

What's the difference between a gap analysis and a feasibility study?

A gap analysis identifies what's missing between your current state and your future state. A feasibility study takes that gap and evaluates how realistic it is to close it, including the resources and tools it will take.

Which comes first, gap analysis or feasibility study?

Gap analysis comes first. You can't realistically assess feasibility until you know exactly what gap you're trying to close.

Do I need both, or just one?

Ideally both. A gap analysis without a feasibility study leaves you with a wish list and no sense of what it actually takes to get there. A feasibility study without a gap analysis has nothing concrete to evaluate in the first place.

How long does a gap analysis or feasibility study take?

It depends on how many processes and systems are in scope. Either way, it's a fraction of the time a misaligned purchase or implementation costs to unwind later.

What happens after the feasibility study is done?

Its findings feed directly into the purchase and implementation strategy, and often into a broader technology roadmap if the gap is part of a larger multi-year plan.

Know What's Missing. Know What It Takes to Fix It.

We'll help you name the gap and pressure-test how realistic it is to close, before you spend a dollar on the wrong solution.

Get Pricing Talk to Our Team