System Usability Scale

System Usability Scale: A Quick Usability Scoring Solution
Imagine that you’ve been working for weeks on several updates for your
company’s mobile app that will help connect customers with all the information
they need to access. The project’s finally complete. You take a moment to enjoy
and bask in the sense of accomplishment, and then WHAM! your boss stops and
asks you to provide a report by the end of the week proving that your recent
updates improve the app’s usability. At this moment you could freak out, drop
all personal appointments on your calendar, camp out at the office, and spend the
next few days sleeplessly conducting user tests and gathering results for your
report. OR you can take a few minutes to learn more about the system usability
scale and git-r-done quickly.
Defining Usability
Since you want to prove better usability for your recent updates, then you’d better
dig up a definition of the term usability. The international standard (ISO 9241-
11) defines it as:
The extent to which a product can be used by specified users to achieve specified
goals with effectiveness, efficiency, and satisfaction in a specified context of use.
We also defined usability here. Regardless of which definition you prefer, make
sure you snag one and save it. Using the definition will be a great way to start
off your report or presentation.
Defining System Usability Scale
Now that we have defined what will be measured, let’s talk about the method that
will quickly get you some data – the system usability scale (aka SUS). SUS is a
type of Likert scale that is explicitly designed to measure a product or system’s
usability. When implementing SUS, you will ask users a specific series of 10
questions with responses that range from strongly agree to strongly disagree. The
responses are each given a numerical equivalent that are added together to obtain
a single SUS score (from 0 to 100) representing usability.
This description will also be helpful in explaining your process in the report or
presentation, so feel free to copy this and paste it in place.
A Brief History of the System Usability Scale (SUS)

If you are unfamiliar with SUS, then it may be helpful to know a bit about the
background of this method and where it originated. SUS was developed by John
Brooke in 1986 at Digital Equipment Co. Ltd in Reading, United Kingdom, as
part of the usability engineering program. His team needed a process for
measuring usability that was quick to implement, effective, and reliable. They
started with a pool of 50 questionnaire statements given to 20 people across a
range of occupations to use for assessment on 2 totally disparate software systems
(one that was super simple to use and one that was nearly impossible). The results
were assessed and a set of 10 statements were selected based on intercorrelations
and common responses. You can check out all of the nitty gritty mathematics
and details behind the development of SUS in Brooke’s full documentation. But,
the real take away is that SUS is a tested and proven usability method that has
become the most popular, standardized usability questionnaire.
How to Administer SUS
Believe it or not, administering the SUS is the easiest part of the process. The
questionnaire statements are already created for you. Here they are:
1. I think that I would like to use this system frequently.

2. I found the system unnecessarily complex.
3. I thought the system was easy to use.
4. I think that I would need the support of a technical person to be able to use
this system.
5. I found the various functions in this system were well integrated.
6. I thought there was too much inconsistency in this system.
7. I would imagine that most people would learn to use this system very
quickly.
8. I found the system very cumbersome to use.
9. I felt very confident using the system.
10.I needed to learn a lot of things before I could get going with this system.
You should not alter these statements in any significant way whatsoever. You
are allowed to replace the word “system” with “website” or “product” or
whatever word best represents the object you are testing. And, you can replace
any words that may cause confusion to the participants – the word “cumbersome”
is often replaced with “awkward”. Other than those minor adjustments, you
should not alter the language and/or order of the statements.
We made minor adjustments to the SUS for a mobile app here:

Next, you need to determine how you will present the questionnaire to your
participants. The easy and most common options are paper, PDF, and online
survey system. Feel free to download this form we created for SUS. You can
distribute it as a fillable PDF or print it off and offer your participants paper
copies.
After you’ve prepared the questionnaire, you need to gather a list of people to
participate in the questionnaire. Ideally these people will have had an opportunity
to use the product (even if it’s only for a brief period of time 3-5 minutes) you are
evaluating, but not discussed their opinions with anyone yet. SUS does not
require a large group of participants for reliable results – yes, even asking 5-10
people in your office will work.
Now it’s time to put SUS to work and pull in some data for your report. Deliver
the questionnaire to your participants and ask them to record their immediate
response to each statement without thinking about them for a long time. If a
person feels that they cannot respond to a particular item, then they should mark
the center point of the scale (neither strongly agreeing or strongly disagreeing
with the statement). When the participants have completed their questionnaires,
gather them together for scoring.
How to Score SUS

To determine the SUS score, you first need to note the scale position for each
statement. Scale position values range from 1 to 5 with strongly disagree
equating to 1 and strongly agree equating to 5 (see diagram).
Then, you must calculate a score contribution for each statement. For odd
numbered statements (1, 3, 5, 7, 9), the score contribution is equal to the scale
position minus 1. For even numbered statements (2, 4, 6, 8, 10), the score
contribution is equal to 5 minus the scale position. Each score contribution will
fall within the range of 0 to 4.
Once you have calculated all 10 scores, multiple the sum of the scores by 2.5
which will produce the overall system usability value. These values will range
from 0 to 100.
Here is a sample SUS that has been scored:

