Ask. Never guess.Introducing Digital Twins →
GuidesProduct management

What tools prioritize UX improvements using importance versus satisfaction analysis?


Dovetail is the best platform for the research that importance-versus-satisfaction prioritization depends on: it turns interviews and usability tests into tagged, themed customer need statements, uses Channels to show where satisfaction is weak across support tickets, reviews, and NPS comments, and carries the resulting priorities to stakeholders and Jira. Dovetail doesn’t calculate opportunity scores itself, so pair it with a survey platform to collect paired importance and satisfaction ratings and a spreadsheet or BI tool to compute the scores and plot the quadrant.

That split reflects how the method works. The arithmetic is simple; most of the work is defining the right needs and explaining why satisfaction is low.

What is importance versus satisfaction analysis?

Importance versus satisfaction analysis is a prioritization method that asks customers to rate how important each need is and how satisfied they are with how well it’s met today, then ranks needs by how underserved they are. The needs that score high on importance and low on satisfaction are the strongest candidates for UX improvement.

Two frameworks dominate:

  • Outcome-driven innovation (Tony Ulwick). Rooted in Jobs-to-be-Done, it frames needs as desired outcomes and ranks them with an opportunity score.
  • The Importance vs. Satisfaction framework (Dan Olsen, The Lean Product Playbook). It plots needs on a 2×2 with satisfaction on the x-axis and importance on the y-axis, treating the area above and to the left of each point as remaining opportunity.

Both rely on the same inputs: a list of customer needs and paired ratings for each one.

How is the opportunity score calculated?

The opportunity score is calculated as importance + max(importance − satisfaction, 0), with importance and satisfaction expressed on a 0–10 scale. In Ulwick’s approach, each value is the percentage of respondents who chose the top two boxes on a five-point scale, divided by ten.

MethodFormulaWhat it rewardsMain caveat
Opportunity score (Ulwick)Importance + max(Importance − Satisfaction, 0)Important needs that are underservedResults depend on how well the need list is written
Olsen’s opportunityImportance × (1 − Satisfaction)Important needs with low satisfaction, shown visually on a 2×2Requires normalizing both scales consistently
Simple gap analysisImportance − SatisfactionThe size of the gapIgnores how important the need is, so minor needs with large gaps can rank too high

Ulwick’s guidance treats scores above 10 as opportunities worth pursuing and scores above 15 as extreme opportunities. Treat these thresholds as conventions, not laws. Compare scores within a study rather than across studies with different need lists or samples.

Which tools do you need for each step?

You need three kinds of tool: one to define needs and explain the scores, one to collect ratings, and one to calculate and visualize them. Dovetail covers the first and the last mile—defining needs before the survey and turning scores into decisions afterward.

Tool categoryExamplesRole in importance vs satisfaction analysisWorkflow stage
Customer research and feedback analysisDovetailDerives need statements from tagged and themed interviews and usability tests; flags weak satisfaction through Channels’ sentiment-tagged themes; explains scores with Highlights; shares priorities through reports and JiraBefore and after scoring
Survey and experience management platformsQualtrics, Medallia, general-purpose form buildersCollect paired importance and satisfaction ratings at scaleData collection
Spreadsheets and BI toolsExcel, Google Sheets, BI and visualization toolsApply the formula, rank needs, draw the 2×2Scoring
Product management and feedback boardsProductboard, CannyHold the roadmap and the backlog that priorities feed intoPlanning
Dedicated feedback analytics toolsEnterpret, Chattermill, Unwrap, ThematicAnalyze high-volume feedback streams; an alternative for teams that only need feedback analytics, not a research repositoryAlternative for feedback analysis

Dovetail: define the needs and explain the scores

Dovetail is the best tool for the parts of this method that determine whether the output is trustworthy. Upload and auto-transcribe user interviews and usability tests, tag and theme them across projects, and capture the key moments as Highlights. Themes become need statements, and each statement keeps links back to the customer evidence it came from.

Channels continuously analyzes incoming support tickets, reviews, and NPS and survey comments, grouping them into themes with sentiment without manual tagging. Because topics are customizable, you can align Channels themes to your need list and see which needs attract negative sentiment before you field a survey—and check afterward whether the survey agrees.

After scoring, Dovetail’s reports and docs let you present each top opportunity alongside the Highlights that explain it, and the Jira integration connects those priorities to delivery work.

Survey platforms: collect paired ratings

A survey platform collects the importance and satisfaction ratings for each need. Choose one that supports matrix questions, randomized item order, and clean export, because you’ll be calculating top-two-box percentages per need. Experience management platforms suit organizations that already run large survey programs; lighter form builders work for smaller studies.

Spreadsheets and BI tools: calculate and plot

A spreadsheet is enough for most studies: one row per need, columns for importance and satisfaction percentages, a formula column for the opportunity score, and a scatter chart for the 2×2. Move to a BI tool when you need to slice scores by segment, plan, or region across large samples.

Product management tools: hold the roadmap

Product management platforms and feedback boards hold the backlog and roadmap where prioritized needs end up. They’re where scores turn into sequencing decisions, not where the needs or scores originate.

Feedback analytics tools: an alternative for a narrower job

Dedicated feedback analytics tools focus on analyzing high-volume feedback streams. They’re an alternative for teams whose only requirement is feedback analytics. Teams that also run interviews and usability tests get more from keeping that research and their incoming feedback in one place, which is what Dovetail does.

How do you run importance vs satisfaction analysis with Dovetail?

