Unmet Customer Needs Analysis Template

A minimum of 10 interviews in your target segment gives you enough data to identify patterns. Below 10, you risk building on coincidence rather than signal. At 15-20 interviews, patterns stabilize and you can assign frequency counts with confidence. See the [Product Discovery Handbook](/discovery-guide) for interview methodology.

A need describes what the customer is trying to accomplish and why it matters. A feature request describes a specific implementation. "I need to share project status with executives" is a need. "Add a PDF export button" is a feature request. Multiple features can address the same need. Always dig past the request to the underlying need by asking "What are you trying to accomplish?" and "What would change for you if this were solved?"

Use customer survey data when possible. Ask customers to rate "How important is [need] to your success?" (1-10) and "How well does your current tool handle [need]?" (1-10). If survey data is not available, use interview evidence and support ticket volume as proxies. Have 2-3 team members score independently and average the results to reduce individual bias.

Include them in the inventory (Part 2) for completeness, but they will naturally score low on frequency and likely low on the opportunity matrix. A single mention could be an outlier or it could be the first signal of an emerging need. Flag it and watch for additional evidence in future interviews. If it reappears, elevate it.

Quarterly for fast-moving markets (SaaS, consumer tech). Every 6 months for slower markets (enterprise, regulated industries). Major events (new competitor launch, significant product release, market shift) warrant an immediate refresh. Needs that were low priority 6 months ago may become urgent when competitive dynamics change. ---