Success

Success measures whether users can complete a specific task, like finding a button, using a filter, or reaching the right page. It focuses on interaction-level usability and whether people can get something done without getting stuck.Use this metric during usability tests, A/B comparisons, or when auditing known problem areas. It’s especially helpful for checking if users can find and use key actions, and whether interface elements are easy to understand.Success helps you validate whether users can move through a flow with clarity and confidence. If the score is low, it’s usually a sign of trouble with labeling, layout, or overall task visibility.Interpreting the ResultsUse this key to understand what your Success score means and how to interpret that for your product experience:How to Calculate SuccessThe Success metric measures whether users are able to correctly identify and interact with the intended target area in a design, helping evaluate clarity and usability.Set up questionsUse a click test that asks participants to complete a task on a page:This task should include a predefined correct area (or “success hotspot”) and can be distributed to your target audience via a remote testing tool.Collect dataYour click test may produce a data report like this heatmap:Or simply a data report where clicks are recorded and classified as either correct (clicked the designated hotspot) or incorrect.Plug data into the formulaThe Success score is calculated using the formula:This gives you the proportion of participants who successfully completed the task by clicking on the intended UI element.Calculate the Success scoreFor this task, 84% of participants clicked the correct hotspot to activate the try-on feature.This Success score of 84% is considered Good on a scale from Very Poor to Very Good, indicating that most users understood where to take action on the pageWhen to Use Success MetricsSuccess UX metrics provide valuable insights into how effectively users interact with your product or feature, helping you identify pain points and improve usability. By measuring task completion rates, error rates, and overall satisfaction, you can optimize your design to ensure that users achieve their goals efficiently and with ease. High success metrics lead to better user experiences, driving adoption and satisfaction. Here are some common use cases for measuring success:Landing Page ConversionSuccess metrics help evaluate how effectively a landing page converts visitors into customers by guiding them toward actions like sign-ups or purchases. Tracking conversion rates and task completions can reveal whether the design aligns with user expectations and drives engagement.Account ManagementMeasuring success metrics in account management evaluates how easily users can update profiles, manage subscriptions, or access account details. High task completion rates and reduced errors indicate a smooth and user-friendly interface.Shopping Cart FlowSuccess metrics in shopping cart flows measure how efficiently users can add items, review their carts, and complete purchases. Tracking drop-off rates and time on task provides insights into friction points in the checkout process.How We Measured Success of Getup’s “Try On in Store” FeatureTo evaluate whether users could successfully find and use Getup’s new “Try On in Store” option, we ran a Success test on the brand’s product landing page. This feature lets shoppers select clothing online and send it to a nearby retail location to try on in person, bridging digital browsing with in-store experiences.The SetupSuccess is measured by giving participants a task-based prompt—for example:“Find where you would go to try this item on in-store.”We then measure whether participants are able to complete the task accurately and where they click first, as well as how long it takes to make that decision. This produces a Success score and an accompanying Response Time metric.The ResultsOur click test produced the following results:We plugged the data into theSuccess formula to reveal the score:Getup’s “Try On in Store” feature earned a Success score of 84%, rated Good on the Glare scaleMost participants were able to locate and use the feature with little confusion, identifying the correct interaction pathThe average Response Time was 10.38 seconds, indicating moderate scannability—users could find the action relatively quickly, though not instantlyHeatmap data showed the majority of first clicks landing directly on the “Add to Cart” area, where the Try On option was surfaced as a variation or next stepThe ImpactThis Success test showed that Getup’s integration of the Try On feature into their product page flow was intuitive for most users. However, the slightly longer response time suggested the team could benefit from boosting the visibility or labeling of the feature. The results reinforced that users are open to blending online and offline shopping—if they can find the tools easily.SourceHelio SurveyCSVHow to Use AI to Measure SuccessUsing the first-click test outlined in the How to Calculate section above, gather responses on a survey from an audience of at least 100 respondents. We find that 100 responses is statistically significant in most markets. Once the responses are collected, download the CSV file of your data report and upload it into an AI platform along with the prompt below.Copy this AI prompt to calculate your own Success score, and check out the type of output it would produce:Technicals for Measuring SuccessThe code snippets below show how UX metrics can be measured using data from a survey platform. Take a peak into the development of these metrics, and even become a contributor in ourpublic repo.Data StructureThe following JSON structure tracks success metrics and user interactions with call-to-action (CTA) hotspots. The scores object includes percentages for primary, secondary, and tertiary CTAs. The clicks array logs details of user interactions such as where and when they clicked.{\n\tscores: {\n\t\tsuccessful_primary_score: 60,\n\t\tsuccessful_secondary_score: 20,\n\t\tsuccessful_tertiary_score: 20\n\t},\n\tclicks: [\n\t\t{\n\t\tid: 1,\n\t\trelative_x: 0.5341614906832298,\n\t\trelative_y: 0.17133956386292834,\n\t\tcreated_at: \u00222018-12-13 17:54:24\u0022,\n\t\tsection_response_id: 424242,\n\t\thotspot_id: 1\n\t\t},\n\t\t....\n\t]\n\t\n}Parsing DataIn Ruby, the net_success_score method calculates the success score for primary, secondary, and tertiary CTAs. Each success metric is determined by dividing the number of successful clicks by the total number of clicks, providing a percentage for each. This parsing logic calculates the percentage of users who successfully clicked on the appropriate CTAs, giving insight into how well users perform key tasks based on the type of action (primary, secondary, or tertiary).class UxMetric\n\tdef net_success_score\n\t\tsuccessful_primary_CTA_clicks = clicks.where(primary_hotspot: true)\n\t\tsuccessful_secondary_CTA_clicks = clicks.where(secondary_hotspot: true)\n\t\tsuccessful_tertiary_CTA_clicks = clicks.where(tertiary_hotspot: true)\n\n @scores ||= {\n\t successful_primary_score: (successful_primary_CTA_clicks / total_clicks) * 100,\n\t successful_secondary_score: (successful_secondary_CTA_clicks / total_clicks) * 100,\n\t successful_tertiary_score: (successful_tertiary_CTA_clicks / total_clicks) * 100\n }\n end\nendValidationThe JavaScript function below validates whether the success questions are structured properly. It ensures that each question has hotspots labeled appropriately (e.g., primary, secondary, tertiary) and checks that the user isn't immediately navigating to the next section.This validation ensures that each success question is correctly labeled and structured for evaluating success rates, preventing navigation errors that could interfere with the accuracy of the results.function isValidSuccessQuestion(question) {\n\tlet success_labels = [\n\t\t'primary', 'secondary', 'tertiary', 'quaternary',\n\t\t'quinary', 'senary', 'septenary', 'octonary',\n\t\t'nonary', 'denary'\n\t]\n\tif (question.type !== 'Click' \u0026\u0026 question.hotspots.length === 0) {\n\t\treturn false;\n\t}\n\t\n\tfor ( let i = 0 ; i \u003c question.hotspots.length; i++ ) {\n\t\tif (!question.hotspots[i].label.includes(success_labels[i])) {\n\t\t\treturn false;\n\t\t}\n\t\tif (question.hotspots[i].branch_event +== 'next_section') {\n\t\t\treturn false;\n\t\t} \n\t}\n return true;\n}Score TranslationThe JavaScript functiontranslateSuccessScoreconverts the success scores into qualitative categories—High,Average, orLow—based on predefined thresholds for primary, secondary, and tertiary CTAs.This function evaluates the success score based on specific thresholds and returns a qualitative label (High, Average, or Low) for quick interpretation of user success performance.function translateSuccessScore(scores) {\n\tlet {\n\t\tsuccessful_primary_score,\n\t\tsuccessful_secondary_score,\n\t\tsuccessful_tertiary_score\n\t} = scores;\n\t\n\tif (\n\t\tsuccessful_primary_score \u003e= 90 ||\n\t\tsuccessful_secondary_score \u003e= 80 ||\n\t\tsuccessful_tertiary_score \u003e= 65\n\t\t) {\n\t\treturn 'High'\n\t}\n\telse if (\n\t\t\t(successful_primary_score \u003e= 80 \u0026\u0026 successful_primary_score \u003c 90) ||\n\t\t\t(successful_secondary_score \u003e= 70 \u0026\u0026 successful_secondary_score \u003c 80) ||\n\t\t\t(successful_tertiary_score \u003e= 55 \u0026\u0026 successful_tertiary_score \u003c 65))\n\t\t{\n\t\treturn 'Avg';\n\t} else {\n\t\treturn 'Low';\n\t}\n}Templates & Presentation MaterialsCreate effective presentation slides, document design concepts, and implement UX Metrics with templates and resources.We've done the work to provide professional layouts that communicate to your stakeholders. UX Metric cards clearly communicate the totals, allow space for breakdowns, and styled to allow for your own brand.Visit Findings for TemplatesResourcesThe Resources section provides a collection of articles, case studies, methods, and blog posts to support your work within the UX metrics framework. These materials offer insights into best practices, research methodologies, and practical applications for improving design comprehension and usability. Whether you're refining your design process or conducting user research, these resources will help guide you towards data-informed, user-centered decisions.ArticlesSuccess Rate: The Simplest Usability Metricby,Jakob NielsonandRaluca BudiuExplore the usability success rate, the percentage of users who complete a given task, as the most straightforward, intuitive usability metric. They argue it's a powerful snapshot of user experience but comes with limitations and practical considerations.Helio MethodsPrototype Testingby HelioThe Essential Guide to Choosing the Right Rapid Prototype Techniqueby HelioHelio Case studiesHelloFresh Membership Offer Effectivenessby HelioMaximizing Design Efficiency with Low-Fidelity Prototypesby HelioTake This Further with the UX Metrics AI SkillsSuccess measures whether users are actually achieving their goals in your product. TheUX Metrics AI Skillsis a package you load into your LLM so you can ask questions and get expert answers anytime.Define what success looks like for your usersSet success rate benchmarks and track changes over timeFind out what is blocking users from succeedingConnect success data to product and design prioritiesDrop it into your LLM and start asking questions right away.