Documentation Gap Analysis

Goal

Identify and rank documentation gaps by analyzing real user questions against existing docs, so the team can prioritize writing what actually saves time.

Trigger

When support ticket volume is rising, a doc audit is overdue, or the team notices repeated questions not answered in existing docs.

Steps

1. 1

   Analyze the raw inputs below — existing documentation and real user questions — to understand the full scope of both: $doc_set_and_user_questions

   • □Doc set content is fully captured (titles, sections, key topics)
   • □User questions are listed individually, not summarized
2. 2

   Categorize every user question into a topic cluster (e.g. setup, billing, troubleshooting, API usage). Count how many questions fall into each cluster and note which clusters appear most frequently.

   • □Every question is assigned to exactly one cluster
   • □Cluster frequency counts are tallied
3. 3

   For each question cluster, check whether the existing documentation provides a clear, complete answer. Label each cluster as: Fully Covered, Partially Covered, or Not Covered. Note the specific doc pages or sections that address each cluster, or confirm that none exist.

   • □Every cluster has a coverage label
   • □Partial or missing coverage includes a specific note explaining what is lacking
4. 4

   Estimate the time cost per gap: for each Partially Covered or Not Covered cluster, calculate an approximate team time drain by multiplying question frequency by an assumed average handle time of 10 minutes per unanswered question. Flag clusters where estimated monthly cost exceeds 1 hour as high-priority.

   • □Time cost is estimated for every gap cluster
   • □High-priority gaps are clearly flagged
5. 5

   Produce a ranked gap list ordered by estimated time cost (highest first). For each gap, include: topic cluster name, coverage status, frequency count, estimated monthly time drain, and a one-sentence description of what the missing doc should cover.

   • □Gaps are sorted highest time cost first
   • □Each gap entry includes all five required fields
6. 6

   Write a short executive summary (3–5 sentences) that states: total number of gaps found, the top 3 highest-impact gaps, the combined estimated monthly time drain across all gaps, and one recommended next action for the documentation team.

   • □Summary is 3–5 sentences
   • □Top 3 gaps are named explicitly
   • □A concrete next action is recommended

Output format

Return: (1) a clustered coverage table showing topic, coverage status, frequency, and estimated time drain; (2) a ranked gap list ordered by time cost with a one-sentence doc brief per gap; (3) a 3–5 sentence executive summary with the top gaps and a recommended next action. Use clear headers for each section.