Gap Analysis Process

Gap analysis identifies where the blue book does not yet support the work teams are actually doing. Run it after major engagements and during planned content reviews.

Inputs

Use:

• Engagement retrospectives.
• Questions repeatedly asked by clients.
• Support or delivery blockers.
• Incident and audit lessons.
• Pages with heavy use or no use.
• Search terms with poor results.
• New platform or regulatory requirements.

Process

Prioritization

Prioritize gaps that:

• Reduce delivery or production risk.
• Are asked about repeatedly.
• Support common engagement scenarios.
• Clarify decision-making for stakeholders.
• Improve onboarding for new consultants.
• Prevent security, compliance, or privacy mistakes.

Done criteria

A gap is closed when the content is published, linked from the right paths, validated by someone who would use it, and included in the appropriate review cadence.

Watchouts

• A long page is not automatically a closed gap.
• Search and navigation matter as much as content volume.
• Repeated questions may indicate unclear structure, not missing pages.