Gap Analysis Skill
Purpose
Identify the difference (gap) between the current state (As-Is) and the desired future state (To-Be) to determine what actions, processes, or technologies are needed to bridge that gap.
When to Use
- Strategic planning
- Software migration/upgrades
- Process improvement initiatives
- Compliance audits
- Feature parity analysis (e.g., moving from Legacy to New System)
The Gap Analysis Process
1. Identify Current State (As-Is)
- What: How things work today.
- Sources: Documentation, interviews, observation, system data.
- Artifacts: Current process maps, system architecture diagrams, SWOT strengths/weaknesses.
- Questions:
- What is the current manual process?
- What are the pain points?
- What metrics are we hitting/missing?
2. Define Future State (To-Be)
- What: Where we want to be.
- Sources: Strategic goals, industry benchmarks, stakeholder vision.
- Artifacts: Future process maps, target architecture, KPIs.
- Questions:
- What does "good" look like?
- What are the automation targets?
- What functionality is mandatory?
3. Analyze the Gap
- Compare As-Is and To-Be directly.
- Characterize the gap:
- Process Gap: Missing steps, inefficient workflows.
- Technology Gap: System limitations, missing features, integration needs.
- Skill/People Gap: Training needs, resource shortages.
- Data Gap: Missing data fields, poor data quality.
4. Bridge the Gap (Action Plan)
- Define solutions to close each gap.
- Prioritize solutions.
- Estimate effort and impact.
Gap Analysis Matrix Template
| # |
Category |
Current State (As-Is) |
Future State (To-Be) |
Gap Description |
Action / Solution |
Priority |
| 1 |
Process |
Orders manually entered from email to ERP. |
Orders automatically synced from Web to ERP. |
No integration exists. Manual entry takes 15 mins/order. |
Implement ERP API integration. |
High |
| 2 |
Data |
Customer phone numbers stored in free text. |
Customer phone numbers validated and standardized (E.164). |
Data quality issue, unable to use SMS gateway. |
Data cleansing script + Validation on frontend. |
Medium |
| 3 |
Feature |
No guest checkout available. |
Guest checkout supported. |
Missing functionality causing 20% drop-off. |
Build guest checkout flow. |
High |
| 4 |
Skill |
Support team knows Tier 1 issues only. |
Support team handles Tier 2 issues. |
Knowledge gap. |
Train Lead Support agents on Tier 2 troubleshooting. |
Low |
Comparison Frameworks
1. SWOT Analysis (Current State Focus)
- Strengths: Internal positives.
- Weaknesses: Internal negatives (GAPS).
- Opportunities: External positives (Future State potential).
- Threats: External negatives.
2. McKinsey 7S Framework
Analyze gaps across:
- Hard Elements: Strategy, Structure, Systems.
- Soft Elements: Shared Values, Style, Staff, Skills.
3. Nadler-Tushman Congruence Model
Checks fit between Work, People, Structure, and Culture.
Output Artifacts
- Gap Analysis Document: Detailed report.
- Action Plan / Roadmap: Timeline of projects to close gaps.
- Business Case: Justification for the investment.
Tips for Success
- Be quantified: "Slow processing" is bad. "Processing takes 4 days vs target of 4 hours" is good.
- Focus on root causes: Don't just list symptoms.
- Validate: Confirm As-Is with users who do the work, not just managers.
References
- BABOK Guide - Strategy Analysis
- Business Capability Mapping
1---2name: gap-analysis3description: Conduct Current State vs. Future State analysis to identify gaps and define the roadmap for change4---56# Gap Analysis Skill78## Purpose9Identify the difference (gap) between the current state (As-Is) and the desired future state (To-Be) to determine what actions, processes, or technologies are needed to bridge that gap.1011## When to Use12- Strategic planning13- Software migration/upgrades14- Process improvement initiatives15- Compliance audits16- Feature parity analysis (e.g., moving from Legacy to New System)1718## The Gap Analysis Process1920### 1. Identify Current State (As-Is)21- **What**: How things work today.22- **Sources**: Documentation, interviews, observation, system data.23- **Artifacts**: Current process maps, system architecture diagrams, SWOT strengths/weaknesses.24- **Questions**:25 - What is the current manual process?26 - What are the pain points?27 - What metrics are we hitting/missing?2829### 2. Define Future State (To-Be)30- **What**: Where we want to be.31- **Sources**: Strategic goals, industry benchmarks, stakeholder vision.32- **Artifacts**: Future process maps, target architecture, KPIs.33- **Questions**:34 - What does "good" look like?35 - What are the automation targets?36 - What functionality is mandatory?3738### 3. Analyze the Gap39- Compare As-Is and To-Be directly.40- Characterize the gap:41 - **Process Gap**: Missing steps, inefficient workflows.42 - **Technology Gap**: System limitations, missing features, integration needs.43 - **Skill/People Gap**: Training needs, resource shortages.44 - **Data Gap**: Missing data fields, poor data quality.4546### 4. Bridge the Gap (Action Plan)47- Define solutions to close each gap.48- Prioritize solutions.49- Estimate effort and impact.5051## Gap Analysis Matrix Template5253| # | Category | Current State (As-Is) | Future State (To-Be) | Gap Description | Action / Solution | Priority |54|---|----------|-----------------------|----------------------|-----------------|-------------------|----------|55| 1 | **Process** | Orders manually entered from email to ERP. | Orders automatically synced from Web to ERP. | No integration exists. Manual entry takes 15 mins/order. | Implement ERP API integration. | High |56| 2 | **Data** | Customer phone numbers stored in free text. | Customer phone numbers validated and standardized (E.164). | Data quality issue, unable to use SMS gateway. | Data cleansing script + Validation on frontend. | Medium |57| 3 | **Feature** | No guest checkout available. | Guest checkout supported. | Missing functionality causing 20% drop-off. | Build guest checkout flow. | High |58| 4 | **Skill** | Support team knows Tier 1 issues only. | Support team handles Tier 2 issues. | Knowledge gap. | Train Lead Support agents on Tier 2 troubleshooting. | Low |5960## Comparison Frameworks6162### 1. SWOT Analysis (Current State Focus)63- **Strengths**: Internal positives.64- **Weaknesses**: Internal negatives (GAPS).65- **Opportunities**: External positives (Future State potential).66- **Threats**: External negatives.6768### 2. McKinsey 7S Framework69Analyze gaps across:70- **Hard Elements**: Strategy, Structure, Systems.71- **Soft Elements**: Shared Values, Style, Staff, Skills.7273### 3. Nadler-Tushman Congruence Model74Checks fit between Work, People, Structure, and Culture.7576## Output Artifacts77- **Gap Analysis Document**: Detailed report.78- **Action Plan / Roadmap**: Timeline of projects to close gaps.79- **Business Case**: Justification for the investment.8081## Tips for Success82- **Be quantified**: "Slow processing" is bad. "Processing takes 4 days vs target of 4 hours" is good.83- **Focus on root causes**: Don't just list symptoms.84- **Validate**: Confirm As-Is with users who do the work, not just managers.8586## References87- BABOK Guide - Strategy Analysis88- Business Capability Mapping
danhvb