We can use that assessment to determine which of the 6 stages an organization currently occupies. The UX-maturity model provides a framework to assess each organization’s UX-related strengths and weaknesses. As we continue to work with organizations to assess UX maturity and gather additional data about the evolution and outcomes of UX maturity, we plan to continue refining this model. This article details the NN/g UX-maturity model. With these changes in mind, we have revised how UX maturity should be modeled and measured to incorporate the new norms and to describe the organizational evolutions we’ve witnessed in our thousands of clients and students over the past decade and a half. Since then, much has changed in the field of UX: how we perform design and research, our knowledge about jobs, work, processes, tools, deliverables, leadership involvement, and, how enterprises view and prioritize UX into overall strategy. Each stage described UX presence in different organizational circumstances - from companies that engaged in absolutely no user research to ones that achieved peak focus. In 2006, Jakob Nielsen developed one of the earliest UX-maturity models, defining 8 phases of UX maturity. It encompasses the quality and consistency of research and design processes, resources, tools, and operations, as well as the organization’s propensity to support and strengthen UX now and in the future, through its leadership, workforce, and culture. The references at the end of this page and the template provide more information in context about the process.UX maturity measures an organization’s desire and ability to successfully deliver user-centered design. Though the scores are 0-100, these are not percentages and should be considered only in terms of their percentile ranking.īased on research, a SUS score above a 68 would be considered above average and anything below 68 is below average, however the best way to interpret your results involves “normalizing” the scores to produce a percentile ranking. The participant’s scores for each question are converted to a new number, added together and then multiplied by 2.5 to convert the original scores of 0-40 to 0-100. The questionnaire and scoring are outlined in the System Usability Scale (SUS) Template. I needed to learn a lot of things before I could get going with this system. I found the system very cumbersome to use. I would imagine that most people would learn to use this system very quickly. I thought there was too much inconsistency in this system. I found the various functions in this system were well integrated. I think that I would need the support of a technical person to be able to use this system. I found the system unnecessarily complex. I think that I would like to use this system frequently. When a SUS is used, participants are asked to score the following 10 items with one of five responses that range from Strongly Agree to Strongly disagree: SUS is not diagnostic - its use is in classifying the ease of use of the site, application or environment being tested The best way to interpret your results involves “normalizing” the scores to produce a percentile ranking There is a temptation, when you look at the scores, since they are on a scale of 0-100, to interpret them as percentages, they are not If you are considering using a SUS, keep the following in mind: Is valid – it can effectively differentiate between usable and unusable systems Is a very easy scale to administer to participantsĬan be used on small sample sizes with reliable results The noted benefits of using SUS include that it: SUS has become an industry standard, with references in over 1300 articles and publications. Originally created by John Brooke in 1986, it allows you to evaluate a wide variety of products and services, including hardware, software, mobile devices, websites and applications. It consists of a 10 item questionnaire with five response options for respondents from Strongly agree to Strongly disagree. The System Usability Scale (SUS) provides a “quick and dirty”, reliable tool for measuring the usability.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |