How to Run a Gap Analysis That Produces Actionable Results

What is a gap analysis?

A gap analysis compares where an organisation is today (current state) with where it needs or wants to be (future state). The difference between the two is the gap. The gap analysis identifies what must change — in processes, systems, skills, or structure — to close that gap.

Step 1: Define the scope

A gap analysis can apply to a single process, a department, an entire organisation, or a technology landscape. The broader the scope, the less detailed each gap will be. For most projects, a focused gap analysis on a specific capability area is more useful than a broad organisational assessment.

Define the scope in terms of: which business functions are included; which time horizon applies (current vs 12 months vs 3 years); which stakeholders have input; and what outcome the gap analysis must support (a business case, a project brief, a technology strategy).

Step 2: Document the current state

The current state is what actually happens today — not what the process documentation says happens, and not what management believes happens. Walk the process with the people who do it. Measure where possible: cycle times, error rates, volumes, costs. Interview multiple levels of the organisation.

The current state assessment should document: what is working well (and must be protected), what is not working (and why), the metrics that describe current performance, and the root causes of the most significant pain points.

Step 3: Define the future state

The future state is the target — what good looks like. It should be defined in terms of outcomes, not features. "Customers can onboard in under 3 days" is a future state outcome. "We implement an automated onboarding portal" is a solution. Define the outcome first; the solution comes later.

The future state should be achievable within a realistic timeframe. If the future state is so ambitious that it requires three years and a complete transformation, define an interim future state that is achievable in 12 months and creates a platform for the longer-term vision.

Step 4: Identify and size the gaps

For each area in scope, compare the current state assessment against the future state definition. The gap is the difference. Describe each gap in specific, observable terms: "Current customer onboarding takes 14 days across 6 manual steps involving 3 departments. The target is 3 days across 2 automated steps with one human review."

Size each gap in terms of effort, cost, and complexity. A gap that requires significant technology change is more expensive and slower to close than a gap that requires a process change only.

Step 5: Prioritise the gaps

Not all gaps are equal. Prioritise using two dimensions: business impact (how much value does closing this gap deliver?) and feasibility (how easy is it to close, given available resources and constraints?). Gaps with high impact and high feasibility are your quick wins. Gaps with high impact and low feasibility are your strategic bets. Gaps with low impact in either direction are candidates for deferral.

Turning findings into action

A gap analysis that sits in a report is wasted effort. For each prioritised gap, define: the initiative that will close it, the owner of that initiative, the investment required, the expected timeline, and the metric that will confirm the gap is closed. This transforms a gap analysis from an assessment into a roadmap.