Gap Analysis Technique - TOGAF 10 Foundation Guide

Gap Analysis Technique - Complete Guide

Understanding Gap Analysis in TOGAF

Gap Analysis is a fundamental technique within the TOGAF (The Open Group Architecture Framework) ADM (Architecture Development Method) that identifies and documents the differences between the current state (baseline architecture) and the desired future state (target architecture). This technique is essential for understanding what needs to change, what needs to be built, and what needs to be modified to achieve organizational transformation goals.

Why Gap Analysis is Important

Organizational Alignment: Gap Analysis ensures that proposed architectural changes directly support business objectives and strategic goals. It bridges the gap between business strategy and technical implementation.

Resource Planning: By identifying specific gaps, organizations can allocate resources more effectively. It helps determine what investments are needed, which systems require modernization, and where new capabilities must be developed.

Risk Management: Understanding gaps helps identify risks associated with transformation. It reveals dependencies, potential conflicts, and areas where change resistance might occur.

Change Management: Gap analysis provides a clear roadmap for change, helping stakeholders understand what will change and why. This transparency supports smoother change adoption.

Prioritization: Not all gaps are equally important. Gap analysis helps prioritize which gaps to address first based on business impact, feasibility, and strategic importance.

Measurement and Validation: Gap analysis provides metrics to measure progress toward the target architecture. Organizations can track whether they are successfully closing identified gaps.

What is Gap Analysis?

Gap Analysis is a structured technique for comparing an organization's current state architecture with its target state architecture across multiple domains. The analysis identifies the gaps (differences) that exist and must be addressed through a transformation program.

The Three Core Elements:

1. Baseline Architecture: The as-is state representing the current architectural situation. This includes existing business processes, systems, technologies, organizational structures, and information flows.

2. Target Architecture: The to-be state representing the desired future architectural situation. This reflects the outcomes desired when the architecture work is complete and aligns with business strategy.

3. Gap: The difference between baseline and target. Gaps can involve new capabilities needed, systems to be decommissioned, changes to business processes, technology upgrades, organizational restructuring, or data management improvements.

Types of Gaps:

• Capability Gaps: Missing or inadequate business capabilities that need to be developed or acquired
• System Gaps: Applications and systems that need to be built, replaced, or retired
• Data Gaps: Data structures, information management, or data quality issues that need addressing
• Technology Gaps: Technology infrastructure, platforms, or tools that require updates or replacement
• Process Gaps: Business processes that need redesign, automation, or improvement
• Organizational Gaps: Staffing, skills, roles, or organizational structure changes required

How Gap Analysis Works

Step 1: Establish the Baseline Architecture

The first step is to clearly document the current state. This involves:

• Documenting existing business capabilities and processes
• Mapping current applications and systems
• Identifying existing technology infrastructure
• Understanding organizational structure and current roles
• Documenting current data flows and information management
• Recording existing standards and compliance requirements

Step 2: Define the Target Architecture

Next, define the desired future state by:

• Identifying business capabilities needed to achieve strategic goals
• Designing future business processes
• Planning the application portfolio for the future state
• Defining technology strategy and infrastructure requirements
• Outlining future organizational structure
• Planning future data management and information flows

Step 3: Identify Gaps

Compare baseline and target architectures systematically:

• Analyze each architectural domain (business, data, application, technology)
• Identify what exists in target but not in baseline (additions needed)
• Identify what exists in baseline but not in target (things to remove or retire)
• Identify what exists in both but requires change (modifications needed)
• Document gaps with sufficient detail for subsequent planning

Step 4: Prioritize Gaps

Not all gaps have equal importance. Prioritization typically considers:

• Business impact and strategic importance
• Technical complexity and feasibility
• Cost and resource requirements
• Dependencies between gaps
• Timeline and urgency
• Risk considerations

Step 5: Document Gap Analysis Results

Create comprehensive documentation including:

