Gap analysis

Gap analysis is the practice of comparing where something is today with where it needs to be, then naming the difference clearly enough to act on it. In operations, that usually means looking at a process, team, system, or performance metric and asking what is missing, weak, delayed, undocumented, or under-resourced.

A good gap analysis turns a vague complaint into a concrete decision: which gap matters enough to close, what closed would look like, and what work has to change to get there.

Gap analysis gives teams a structured way to avoid vague improvement work. Structured assessment can identify disparities and focus improvement efforts. ¹

A skill gap may need training. A process gap may need a clearer workflow. A documentation gap may need a guide, checklist, or example. A capacity gap may need staffing or prioritization. Treating all of them as the same problem usually creates busywork.

A useful gap analysis has four parts: current state, desired state, gap, and action. The common failure is making the desired state too abstract. Better documentation is not a target; a clear, observable standard is.

Ground the analysis in examples, artifacts, data, or observed work; CDC guidance similarly emphasizes using data and benchmarks to understand and improve performance. ²

Imagine an operations manager reviewing new-hire onboarding. The target is that every new employee can complete first-week setup without asking a manager for repeated instructions. The current state is scattered: HR has one checklist, IT sends separate setup steps, and team leads keep their own notes.

• The source-of-truth gap: no one knows which checklist is current.
• The sequence gap: employees receive some steps before they have the right account access.
• The ownership gap: no one is accountable for updating the process after tools change.

Those gaps point to different actions. A single onboarding guide may solve the source-of-truth issue, a first-week timeline the sequence issue, and an assigned process owner the maintenance issue.

Do not turn gap analysis into a complaint inventory: rank gaps by consequence, frequency, and fixability, and judge improvement strategies against evidence and local context. ³

Other common mistakes are skipping the target state and naming symptoms instead of causes. Too many support questions may be a symptom; the underlying gap may be missing setup steps, unclear product language, or help written for the wrong audience.

Pick one workflow, define what a competent person should be able to do after reading the documentation, then compare that target against the current materials. If the evidence is weak, the next step is observation, not rewriting everything.

Gap analysis diagnosticmarkdown

Copy to AI

ChatGPTClaudeGeminiPerplexity

Paste into ChatGPT, Claude, Gemini, or Perplexity and personalize for your use case

## Gap analysis diagnostic

**Glossary term:** Gap analysis
**Source:** Trails Glossary — trails.so/glossary/gap-analysis

---

### 01. Prompt

"For [process], the current documentation helps [audience] do [task]. The target state is that they can do [task] without [avoidable dependency or failure]. Today, the biggest gap is [missing information, unclear sequence, outdated step, owner ambiguity, or exception path]. Evidence: [example, ticket, audit result, repeated question, or observed handoff]. The smallest useful fix is [specific documentation or workflow change]."

Trails is useful when the gap is caused by unclear, inconsistent, or stale process documentation. A team can capture a workflow as someone performs it, turn it into a polished step-by-step guide, and create an AI-narrated video version for training or sharing.

What is the purpose of gap analysis?

It defines the difference between the current and desired state so a team can choose the right improvement work.

Is gap analysis only used for business strategy?

No. It can be used for strategy, operations, training, documentation, compliance readiness, customer support, or any situation with a target state.