Gap

Intro

A gap describes the difference between two states, often baseline and target architecture. It matters because gap analysis identifies work needed to reach desired outcomes.

Key points:

• Frames changes in capabilities, processes, or technologies.
• Supports planning, prioritization, and risk management.
• Common use cases: roadmap definition (EA), process improvement (BPM), tech refresh planning.
• Pitfall: vague gaps without quantified measures or owners.

Examples:

• Baseline lacks API gateway; target requires secure APIs.
• Current process cycle time exceeds the target SLA by 30%.
• Data quality gaps relative to governance standards.

In practice:

Document gaps with metrics, root causes, and actions; align with a delivery roadmap and governance checkpoints.

Related terms: baseline; target-architecture; roadmap

FAQs:

Q: What makes a good gap statement?
A: Clear current vs. target metrics, impact, and accountable owner.

Q: How are gaps prioritized?
A: By business value, risk, dependencies, and effort.

‍