You should average the system usability values of all participants to obtain your
overall system usability value.
How to Analyze SUS

Now that you have your SUS score, it’s time to talk about what the score
means. Even though the score will always range between 0 and 100, you must
resist the urge to call it a percentage. It is not a percentage; it is actually a
percentile ranking. Remember back in school when the teacher graded on a bell
curve? Yep. This is the same thing.
If you don’t want to do the math to calculate a true percentile ranking, then you
can go by this rule of thumb – an SUS score of 68 is average. So, any score above
68 is above average, and any score below 68 is below average. Hopefully, your
score is well above 68 so you can report a high usability score.
Make sure you clearly communicate to your boss and anyone else that views your
report that the SUS score does NOT equate to a percentage.
Pros of SUS
There are many reasons why SUS is the most popular standardized usability
questionnaire. Here’s a few of them:
• SUS is inexpensive. In fact, the system itself is non-proprietary (no license

needed) and totally free. The only cost is your time spent preparing,
conducting, and analyzing the questionnaire. (You may incur costs if you
choose to use an online survey system to administer the questionnaire.)
• SUS is easy to administer. There are only 10 questions. The questions are
pre-written for you. And, you can choose to collect responses in the way
that is easiest for you (paper, PDF form, online survey).
• SUS questionnaires are easy for participants to complete. With only one
instruction and a fairly simple structure for responses, participants can
quickly understand what to do and finish an SUS questionnaire in a matter
of minutes.
• SUS produces quick results. You can easily prep, conduct, analyze, and
report on an SUS study in a matter of hours.
• SUS is technology agnostic. You can determine usability for a wide range
of products (not just technology based products) using SUS.
• SUS provides single score results. Having one score to analyze makes
reporting extremely simple.
Cons of SUS
As with any system, SUS does have some drawbacks. Here’s a list of the most
commonly sited ones:
• SUS scoring is a bit tricky which can lead to calculation errors. You can
easily avoid this by using a scoring sheet that automatically calculates scores
like this handy one we created. Please feel free to download the excel file
and use for your SUS.
• SUS scores can be misinterpreted as percentages, which they are NOT. This
is why you should clearly explain the score and even offer up a comparable
grade for the people you share the scores with, so they do not need to draw
their own conclusions. See Brooke’s SUS: A Retrospective for more info
on scoring.
• SUS is not a diagnostic tool. It cannot tell you which piece of your product
causes high or low levels of usability. It only gives one score which
represents the product’s overall usability. If your SUS does result in a low
usability score, you will need to conduct further research to pinpoint the
problem areas.
When & Where You Should Use SUS
You should consider SUS for your UX research when you are looking for a quick
assessment of a product’s usability. Since, SUS can be used on practically any
product, it is a good option when other research methods are projected to return
scores with low confidence or may be skewed based on technological challenges.
SUS results get even better when you implement an SUS at each revision round
thus providing you with scores that can be compared while progress is being made
to ensure that changes are improving the product.
SUS can be administered in many different scenarios and return valid results for
both in-person and remote situations.
When & Where You Should NOT Use SUS

Even though SUS is highly reliable, there are scenarios when you should not use
it for your UX research. The most common scenario is when you are interested
in obtaining feedback about specific components of a product. If you need to
know whether the new dropdown menu is working for users, then SUS cannot
deliver that data. Again, SUS only provides an overall usability score for a
product.
Conclusion
As you can tell there is certainly a right place and right time for SUS. In our
scenario, it most certainly was the right place and time because we had just a few
days to conduct usability research and provide a report for the executive team.
Even though there are limitations around the depth of usability information SUS
can provide, it is still a widely used and accepted UX research method. This is
primarily because it’s ease to administer and its longevity of providing valid,
reliable results across many 1000s of studies.
Please feel free to download and use any of the SUS tools we’ve made available,
and reach out to us if questions arise as you are conducting your own SUS studies.

System Usability Scale

Uploaded by

Copyright:

Available Formats

System Usability Scale

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Usability Scale

Uploaded by

Copyright:

Available Formats

What is the System Usability Scale (SUS)?

How is SUS administered?

System Usability Scale: A Quick Usability Scoring Solution

A Brief History of the System Usability Scale (SUS)

1. I think that I would like to use this system frequently.

We made minor adjustments to the SUS for a mobile app here:

How to Score SUS

Here is a sample SUS that has been scored:

How to Analyze SUS

• SUS is inexpensive. In fact, the system itself is non-proprietary (no license

When & Where You Should NOT Use SUS

You might also like