A gap list isn't a plan
Most gap analyses stop at the comparison table: current state, desired state, done. What actually gets something closed is knowing which gaps are critical and cheap to fix now, which need a business case first, and which can genuinely wait — and that sequencing work is where most gap analyses run out of time.
What it does
- Confirms the comparison dimension first. Capability, process, data, technology, compliance, or skills — and states the target criteria it inferred if the desired state was vague.
- Rates every gap. Type, severity (critical/major/minor), effort (H/M/L), and a one-line closure action — not a full solution design, just what closing it requires.
- Groups gaps into themes. Three to five clusters, each with a one-sentence "what this really means" so the pattern isn't lost in the row-by-row detail.
- Sequences the plan. Close now (critical, low effort), plan (critical or major, high effort), defer (minor), accept (with the stated reason).
- Never assumes an unknown current state. Marked UNKNOWN, and the assessment itself becomes an action.
Example
Illustrative, not a real client assessment.
Current: approvals happen over email, no audit trail. Desired: every approval logged with who, when, and why, for the new compliance requirement effective Q3.
GAP: No audit trail of who approved what, or when. Type: process/technology. Severity: Critical (compliance deadline). Effort: M. Closure action: add an approval log field to the existing tool before Q3. CLOSE NOW: this gap — critical, moderate effort, hard deadline.
How it works with Claude
Install once in Claude, roughly 10 minutes.
Describe the current state and the target you're comparing to.
Get the gap table, the themes, and a sequenced closure plan back.
FAQs
What is a gap analysis in business analysis?
A structured comparison between where things stand today and where they need to be, across dimensions like process, technology, data, people or compliance, that makes the distance between the two explicit rather than assumed.
What if the current state isn't fully known?
A good gap analysis marks it UNKNOWN and treats getting an answer as an action in its own right, rather than assuming the best or worst case to fill the blank.