Do Novices or Experts Uncover More Usability Issues?

Do Novices or Experts Uncover More Usability Issues_

Do Novices or Experts Uncover More Usability Issues_Finding and fixing problems encountered by participants through usability testing generally leads to a better user experience.

But not all participants are created equal. One of the major differentiating characteristics is prior experience.

People with more experience tend to perform more tasks successfully, more quickly and generally have a more positive attitude about the experience than inexperienced people.

But does testing with experienced users lead to uncovering fewer problems or different problems than with novices? As participants gain experience with an app do they find workarounds that mean problems are less detectable in usability tests? Or do expert users tend to uncover the same or even more issues because of their knowledge of the app?

Defining Experience

For quite some time there has been a discussion on the differences between novice and experienced users. For example, in Nielsen’s seminal book, Usability Engineering, he defines three types of experience levels that are worth noting:

  • Domain knowledge: Ignorant versus knowledgeable
  • Computer knowledge: Minimal versus extensive
  • System knowledge: Novice versus expert

While there’s general agreement that domain, tech, and app-specific experience are the aspects that separate novices from experts, it’s less clear what those thresholds are. For example, Dumas and Redish provide the general guidance of:

  • Novice: < 3 months of experience
  • Intermediate: > 3 months but < 1 year of experience
  • Expert: > 1 year experience

And Hackos and Redish (1998) identify four levels of expertise:

  • Novices: New users of a product (e.g. using an information kiosk at a museum or airport)
  • Advanced beginners: Focus on getting job done (e.g. most people’s use of microwave ovens)
  • Competent performers: Ability to perform more complex tasks (e.g. computer repair technician)
  • Expert performers: Have a comprehensive understanding of the whole system (teach the support technicians)

Differences in Problems Uncovered Between Experts and Novices

While there is variation in how experts and novices are differentiated, I reviewed the literature to look for studies that compared the two, however they are defined. In particular, I looked for any evidence that experts and novices encountered a different number, severity, or type of usability issue.

Experts Finding More Problems than Novices

Two studies found experts uncovered more problems than novices.

Prümper et al. (1991) observed 174 clerical workers working on their own computers and recorded errors. Experts were defined as having at least one year of computer expertise, familiarity with one program, and using a computer at least 50% of the day (something similar to the Nielsen 3).

In this observational study (rather than usability evaluation), counterintuitively, they found expert users committed more errors than novices but experts spent less time handling the errors than novices. This is in line with Don Norman’s distinction between mistakes (an error in the intention) and slips an error in carrying out the correct intention). Both novices and experts would be expected to make slips, but experts may commit more slips because they’re working faster, and due to their expertise, have developed strategies for quickly recovering from slips.

Sauer et al. (2010) had 48 participants interact with a floor scrubbing prototype or product. Half were experts (used the device at least once per month) and half were novice (never having used). They found that experts identified more usability problems than novices (157 vs. 109). After removing duplicates, they were left with 116 distinct problems, of which 56% were identified by experts, 8.6% by novices, and 35.3% by members of both groups. Usability problems reported by novices were considered to be more severe than those identified by experts.

The authors noted that experts reported more potential problems due to their higher level of expertise, which allowed them to anticipate usability problems that may occur in task scenarios they had previously experienced. They advised that if the primary goal is to identify the most severe usability problems as quickly as possible, there seem to be some benefit of relying on novices rather than experts. But they also recommended including self-reported usability problems as a measure, especially if there is a wide range of possible task scenarios that can’t be covered in a usability test.

Novices Finding More Problems than Experts

Five studies found novices uncovered more problems than experts.

Bourie et al  (1997) observed 10 nurses using an online patient assessment application. Novice usage was three weeks with the system versus 1.5 to 3 years for experts. The authors described novice users having more problems with the system than the experts (although the number and severity weren’t specified).

Donker and Reitsma (2004) tested 70 Dutch kindergarteners and first graders on an educational reading software program. Experts were children who had been using the software three times a week for at least three months or two times a week for six months. They reported novice children encountered more problems than experts while using educational software.

Gerardo (2007) had 23 Norwegian participants attempt 14 tasks in an ERP system for small to medium businesses. The 12 experts in the study had used the system before, but were unfamiliar with the new interface. In contrast, the 11 novices had no experience with the current product but had used a competing product for years (they had domain experience but not specific product experience).

