{"id":9207,"date":"2021-05-27T08:33:03","date_gmt":"2021-05-27T05:33:03","guid":{"rendered":"https:\/\/atostek.com\/?p=9207"},"modified":"2022-09-05T14:47:47","modified_gmt":"2022-09-05T11:47:47","slug":"system-usability-scale-as-a-tool-of-usability-design","status":"publish","type":"post","link":"https:\/\/atostek.com\/en\/system-usability-scale-as-a-tool-of-usability-design\/","title":{"rendered":"The System Usability Scale as a tool of usability design"},"content":{"rendered":"<p><strong>How can we measure usability? This is what Atostek user experience design specialist Markus Jaakola has to ponder.<\/strong><\/p>\n<p>Usability is a feature that is required of software, yet that is challenging to measure objectively. When measuring something, it must always be compared to something else. But there is no absolute scale or metric of usability that every system could be compared to.<\/p>\n<h2 id='defining-and-measuring-usability'  id=\"boomdevs_1\" >Defining and measuring usability<\/h2>\n<p>Traditionally, usability has been defined as referring to system functionality for its intended purpose. The traditional definition of usability is based on three factors:<\/p>\n<ul>\n<li>effectiveness of use<\/li>\n<li>efficiency of use<\/li>\n<li>user satisfaction.<\/li>\n<\/ul>\n<p>The metrics of effectiveness, efficiency and satisfaction can be defined system by system. Each software meets some usability requirements set for it. However, software are different from each other in both purpose and function, so the usability requirements of software are also different.<\/p>\n<p>When we say software differ, we mean that they have different intended uses, different contexts of use and different users. Of course, the implementation technology and user interface can also be anything in the world.<\/p>\n<p>When usability requirements set for the system are met, its usability can be said to be at a good level. But how good is it compared to other systems? How can we compare the usability of different systems? This is the question John Brooke was trying to answer when he developed the System Usability Scale in 1986.<\/p>\n<h2 id='the-sus-survey-method'  id=\"boomdevs_2\" >The SUS survey method<\/h2>\n<p>The System Usability Scale, or SUS, is a simple and reliable tool for measuring the usability of any system. These systems may include software, hardware or a combination of the two.<\/p>\n<p>The SUS method consists of a ten-point questionnaire that users take after using a system or its prototype. The SUS survey questions are multiple-choice questions with a five-level Likert scale, so answering is quick and easy. The result of the survey is a score describing the usability of the system on a scale from zero to one hundred.<\/p>\n<p>The score obtained from the SUS calculation describes system usability on a general level. The SUS survey does not include detailed feedback, so you cannot tell what needs to be improved based on it alone.<\/p>\n<p>The method is based on several hundred system ratings, so we know the average result produced by the survey, regardless of system. Therefore with the results, the target system is compared to all other existing systems.<\/p>\n<p>The strengths of this method are simplicity and reliability. You can get a reliable result with a very small number of respondents. Even just a handful of respondents are enough to give a result providing a correct idea of the real state of the system.<\/p>\n<p>The lightweight survey is easy to implement both on paper and online. No special software is required to analyze the results. You can calculate the result with the formula openly provided by the method. Atostek\u2019s UX experts have developed ready-made survey and formula templates that make usability measurement easy and cost-effective.<\/p>\n<h2 id='challenges-of-the-sus-method'  id=\"boomdevs_3\" >Challenges of the SUS method<\/h2>\n<p>One of the challenges of the method is interpretation of the resulting score. Although the scale runs from 0 to 100, the average result is not halfway through the scale, but at 68 points. This is unintuitive, so when reporting on the results, it is better to use percentiles describing the result distributions. Percentiles describe how many of the data points fall below the value in question.<\/p>\n<p>For example, 68 is the average score, so 50% of all SUS results fall below 68 points, and correspondingly, the other 50% of results fall above it. If the score is 80 points, that is an excellent result belonging to the 90th percentile. With a score like that, we can say that 90% of all systems are worse off in terms of usability than the system in question.<\/p>\n<p>Another challenge is the quantitative and abstract nature of the results. The method provides information on the level of usability but not the reasons behind it. The method does not make respondents give reasons for their answers, instead focusing on getting results quickly and easily.<\/p>\n<p>Usability experts must use other methods in tandem with the SUS in order to identify what can be improved and what needs to change about the system.<\/p>\n<h2 id='benefits-and-using-the-scale'  id=\"boomdevs_4\" >Benefits and using the scale<\/h2>\n<p>The System Usability Scale is just one tool for measuring usability. It alone is not enough for designing and evaluating usability, but it enables us to compare different systems with an universal metric.<\/p>\n<p>The SUS method can be used for software development to, for example, verify the fulfillment of usability goals or assist in choosing the solution with the best usability from several systems.<\/p>\n<p>If you are replacing an old data system with a new one, the goal is usually to improve usability at the same time. With the SUS method, the fulfillment of the goal can be measured and verified numerically in a scientifically valid way. This way, success can be measured by more than just how you happen to feel about it.<\/p>\n<p>Atostek\u2019s toolkit of service and UX design services brings you a variety of tools for a successful software project. One of them is the System Usability Scale presented here.<\/p>\n<p>Sources:<\/p>\n<p>Brooke, John. (1995). SUS: A quick and dirty usability scale. Usability Eval. Ind.. 189.<\/p>\n<p>Nielsen Norman Group: Beyond the NPS: Measuring Perceived Usability with the SUS, NASA-TLX, and the Single Ease Question After Tasks and Usability Tests. <a href=\"https:\/\/www.nngroup.com\/articles\/measuring-perceived-usability\" target=\"_blank\" rel=\"noopener\">https:\/\/www.nngroup.com\/articles\/measuring-perceived-usability<\/a> (Cited May 19, 2021)<\/p>\n<p>Usability.gov: System Usability Scale (SUS). <a href=\"https:\/\/www.usability.gov\/how-to-and-tools\/methods\/system-usability-scale.html\" target=\"_blank\" rel=\"noopener\">https:\/\/www.usability.gov\/how-to-and-tools\/methods\/system-usability-scale.html<\/a> (Cited May 19, 2021)<\/p>\n<hr \/>\n<div style=\"padding: 1%; width: 780px; margin: 1%;\">\n<p><img decoding=\"async\" class=\"wp-image-9201 alignleft\" src=\"https:\/\/atostek.com\/wp-content\/uploads\/2021\/05\/atostek-markus-jaakola_cropped-261x300.jpg\" alt=\"Atostek Markus Jaakola.\" width=\"177\" height=\"203\" srcset=\"https:\/\/atostek.com\/wp-content\/uploads\/2021\/05\/atostek-markus-jaakola_cropped-261x300.jpg 261w, https:\/\/atostek.com\/wp-content\/uploads\/2021\/05\/atostek-markus-jaakola_cropped.jpg 554w\" sizes=\"(max-width: 177px) 100vw, 177px\" \/><\/p>\n<div style=\"float: right; width: 70%;\">\n<p style=\"font-size: 18px;\"><b>Markus Jaakola<\/b><br \/>\n<em>UX Designer<\/em><\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>How can we measure usability? This is what Atostek user experience design specialist Markus Jaakola has to ponder. Usability is a feature that is required of software, yet that is challenging to measure objectively. When measuring something, it must always be compared to something else. But there is no absolute scale or metric of usability&hellip;<\/p>\n","protected":false},"author":24,"featured_media":9193,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"inline_featured_image":false,"footnotes":""},"categories":[114],"tags":[],"class_list":["post-9207","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","entry","has-media"],"_links":{"self":[{"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/posts\/9207"}],"collection":[{"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/comments?post=9207"}],"version-history":[{"count":1,"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/posts\/9207\/revisions"}],"predecessor-version":[{"id":11739,"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/posts\/9207\/revisions\/11739"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/media\/9193"}],"wp:attachment":[{"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/media?parent=9207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/categories?post=9207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/atostek.com\/en\/wp-json\/wp\/v2\/tags?post=9207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}