We can feel satisfied with a meal, a movie, or a moment.<\/p>\n Our feeling of satisfaction blends utility (it fed me), affect (I enjoyed it), and expectation (it lived up to or exceeded what I wanted<\/a>).<\/p>\n The dessert, the movie ending, or the moment can all be satisfying or unsatisfying. And we apply that same idea to measuring satisfaction in consumer and user research.<\/p>\n Customer or consumer satisfaction has a rich history going back almost a century. In the 1940s, satisfaction was used as a marketer\u2019s goal for meeting consumer needs and wants (e.g., Duddy and Revzan, 1947<\/a>, where they described \u201cDissatisfaction \u2026 because of defects in manufacture or design\u201d).<\/p>\n Day (1977) and his colleagues began a modern tradition<\/a> of research aimed at understanding satisfaction and related post-choice constructs.<\/p>\n The historical focus of UX research, in contrast, has been more on ease of use than on general satisfaction because ease is a key experiential driver<\/a> of the broader construct of satisfaction.<\/p>\n However, because modern UX research often overlaps with traditional market research, UX research professionals may need to measure or at least consider customer satisfaction in testing efforts such as benchmarks or surveys.<\/p>\n In this article, at a conceptual level, we discuss the measurement of satisfaction and perceived ease of use in UX research at the study (overall) level and as post-task metrics.<\/p>\n At the study level, measuring one or both of overall satisfaction and ease of use is fairly common, but market research emphasizes satisfaction and UX research emphasizes ease of use.<\/p>\n Satisfaction can be measured in anything: a brand, a product, a feature, a website, or a service experience. Consequently, it can be referred to as CSAT (customer satisfaction) or product satisfaction.<\/p>\n In our taxonomy of UX metrics<\/a>, satisfaction is most commonly collected at the study level<\/em> (Figure 1), meaning it\u2019s collected only once to assess the overall product experience. It can be measured<\/a> using a simple seven- or eleven-point scale or one of the industry metrics, such as the Microsoft Net Satisfaction score (NSAT<\/a>) or the American Customer Satisfaction Index (ACSI<\/a>, which is a proprietary mix of three aspects of satisfaction).<\/p>\n Figure 1:<\/strong> Study-level metrics from the MeasuringU taxonomy of UX metrics include four measures of satisfaction.<\/p>\n Perceived ease of use can also be measured at the product level. We have written extensively about the many ways of measuring ease. Most major standardized UX questionnaires designed to assess user experiences at the study level (e.g., SUPR-Q<\/a>\u00ae<\/sup>, SUS<\/a>, PSSUQ<\/a>, UX-Lite<\/a>\u00ae<\/sup>, and TAM<\/a>) have at least one item (and sometimes more) dedicated to measuring perceived ease (Figure 2). However, satisfaction with a product conceptually involves more than just finding a product easy to use. Product usefulness, pricing, integration, and support are some of the other common constructs that can affect satisfaction, but ease is a fundamental driver.<\/p>\n Figure 2:<\/strong> Study-level metrics from the MeasuringU taxonomy of UX metrics include numerous standardized questionnaires that measure perceived ease (e.g., SUS, PSSUQ, SUPR-Q, TAM, UMUX, UMUX-Lite, UX-Lite).<\/p>\n At the task level, measuring task ease is more common than measuring task satisfaction, largely because task-level evaluation, as conducted in usability studies (a key UX activity), is relatively rare in market research. That said, nothing prevents researchers from including an item to assess task satisfaction in addition to the perceived ease of task completion. We now include both in our taxonomy of UX metrics at the task level (Figure 3).<\/p>\n Figure 3:<\/strong> Attitudinal task-level metrics from the MeasuringU taxonomy showing measures of perceived ease and general satisfaction (along with confidence and workload effort).<\/p>\n While less common than ease ratings, satisfaction ratings can also be collected at the task level. After a participant attempts a task, they can be asked how satisfied they are with the website, the app or product, or a specific functional area.<\/p>\n The Single Ease Question (SEQ<\/a>\u00ae<\/sup>) is the most commonly used post-task measure of ease (with over 600 citations). This single-item scale provides a reliable and sensitive measure of the perceived ease or difficulty of a task experience.<\/p>\n At both the study and task level, conceptually, satisfaction is a broader construct than ease. We often depict satisfaction as a consequence of several variables along with ease, including, to name a few, usefulness, price, and quality. Under this broader construct, people can be satisfied with a product or experience but not necessarily think it\u2019s easy to use. Higher satisfaction scores would have to come from other aspects of the product than ease, such as great features, low price, or wide availability. While the two differ conceptually, we\u2019ll explore qualitatively how much measures of satisfaction and measures of ease actually differ in a future article.<\/p>\n Although satisfaction is often considered a primary measure for market researchers, it also played an early and fundamental role in the definition of UX metrics, reflected in the high-level constructs of the first international usability standard, ISO-9241 Part 11<\/a>. In that standard, the specified components of usability were effectiveness, efficiency (objective metrics), and satisfaction (a subjective metric).<\/p>\n The use of these constructs was common before the publication of the ISO standard in 1998, dating back to at least the early 1980s. The first draft of the standard appeared in 1988, and specific metrics were investigated in the European MUSiC project<\/a>.<\/p>\n ISO-9241 Part 11 and other early UX standards specified measurement of satisfaction but did not usually require specific metrics. The definition of satisfaction from ISO-9241-11 was \u201cfreedom from discomfort and positive attitudes towards the use of the product.\u201d Regarding the measurement of satisfaction, the 2001 ANSI standard Common Industry Format for Usability Test Reports<\/a> stated (p. 11):<\/p>\n A variety of instruments are available for measuring user satisfaction of software interactive products, and many companies create their own. Whether an external, standardized instrument is used or a customized instrument is created, subjective rating dimensions such as Satisfaction, Usefulness, and Ease of Use should be considered for inclusion, as these will be of general interest to customer organizations. A number of questionnaires are available that are widely used. They include: ASQ, CUSI, PSSUQ, QUIS, SUMI, and SUS. While each offers unique perspectives on subjective measures of product usability, most include measurements of Satisfaction, Usefulness, and Ease of Use<\/em>.<\/p>\n So, in the early days of UX research and measurement, especially in the context of usability testing, the concept of satisfaction was broad and included measures of ease of use as proxies of satisfaction.<\/p>\n While the Single Ease Question (SEQ) has become the industry standard for measuring post-task ease, prior to its development, we used the After Scenario Questionnaire (ASQ<\/a>).<\/p>\n The three-item ASQ was developed by Jim Lewis and colleagues in 1988 as part of an IBM Research system usability metrics project<\/a> (Figure 4). Although the item format is completely different from the standard SEQ (a lower rating indicates better experience, agreement rather than item-specific endpoints, and satisfaction-based wording), it contains a single-item seven-point measure of perceived ease.<\/p>\n Consistent with the emerging definition of usability at the time of its development, all the items of the ASQ, including the ease item, were framed in the context of satisfaction but were directed at potential drivers of satisfaction at the task level. Over time, the focus in UX practice shifted away from this nod to satisfaction and streamlined the wording of items to focus on their distinctive content (e.g., the SEQ).<\/p>\n Figure 4:<\/strong> The ASQ (from 1990).<\/p>\n When we wrote about the Single Usability Metric (SUM<\/a>) in 2005<\/a>, we incorporated satisfaction into our model along with objective metrics such as task completion rates and times. Our original three-item measure of satisfaction was based on the ASQ, retaining ratings of task ease, task completion time, and overall task satisfaction, then averaging the three ratings for a composite satisfaction score. That\u2019s another broad use of satisfaction as a measure of users\u2019 attitude toward the experience, consistent with the guidance in ISO 9241-11 and other usability standards of the time.<\/p>\n As we consider the future of satisfaction in UX research, we see an opportunity for UX researchers not to feel like they should avoid satisfaction because it\u2019s historically been a metric tracked by another department. We recommend, when appropriate, including general satisfaction (e.g., CSAT) in their battery of subjective metrics, at least at the study level (and possibly at the task level).<\/p>\n Whether or not ratings of satisfaction and perceived ease of use have a high correlation and correspondence (which we are investigating and plan to report in future articles), outside of UX, they are conceptually distinct. Ease is influential in UX research; satisfaction is influential in CX and market research. This is likely due to the logic that perceived ease affects satisfaction rather than the reverse.<\/p>\n UX research tends to focus on the precursors to satisfaction because these precursors are closely related to the specific designs of products or services. CX and market research tend to focus on satisfaction as a driver of important business metrics (e.g., behavioral intentions such as likelihood to repurchase, actual repurchasing behavior, or profit).<\/p>\n Including the measurement of satisfaction in UX research (when appropriate) would enable the quantification of the extent to which perceived ease of use (and other UX metrics such as perceived usefulness, appearance, and trust) drives satisfaction, a major step in bridging the gap between UX and business metrics.<\/p>\n Customer satisfaction is a key metric in market research and business.<\/p>\n Historically, a particular conceptualization of satisfaction has also been important in UX research, but the business and UX conceptualizations are not the same.<\/p>\n From the early days of usability testing to the later development of international usability standards, the UX conceptualization of satisfaction has been any attitude toward a product. Of the various attitudes people might have toward a product, ease of use is a major one.<\/p>\n In this article, we\u2019ve discussed the measurement of satisfaction and ease of use at study and task levels and have presented an argument for measuring both in UX research (at least at the study level) to provide a quantitative connection between UX and business metrics.<\/p>\n![\"feature](\"https:\/\/measuringu.com\/wp-content\/uploads\/2025\/12\/120225-FeatureImage-1.png\")
<\/a>\u201cSatisfaction\u201d is used rather broadly in vernacular speech.<\/p>\nStudy Level<\/h2>\n
Study-Level (Product) Satisfaction<\/h3>\n
<\/a><\/p>\nStudy-Level Ease<\/h3>\n
<\/a><\/p>\nTask Level<\/h2>\n
<\/a><\/p>\nTask-Level Satisfaction<\/h3>\n
Task-Level Ease<\/h3>\n
Satisfaction vs. Ease<\/h2>\n
Historical Role of Satisfaction in UX Research<\/h2>\n
The After-Scenario Questionnaire (ASQ)<\/h3>\n
<\/a><\/p>\nSatisfaction and the Single Usability Metric (SUM)<\/h3>\n
Future Role of Satisfaction in UX Research<\/h2>\n
Summary and Takeaways<\/h2>\n