The author reported novice users revealed more usability problems than experts and concluded that:

“It is therefore likely that the expert user’s usability problems will be detected through the use of novice users in usability tests. If a usability practitioner has to prioritize between recruiting novices and experts for a usability test after a major redesign, the practitioner will gain more by recruiting novice users.”

Faulkner and Wick (2005), in a study of 60 participants attempting tasks on a timesheet application, recorded user deviations from intended actions. These deviations were interpreted as symptoms of usability issues.

The authors differentiated between application experience and computer experience with three levels:

  • Novice/novice: < 1 year of computer experience, no application experience
  • Expert/novice: > 1 year experience using computers, no application experience
  • Expert/expert: > 1 year experience using computers, > 1 year using the application

They reported novices committed three times more deviations from the optimal path than experts (66 vs 19).

Kjeldskov et al. (2005) had 7 nurses in Denmark use an electronic patient record system in a usability evaluation. 15 months later the same nurses who had been using the system extensively participated again in a usability evaluation with the same tasks. They found that novices generally encountered more usability problems: 93% vs 70% critical and 80% vs. 61% severe for novices and experts respectively.

While not a usability study, Shluzas et al (2013) asked 18 nurses to specify requirements of a drug delivery system [pdf]. Novices in the study had some experience with injections compared to experts who had substantially more (about 6 months vs. 17 years of experience). They found novice users cited requirements associated with product usability over two times as often as did expert users (39.4% vs. 17.1%), and experts cited requirements associated with product functionality over two times as often as did novices (35.4% vs. 16.7%). This suggested a different view of potential problems.

Experts vs Novices in a Social Media Usability Test

While we conduct studies regularly at MeasuringU, few studies directly compare novice and experienced users in the same study. A study we recently conducted on a social media platform examined the differences in usability issues between five expert (“power”) high-tech users and five novice, low-frequency, low-tech users. In this study, technical savviness and application experience were combined into one level, similar to the Faulkner and Wick combination. The novice participants, in this case, had some familiarity with the system (accessing only a few times per year) but lacked knowledge of common tech terms. Experts used the system daily and were familiar with all technical terms.

A total of 48 insights and problems were observed among the 10 participants. Novice participants encountered 40 (83%) of the issues and experts 32 (67%) of issues. There was a good overlap in issues between the groups as shown in Figure 1. Novices and experts both encountered 24 (50%) issues at least once. For unique issues, novices encountered 16 problems/insights experts didn’t, and experts encountered 8 that novices did not.

All Problems & Insights

Figure 1: Overlap in problems found between expert and novice users on a social media platform.

Problems were also rated on a three-point severity scale as shown in Figure 1:

  1. Minor: Possible hesitation as participant attempts task, as well as slight irritation (30 issues)
  2. Moderate: Causes occasional task failure for some participants and moderate irritation (6 issues)
  3. Critical: Leads to task failure; causes participant extreme irritation (12 issues)

A similar pattern was seen across all levels of severity where novices uncovered problems experts didn’t critical (2), moderate (2), and minor (12). Experts uncovered 8 minor issues novices did not, showing that including both novice and experts provides a more holistic view.

In short, novices encountered more total problems/insights compared to experts and almost twice as many unique issues that experts didn’t.

Summary & Takeaways

A review of the literature and the study we conducted on experts and novices revealed a few things.

  1. Novices likely will uncover more issues, but not always. Of the 8 studies reviewed, 6 showed that novices uncovered more usability issues than experts. In many cases, novices also uncovered more severe usability issues than experts.
  2. The distinction between novice and expert is fluid. While there is general agreement that both knowledge and frequency of use differentiate experts and novices, there is less agreement on what the right duration and knowledge thresholds are. Despite the conventions by Dumas and Redish, differences can be days or years. This isn’t necessarily a bad thing, as the context will often dictate the delineation.
  3. Use both novices and experts for a holistic view of the experience. The evidence suggests that both novices and experts bring perspectives that aren’t necessarily an easy substitute for each other. Some studies (including ours) showed experts uncovered issues novices did not. If possible, include both novices and experts when looking to uncover the most usability issues.
  4. If testing with only experts, consider encouraging experts to articulate problems they foresee novice participants having. The expert user’s mental model and understanding of the software may allow them to identify potential trouble points.
  5. Small sample sizes may mask patterns, but meta-analysis helps. As is the case with other research (e.g. overlap in problems between HE & UT and the evaluator effect) the studies reviewed here generally have smaller sample sizes and reduce the opportunity to uncover similarities or differences between novices and experts. However, by looking across studies (a meta-analytic technique) you can look for patterns that single studies may not uncover. In this case, the pattern was generally that novices uncover more usability issues than experts.

