What is a Gap Analysis in Business Analysis?
Gap analysis is the structured comparison of an organization's current operational state against its desired future state. The primary output of this technique is a defined list of changes — in processes, technology, capabilities, or organizational structure — necessary to transition the business to its target performance level.
Without a formal gap analysis, project teams often make incorrect assumptions about their starting point, resulting in significant rework and misaligned goals.
What are the Main Focus Areas of a Gap Analysis?
When performing a gap analysis under professional standards, the investigation covers four core dimensions of the organization:
| Focus Area | Description | Practical Question to Ask |
|---|---|---|
| Capabilities | The missing skills, tools, methodologies, or processes. | What capabilities must the team acquire to support the new product? |
| Performance | The delta between current metrics and future targets. | Why is our current throughput at 80% of our desired capacity? |
| Data & Systems | Outdated, absent, or disconnected software and databases. See our guide on sourcing and validating data. | What data integrations are missing between the CRM and the new billing system? |
| Compliance | Gaps in regulatory, safety, security, or legal requirements. | What changes are needed to make the legacy database fully GDPR compliant? |
How is Gap Analysis Represented in BABOK and PMBOK (PMP)?
For professionals preparing for exams like the CBDA or CBAP, gap analysis is a core technique referenced across international standards:
- In the BABOK Guide v3 (IIBA): Gap analysis is a primary technique in Chapter 6: Strategy Analysis. It acts as the bridge connecting Task 6.1 (Analyze Current State) and Task 6.2 (Define Future State) — concepts also foundational to framing and validating research questions in data initiatives. The "gap" represents the explicit delta that informs the change strategy. It also appears in Chapter 8: Solution Evaluation when comparing actual solution performance against business objectives.
- In the PMBOK Guide (PMI / PMP): Project managers utilize gap analysis during scope definition and integration management. It helps determine the variance between baseline plans and project execution, ensuring the project scope directly addresses business needs.
Real-World Example: Gap Analysis in Action
When I joined the LPT project, one of the first tasks I performed was a lightweight gap analysis. The team was struggling with delivery timelines. I mapped the current state (undocumented processes, manual testing bottlenecks) against the future state requested by the client (automated pipelines, transparent reporting).
The resulting gap analysis pointed directly to the exact interventions that mattered. Instead of guessing where the bottlenecks were, we focused resources on automating the regression suite, which resolved the primary delivery gap.
Exam Tip: Gap Analysis vs. Root Cause Analysis (RCA)
🎓 Exam Tip for CBAP & PMP: Do not confuse Gap Analysis with Root Cause Analysis (RCA).
- Gap Analysis identifies WHAT is missing between your current state and the future state.
- Root Cause Analysis (RCA) identifies WHY that gap exists in the first place (using tools like Fishbone diagrams or the 5 Whys).
A successful change strategy always pairs these two: Gap Analysis defines the scope of change, while RCA ensures you are fixing the underlying problem rather than the symptom.
Explore more Business Analysis resources or read our deep dives into other BABOK techniques.