• Gap statements describing each identified difference
• Baseline and target state descriptions
• Impact analysis for each gap
• Prioritization rationale
• Mapping of gaps to architecture work streams
• Recommendations for gap resolution

Gap Analysis in the ADM Phases

Phase A (Architecture Vision): Identifies high-level gaps between current and desired business outcomes.

Phase B (Business Architecture): Analyzes gaps in business capabilities, processes, and organizational structures.

Phase C (Information Systems Architectures): Identifies gaps in data and application architectures.

Phase D (Technology Architecture): Analyzes gaps in technology infrastructure, platforms, and tools.

Phase E (Opportunities and Solutions): Translates gaps into specific transformation initiatives and projects.

Gap Analysis Matrices and Tools

Gap Analysis Matrix: A table comparing baseline and target across dimensions:

Impact Analysis: Assesses the consequences of each gap and its resolution. Considers business, technical, and organizational impacts.

Dependency Mapping: Shows how gaps relate to and depend on one another, helping sequence resolution activities.

Best Practices for Gap Analysis

1. Involve Stakeholders: Include business owners, technical experts, and affected parties in gap identification. Multiple perspectives ensure comprehensive analysis.

2. Be Specific and Measurable: Gaps should be clearly defined with measurable criteria, not vague generalizations.

3. Document Assumptions: Record assumptions about baseline and target states. These may change as transformation progresses.

4. Consider Multiple Domains: Analyze gaps across business, data, application, and technology domains. Don't focus only on technology.

5. Link to Business Value: Connect each gap to business outcomes and strategic objectives. This justifies the effort to close gaps.

6. Review and Validate: Have stakeholders validate identified gaps. Ensure baseline and target descriptions are accurate.

7. Plan for Change: Gap analysis should feed into change management planning and implementation roadmapping.

Common Challenges in Gap Analysis

Incomplete Baseline Understanding: Organizations sometimes lack clear documentation of their current state. Solution: Conduct thorough discovery and documentation work.

Unclear Target Definition: If the target architecture is vague, gaps cannot be clearly identified. Solution: Develop detailed target architectures before analyzing gaps.

Too Many Gaps: Large transformation efforts may identify hundreds of gaps. Solution: Apply structured prioritization and organize gaps into coherent work streams.

Gaps Versus Solutions: Confusing the identification of gaps with proposing solutions. Solution: Keep gap analysis focused on identifying differences, not solving them.

Stakeholder Disagreement: Different stakeholders may have different views of gaps. Solution: Use facilitated workshops and documented criteria for gap identification.

Exam Tips: Answering Questions on Gap Analysis Technique

Tip 1: Understand the Definition

Gap Analysis compares baseline (as-is) and target (to-be) architectures to identify differences that must be addressed. Be prepared to define it clearly and concisely. Emphasize that it's about identifying what needs to change, not how to change it.

Tip 2: Know the Purpose and Value

Gap analysis is not just a mechanical comparison. Understand why it matters: it drives prioritization, supports resource planning, manages risk, and ensures alignment with business strategy. Exam questions often test whether you understand the why behind the technique.

Tip 3: Remember the Three Components

Any gap analysis discussion should reference: baseline architecture, target architecture, and the gap itself. When answering questions, explicitly mention these three elements. Example answer structure: "The baseline shows X, the target requires Y, therefore the gap is Z."

Tip 4: Know the Types of Gaps

Be familiar with gap types: capability gaps, system/application gaps, technology gaps, data gaps, process gaps, and organizational gaps. Exam questions may ask you to classify a specific gap or identify which type is being described.

Tip 5: Understand When Gap Analysis Occurs

Gap analysis spans multiple ADM phases. However, formal gap analysis typically occurs in the architectural design phases (B, C, D) and becomes concrete in the "Opportunities & Solutions" phase (E). Questions may ask where in the ADM gap analysis is most critical or where it's conducted.

Tip 6: Link to Implementation