Thanks to Jim Lewis for commenting on an earlier version of this draft.

from MeasuringU https://measuringu.com/novice-expert-issues/

The best free online courses of 2017 according to the data


The results are in! In 2015, Class Central first published a ranking of the best online courses of the year based on reviews from our users. I did it again in 2016. Now I’m back with a list of the best online courses of 2017. Like last year and the year before, this year’s list is based on thousands of reviews written by our users.

The methodology is simple. I made a list of all the courses that were offered for the first time in 2017 (which comes out to be over 2,000 courses), ranked the courses by the Bayesian average of their ratings, and filtered out the ones with less than ten reviews.

As you will see below, some of the highlights of this year’s ranking include: a new course by the team that created Learning How To Learn, one of the most popular MOOCs of all time; a new course from Andrew Ng, one of the founders of the modern MOOC movement; and, for you Italian speakers, three new courses from Italy’s University of Naples Federico, which started offering its MOOCs on the edX platform in 2017.

So without further ado, here are 2017’s best online courses:

Mindshift: Break Through Obstacles to Learning and Discover Your Hidden Potential
McMaster University via Coursera
Mindshift is designed to help boost your career and life in today’s fast-paced learning environment. Whatever your age or stage, Mindshift teaches you essentials such as how to get the most out of online learning and MOOCs, how to seek out and work with mentors, the secrets to avoiding career ruts (and catastrophes) and general ruts in life, and insights such as the value of selective ignorance over general competence.
★★★★★ (1250 ratings)

Mountains 101
University of Alberta via Coursera

Mountains 101­­ is a broad and integrated overview of the mountain world. This 12-lesson course covers an interdisciplinary field of study focusing on the physical, biological, and human dimensions of mountain places in Alberta, Canada, and around the world. Specifically, we’ll study the geological origins of mountains, how they’re built-up and worn-down over time; we’ll learn about their importance for biodiversity and water cycles, globally and locally; we’ll explore their cultural significance to societies around the globe, and how that relationship has evolved over time; and we’ll learn how mountains are used, how they’re protected, and how today they’re experiencing rapid change in a warming climate.
★★★★★ (273 ratings)

Quantum Mechanics for Everyone
Georgetown University via edX

Quantum Mechanics for Everyone is a four-week long MOOC that teaches the basic ideas of quantum mechanics with a method that requires no complicated math beyond taking square roots (and you can use a calculator for that). Quantum theory is taught without “dumbing down” any of the material, giving you the same version experts use in current research.
★★★★★ (24 ratings)

Extinctions: Past and Present
University of Cape Town via FutureLearn

This free online course explores how life on earth has been shaped by five mass extinction events in the distant past. At present, biodiversity is facing a crisis, with the prospect of a sixth extinction event today.
★★★★★ (42 ratings)

Viruses & How to Beat Them: Cells, Immunity, Vaccines
Tel Aviv University via edX

Learn how our immune system fights viral disease and make better vaccination decisions with a clearer understanding of Cells, Viruses, and Immunity.
★★★★★ (21 ratings)

Basic Spanish 2: One Step Further
Universitat Politècnica de València via edX
Beginner’s course for learners of Spanish that focuses not only on language, but also on cultural aspects, specifically designed for English speakers.
★★★★★ (57 ratings)

Comprendere la filosofia
University of Naples Federico II via edX

Che cosa è la filosofia? Questo corso offre un racconto del pensiero filosofico attraverso quattro epoche da quella antica cosidetta della contemplazione a quella più recente.
★★★★★ (21 ratings)

Positive Psychiatry and Mental Health
The University of Sydney via Coursera
In this course, we will explore different aspects of good mental health as well as provide an overview of the major kinds of mental disorders, their causes, treatments and how to seek help and support. The course will feature a large number of Australian experts in psychiatry, psychology and mental health research, and we will also hear from “lived experience experts”, people who have lived with mental illness, and share their personal stories of recovery.
★★★★★ (13 ratings)

Dante tra poesia e scienza
University of Naples Federico II via edX

La Commedia di Dante è una delle opere più tradotte e stampate nelle lingue e nei dialetti del mondo. Un testo scritto nel 1300 che affronta temi ancora oggi attuali, e che può rendere l’uomo del nostro tempo più vicino «a quell’amore che move il sole e l’altre stelle.
★★★★★ (15 ratings)

Introductory AP® Microeconomics
Massachusetts Institute of Technology via edX

This economics course is an introduction to basic microeconomic principles. You will learn how individuals make decisions ranging from what type of goods to buy to how many hours to work, and how firms make decisions ranging from how many workers to hire to what prices to charge.
★★★★★ (31 ratings)

Introducción a la programación orientada a objetos en Java
Universidad de los Andes via Coursera
¡Le damos la bienvenida al curso de Introducción a la programación en java por objetos de la Universidad de los Andes! El propósito de este curso es ofrecerle un ambiente interactivo orientado a construir aprendizajes sobre el lenguaje de la programación en Java para la creación y manipulación de objetos.
★★★★★ (17 ratings)

EU policy and implementation: making Europe work!
Leiden University via Coursera
People have become more critical of European policy and often seem to prefer local policy solutions in response to globalisation problems. How do you experience EU policy? Does it help? And if not, how can we change this?
★★★★★ (35 ratings)

Quantum Mechanics: 1D Scattering and Central Potentials
Massachusetts Institute of Technology via edX

In this quantum physics course you will learn the basic concepts of scattering — phase-shifts, time delays, Levinson’s theorem, and resonances — in the simple context of one-dimensional problems. We then turn to the study of angular momentum and the motion of particles in three-dimensional central potentials.
★★★★★ (11 ratings)

Patrick Henry: Forgotten Founder
University of Virginia via Coursera
Patrick Henry, who helped to ignite a revolution, deserves better. This course will explore how he overcame challenges to reach the pinnacle of Virginia politics and unite Americans behind a challenge to Britain — the eighteenth century’s super-power, why he opposed the U.S. Constitution, and why he then came out of retirement to defend the people’s Constitution against the attacks of Jefferson and Madison.
★★★★★ (13 ratings)

L’Italiano nel mondo
University of Naples Federico II via edX

La diffusione dell’italiano nel mondo è veicolata da canzone, cinema, teatro, opera lirica, gastronomia, design che diffondono anche per la lingua un’immagine legata alle eccellenze italiane. Questo corso ti guiderà nella comprensione della lingua italiana, nel suo evolversi nell’uso quotidiano ed in rapporto alle diverse funzioni cui è destinata.
★★★★★ (21 ratings)

Introdução ao Controle Moderno
Instituto Tecnológico de Aeronáutica via Coursera
Este curso lhe dará a base necessária para entender técnicas mais avançadas de controle moderno.
Você aprenderá como representar a dinâmica de um sistema no espaço de estados, como analisar um sistema no espaço de estados, como projetar uma realimentação de estado e como projetar um observador de estado.
★★★★★ (11 ratings)

Whole genome sequencing of bacterial genomes — tools and applications
Technical University of Denmark (DTU) via Coursera
The course will give the learners a basis to understand and be acquainted with WGS applications in surveillance of bacteria including species identification, typing and characterization of antimicrobial resistance and virulence traits as well as plasmid characterization.
★★★★★ (17 ratings)

Neural Networks and Deep Learning
deeplearning.ai via Coursera
If you want to break into cutting-edge AI, this course will help you do so. Deep learning engineers are highly sought after, and mastering deep learning will give you numerous new career opportunities. Deep learning is also a new “superpower” that will let you build AI systems that just weren’t possible a few years ago.
★★★★★ (10 ratings)

Deciphering Secrets: Unlocking the Manuscripts of Medieval Toledo (Spain)
Universidad Carlos iii de Madrid via edX

This course evaluates the medieval history of Toledo from the reign of King Alfonso “The Wise” (1252–1284) until the creation of the blood purity statutes in the 1450s.
★★★★★ (11 ratings)

Python for Data Science
University of California, San Diego via edX

In the information age, data is all around us. Within this data are answers to compelling questions across many societal domains (politics, business, science, etc.). But if you had access to a large dataset, would you be able to find the answers you seek?
★★★★★ (37 ratings)

from freeCodeCamp https://medium.freecodecamp.org/the-best-free-online-courses-of-2017-according-to-the-data-bd7c0077fb94?source=rss—-336d898217ee—4

If Nobody Reads Your Research, Did it Really Happen?


How great research and poor social skills can give your work a bad case of “Schrödinger’s Research”

Lesson 1: Make it eye-catching

If you can’t draw a line specific research you conducted to a change in the product, you may be experiencing a case of “Schrödinger’s Research.”

Don’t sweat! Schrödinger’s Research is a common phenomenon in the user experience industry. It occurs when bright researchers conduct brilliant UX studies, but the insights never make it out of their brain and into the brain of their stakeholders.

It’s as if the research might never have taken place at all.

Schrödinger’s Cat is a famous thought experiment highlighting the observer effect in quantum physics. If a cat is in a box with poison and has a 50/50 chance of surviving, the cat could theoretically be alive or dead, or both, until someone looks inside the box and checks.

Just like Schrödinger’s Cat, your research could be useless, impactful, or both — but it just isn’t anything until someone looks inside the box.

An Argument for Waving Your Research Around Like A Fucking Flag

Companies like Facebook tie promotions and raises to “impact” employees have upon the project for a reason. Though this approach has a few downsides that I’ll explore in another article, it does prompt researchers to tie the impact of their research to specific product changes.

When this works well, it incentivizes researchers to more proactively share their findings and follow through on areas of interest with design and product management to make sure improvements ship.

When you have a bad case of Schrödinger’s research, this may mean you can’t prove you’ve had any impact at all on the product.

This article will cover the few major steps in ‘socializing’ your research — or proactively bringing it into the design or decision making processes.

In general, we socialize research for a few company-wide benefits:

  • So the product is inspired by the user — user experience research findings shared early on in the design process can inspire elements of a design. This changes your product design process from “guessing and checking” to something more human centered.
  • So the product team makes better decisions — if designers and product managers are aware of the limitations and preferences of their user, they’ll make better UI and interaction decisions the first time through.
  • So the user becomes the ‘judge’ — teams that make decisions based on user experience research are less likely to steer towards what they personally prefer at the expense of the user. This also makes creative decision making more methodical by deferring to data rather than individuals on the design or management team.

Common Causes of Schödinger’s Research

Your team’s research blindness may be caused by any combination of: lack of awareness, ignorance, contempt, day drunkeness, or lack of bandwidth.

More likely though, there’s a problem with your method of communicating your findings.

  • Your method of presentation is boring or hard to absorb ex. dull, text-heavy slide decks or tons of confusing charts.
  • Your distribution channels suck — ex. overcrowded Slack channels, un-used Wikis, un-navigable document folders.
  • Your stakeholders don’t know the benefit of UX research ex. they view research as a yes/no nod on a design, they’re sure they know what’s best for the user.

Show Me What You Got

Even if your research is great, pertinent, timely — it still doesn’t speak for itself. User research, especially at a large company, is a role that requires the researcher to act as a spokesperson and mouthpiece for the user.

Here are a few ways that you can better share and promote your research findings. If you have other methods you employ, please let us know more about them in the comments!

Make Your Findings Interesting & Usable

Above all, the information you communicate must be accurate and given the correct context (ie. sample size, statistical significance).

But once you’ve nailed accuracy, make that shit as colorful, eye-catching and incendiary as possible to get people to read and absorb it.

Here are a few tips on effective slide decks from: UX Research is Boring and Nobody Reads It.

  • Use colors and themes to help stakeholders identify what information the research covers
  • Include a TL;DR and Recommendation slide as an index and for skimmers
  • Don’t just include that an element worked/didn’t. Tell the reader WHY

Make Your Research a Reference

If your research is unfindable, it can’t be used.