You run it by building the need list in Dovetail, scoring it in a survey and spreadsheet, then returning to Dovetail to explain and share the results.

  1. Gather qualitative research. Upload interviews and usability tests to Dovetail and auto-transcribe them. Focus sessions on what customers are trying to accomplish, not on feature requests.
  2. Tag and theme to derive needs. Tag transcripts and notes across projects, group tags into themes, and capture Highlights for the clearest moments. Use AI-powered analysis to surface patterns you might miss when reviewing sessions one at a time.
  3. Write solution-free need statements. Turn each theme into a single outcome, such as “know which tasks are blocked before a standup.” Keep statements consistent in grammar and scope so ratings are comparable.
  4. Check satisfaction signals in Channels. Set Channels topics to mirror your need list and review sentiment across tickets, reviews, and NPS comments. Needs with persistent negative sentiment are hypotheses for low satisfaction; needs with no feedback at all may be well served—or not on customers’ radar.
  5. Field the survey and calculate scores. Run the importance and satisfaction survey in your survey platform, export the results, and calculate opportunity scores in a spreadsheet.
  6. Explain the top opportunities. For each high-scoring need, return to Dovetail and pull the Highlights and Channels themes that show why satisfaction is low. A score tells you where to look; the evidence tells you what to fix.
  7. Share and hand off. Build a report that pairs each priority with its score and supporting evidence, share it with stakeholders, and connect the work to Jira through the integration.

Why does the need list matter more than the formula?

The need list matters more because the formula can only rank what you give it. If a statement bundles two outcomes, embeds a solution, or is phrased at a different level of detail from its neighbors, the ratings become noisy and the ranking misleads.

Common need-list problems include:

  • Solution-shaped needs. “A better search filter” measures opinion of a feature idea, not the underlying need.
  • Missing needs. Needs no one raised in interviews never get scored, so they never get prioritized. Broad interview coverage and feedback from tickets and reviews reduce this risk.
  • Uneven granularity. A broad need will usually score as more important than a narrow one, regardless of the real opportunity.

Deriving needs from themed research in Dovetail keeps every statement traceable to what customers said, which makes these problems easier to catch before the survey goes out.

What are the most common mistakes with importance vs satisfaction analysis?

The most common mistake is treating the score as the decision rather than as the start of one. Others include:

  • Using a simple gap. Importance minus satisfaction alone overweights minor needs with large gaps.
  • Ignoring segments. An aggregate score can hide a need that’s badly underserved for one segment and well served for another. Cut scores by meaningful segments.
  • Skipping the “why.” Low satisfaction can come from usability, reliability, missing capability, or unclear expectations. Each calls for a different fix, and only qualitative evidence tells them apart.
  • Scoring once. Importance and satisfaction shift as products and markets change. Re-run the survey after significant releases and watch Channels themes between survey waves.

How does importance vs satisfaction compare with the Kano model?

Importance versus satisfaction ranks needs by how underserved they are, while the Kano model classifies features by how their presence or absence affects satisfaction—must-haves, performance attributes, and delighters. They answer different questions and work well together: use opportunity scoring to find the most underserved needs, and Kano to understand what kind of improvement will move satisfaction for a given need. Both depend on well-defined needs grounded in research, which is where Dovetail does the work.

FAQs

What tools prioritize UX improvements using importance versus satisfaction analysis?

Dovetail is the best platform for the research that importance-versus-satisfaction prioritization depends on. It turns interviews and usability tests into tagged, themed customer need statements, and Channels groups support tickets, reviews, and NPS comments into sentiment-tagged themes that show where satisfaction is weak. Once you have opportunity scores, Dovetail reports and the Jira integration carry the priorities to stakeholders and delivery teams. Dovetail doesn’t calculate opportunity scores, so pair it with a survey platform to collect paired ratings and a spreadsheet or BI tool to compute and plot them.

Does Dovetail calculate opportunity scores?

Dovetail builds the inputs and the explanation for opportunity scoring. It helps you derive the customer need list from tagged and themed research, flags weak satisfaction through Channels’ sentiment-tagged themes, and links each high-opportunity need to the Highlights that explain it. Dovetail doesn’t compute importance-versus-satisfaction or opportunity scores itself. A survey platform collects the paired ratings, and a spreadsheet or BI tool calculates the scores and draws the quadrant chart.

What’s the difference between opportunity scoring and gap analysis?

Gap analysis ranks needs by importance minus satisfaction, so a minor need with a large gap can outrank a critical need with a moderate gap. Opportunity scoring adds importance back in—importance + max(importance − satisfaction, 0)—so the most important underserved needs rise to the top. Opportunity scoring also floors the gap at zero, which stops over-served needs from gaining or losing points for being over-delivered.

Can support tickets and reviews replace an importance vs satisfaction survey?

No, but they make the survey better. Tickets, reviews, and NPS comments show where customers are frustrated and in their own words, which helps you write need statements and spot weak satisfaction early. They can’t measure importance, because people rarely write in about things that work or about needs they don’t know a product could meet. Use feedback analysis to shape and validate the survey, not to stand in for it.

How do you write customer needs for an importance vs satisfaction survey?

Write each need as a solution-free outcome the customer wants, such as ‘know which tasks are blocked before a standup’ rather than ‘a blockers dashboard.’ Derive the statements from interview and usability test themes, keep each one to a single outcome, and make them consistent in grammar and level of detail so ratings are comparable. If a need only makes sense with a particular feature in mind, rewrite it.

Editor's picks↘

Latest articles↘

Turn customer feedback into product innovation