Глосарій
Gap Analysis
A method for finding the difference between what users want and what existing products deliver, so you can prioritize what to build or message next.
Gap analysis is the process of mapping unmet customer needs against the features, workflows, or outcomes offered by you and your competitors. In SaaS, it usually begins with review mining — clustering complaints, feature requests, and workarounds from G2, Capterra, Trustpilot, Reddit, and support tickets — then tagging each gap by frequency, severity, and how many competitors (if any) already solve it.
The deliverable is a prioritized list of opportunities: places where the category collectively underdelivers. Gaps that are common, painful, and unsolved by any competitor become roadmap candidates. Gaps that everyone already solves well become table stakes. Gap analysis is distinct from feature comparison: a feature comparison tells you what exists, a gap analysis tells you what should exist.
Why it matters
Teams that ship from internal opinion ship features nobody uses. Gap analysis grounds the roadmap in real user pain — giving product managers evidence to defend priorities and say no to vanity features.
Related terms
Competitive Analysis
A structured evaluation of competing products, companies, or strategies used to understand the market and sharpen your own positioning.
Feature Comparison Matrix
A structured grid that lines up you and your competitors against a list of features to highlight parity, gaps, and differentiators.
Voice of Customer
The disciplined capture and synthesis of customer feedback across every channel, used to drive product and GTM decisions.
Jobs to be Done
A theory that customers "hire" products to make progress on a specific job, not because of demographics or features.
Review Sentiment Analysis
The practice of extracting structured insight — positive, negative, thematic — from unstructured customer reviews.