I create a research “Directory” for each product I work on with a team and circulate the link with pretty much everything I share. The Directory serves as an index of links. In the Directory, I include the following:

  • Description of product — Work with the product manager to come up with a brief description of the product and its basic functionality. Include a picture if possible.
  • Description of use case / user’s need — Briefly sum up what you know about the specific user and task at hand.
  • Primary Research Questions — What stage of research is this team at? Are we checking concepts against each other? Already fine-tuning usability? Just identifying areas for improvement of efficiency on an older product?
  • Links to Research and Design Resources — Include links to foundational research on user type/demographic trends, or the task the product approaches. Include usability test reports, noting the date and what part of the product was tested so stakeholders can jump to relevant data. Include any live test data
  • Upcoming Studies — I list my upcoming research and information on how to watch online or attend. I try to invest time in getting team mates to watch research because it means better understanding, people to bat around thoughts with, and fewer corrections down the line.
  • POC Information — List points of contact and contact information for engineering, design, product management, data and any other main stakeholders. This can help keep you from becoming the hub of all interactions.

Bring Your Research Directly To Your Stakeholder

I employ three main methods of sharing my research directly with peers.

1:1 Meetings

When I work on product teams I generally meet with the product manager once a week to gauge progress and priorities. I also meet 1:1 about once a week with the designers I work with to look at their most recent work and discuss edge cases and assumptions/concerns to explore in upcoming research.

1:1’s or small group meetings are also an excellent time to introduce the research you’ve just completed. You can answer questions and explore individual follow-up — for example, if a designer will need to re-think an interaction based on user research, you can let them know to plan extra time in their schedule to addres.

Research Read Out is a Terrible Name

Though I haven’t found a better way to refer to collecting people and sharing my research, Research Read Out is a deadly boring title for something awesome.

For each big research report (ex. a diary study or a set of surveys that reveal a trend) I like to organize a read out to share findings with context and answer questions.

Schedule 45 minutes to 1 hour. Ensure you have video conferencing set up, share the link, and record the session for those who cannot be there. Go through your report slide-by-slide, adding a bit of color or real examples to provide context. Photos and video clips from testing are your friend.

Because I like to multitask and the audience is captive

I also use these sessions to assign work or formally call issues out to add to our development or design timelines. I ask people about future availability and put time on the calendar so we remember to follow up.

Don’t be scared. Jokes helps when you’re being this direct. So does owning up to your approach and your intensity.

Speaking up and sharing your research can only help you and your user. When people react negatively to my action-oriented approach, it is to critique my personality rather than my accuracy or effectiveness. A grown woman can survive some shade, especially when my products end up shipping and numbers go up.

Insert Your Findings in the Design Process

User research shouldn’t be conducted in a vacuum. The researcher can work hand-in-hand with the rest of the product team to make sure that the user is at the center of the whole process.

Here are a few of my favorite ways to inject your research and knowledge about the user into the the design process.

Run a Sprint

Once you’ve got a nest of related issues, (for example, all kinds of reports of issues with the login process), it could be time to recommend a design sprint to address the whole section.

Work with the design team to insert user research into the sprint. I like to start sprints with a brief overview of our background knowledge on the user, their preferences and limitations.

When I have the time to get really fancy, I incorporate a quick round of user testing into the end of a sprint so designers can see reactions to the earliest sketches of their work and adjust accordingly.

Get Brainstorm Priorities Right

When your team is planning their next round of work or next set of feature priorities, jump in and insert some research.

Start brainstorms off by listing user needs and user priorities, then discuss company goals and metrics. If you ask your design team to just jump in and “maximize new signups”, you run the risk of designing predatory dark patterns.

“How might we satisfy (USER NEED) in a way that (COMPANY PRIORITY). “

Insert Your User Into Decision Making

Ideally a team is on the same page when it comes to priorities and what gets recommended for build or shipping.

The user researcher’s responsibility is advise the design, check impact with data, and above all, help you user achieve their goals.

As such, feel empowered to speak up in decision making meetings to point people towards relevant data or knowledge that you think is important to know about the user.

For example, if the product is about to ship but you have concerns about people misunderstanding, it is okay to pump the brakes and point people towards the data that makes you feel that way.

In fact, it is your responsibility :)

Share What You Know

Do you have tips or ways you’ve effectively shared your research findings? Please tell us about them in the comments below!


from Prototypr https://blog.prototypr.io/if-nobody-reads-your-research-did-it-really-happen-815bfca103ca?source=rss—-eb297ea1161a—4