Understand that gap analysis feeds into project and portfolio planning. Questions may ask how gaps translate into initiatives, roadmaps, or project portfolios. The connection between gap analysis and implementation planning is important.

Tip 7: Prioritization is Key

Gap analysis itself is just identification; prioritization is crucial. Be prepared to discuss what factors influence prioritization: business impact, cost, complexity, dependencies, risk, and timeline. Exam questions often test whether you know that all gaps must be prioritized.

Tip 8: Multiple Perspective Questions

Exam questions may ask about gap analysis from different viewpoints:

• Business perspective: How does gap analysis support business transformation?
• Technical perspective: What technical gaps need to be addressed?
• Change perspective: How does gap analysis support change management?
• Planning perspective: How does gap analysis inform the roadmap?

Be ready to address any of these angles.

Tip 9: Distinguish from Other Techniques

Gap analysis is different from:

• Architecture Views: Which describe what is/will be
• Stakeholder Analysis: Which identifies affected parties
• Risk Assessment: Which identifies threats and vulnerabilities
• Capability Modeling: Which describes what the organization can do

Questions may ask you to differentiate gap analysis from these related techniques.

Tip 10: Sample Question Patterns

Be prepared for questions like:

• "What is the primary purpose of gap analysis?" - Answer: Identify differences between as-is and to-be architectures that must be addressed
• "In which ADM phases is gap analysis conducted?" - Answer: Primarily B, C, D with refinement in E
• "What should gap analysis include?" - Answer: Multiple architectural domains, clear baseline/target definitions, prioritization, and impact analysis
• "How are gaps prioritized?" - Answer: By business impact, technical feasibility, cost, dependencies, risk, and timeline
• "What is a gap versus a solution?" - Answer: A gap is a difference that exists; a solution is how you address it
• "How does gap analysis support the roadmap?" - Answer: By identifying what needs to change and in what priority order

Tip 11: Use Precise Terminology

In exam answers, use TOGAF terminology precisely:

• Use "baseline" not "current" or "existing"
• Use "target" not "desired" or "future"
• Use "gap" not "issue" or "problem"
• Use "gap analysis" not "gap assessment" or "gap identification"

This demonstrates mastery of the framework.

Tip 12: Be Comprehensive but Focused

In essay or scenario questions, demonstrate breadth of knowledge (multiple domains, prioritization, ADM phases) but keep your answer focused on the question asked. Don't just list everything you know about gap analysis; answer specifically what's being asked.

Tip 13: Relate to Business Outcomes

When answering questions about gap analysis, connect it to business value and outcomes. Don't treat it as a purely technical exercise. Mention how it supports strategy, enables change, and guides investment decisions.

Tip 14: Practice with Scenarios

Exam questions often present scenarios. Practice with examples like:

"A company wants to migrate from on-premise systems to cloud. What gaps might gap analysis identify?"

Answer approach: Consider capability, system, technology, data, process, and organizational dimensions. Explain how each type of gap would be identified and why it matters.

Tip 15: Know the Limitations

Be aware that gap analysis:

• Requires clear baseline and target (if these are undefined, gap analysis is difficult)
• Identifies what needs to change, not how to change it
• Can identify hundreds of gaps; prioritization is essential
• Must be supported by stakeholder validation

Questions may test whether you understand these constraints.

Quick Review Checklist

Before the exam, ensure you can answer these questions:

• Can you define gap analysis in one sentence?
• Do you understand the three components (baseline, target, gap)?
• Can you name at least four types of gaps?
• Can you explain why gap analysis is important?
• Do you know which ADM phases conduct gap analysis?
• Can you describe the gap analysis process (5+ steps)?
• Do you understand what factors influence prioritization?
• Can you distinguish gap analysis from other architecture activities?
• Can you relate gap analysis to business outcomes?
• Do you know how gap analysis feeds into roadmapping and planning?

If you can confidently answer these questions, you're well-prepared for gap analysis questions on the TOGAF 10 Foundation exam.