What are Heuristics, and how are we running a Heuristic Evaluation for the SBT?

Heuristics are guidelines that help evaluate the usability of a digital product. They are called "heuristics" because they are broad rules of thumb and not specific usability guidelines. There’s no fool-proof way of designing experiences that work for everyone, instead, heuristics are principles that can guide a designer through the design process.

There are a few different proposed guidelines, but one of the most popular is Nielsen’s: 10 Usability Heuristics, which is the one I will be using to measure usability in this evaluation, the evaluation will be carried out by defining a rating system and a goal followed by a task list that the expert will go over and measure their experience against the Heuristics and rate it in order to identify usability issues.

Screenshot 2023-02-09 at 14.39.30.png

What are Nielsen’s: 10 Usability Heuristics? Read them all here, in more detail.

H1  Visibility of system status

H2 Match between system and the real world

H3 User control and freedom

H4 Consistency and standards

H5 Error prevention

H6 Recognition rather than recall

H7 Flexibility and efficiency of use

H8 Aesthetic and minimalist design

H9 Help users recognize, diagnose, and recover from errors

H10 Help and documentation

Rating System and Analysis

While trying to complete the task list I will be measuring the tasks against the rating system to determine the severity of each usability concern indicating what heuristic we’re failing at together with an explanation of the issue and a solution recommendation.

The rating system used in this evaluation goes from 0 to 4:

0  No Problems

1  Superficial Problem

2  Minor Problem

3  Major Problem

4  Fatal Problem

Persona

For the purpose of this evaluation, we will be using George (our passive user persona).

George is a Senior Frontend Developer (C3: 2-4 years of experience) earning 57k/year based in the UK, he works for a tech company on a hybrid basis and his tech stack is HTML, CSS and React.

Goal & Tasks

Goal George has used cord before to find his current job, but after 2 years working in this tech company, he’s not sure if the job he’s doing is his best work.

Lately, George has been questioning himself if the salary he’s being paid is fair and whether or not he should look into a career progression or a career change.

Using the cord’s Salary Benchmarking Tool, George will try to answer all of these questions.

Tasks 1. Figure out if your salary is fair and in line with industry standards 2. Figure out what your salary progression can be if you negotiate a promotion 3. Figure out how companies are paying other people with the same skills as you 4. Compare your role with another one you would be interested in changing into 5. Understand where the data comes from in order to validate your answers

Untitled Database

Summary:

The findings of this report came from the analysis of the Insights - Data Dashboard - Salary Benchmarking Tool. The evaluations were conducted using a Heuristic Evaluation method, which was chosen to evaluate how effective our users of the tool might be able to perform specific tasks on the website. The evaluation was done by 1 UX Designer using Nielsen’s Ten Usability Heuristics.

The tool is serving well its requirements as It is providing enough search filters to help users understand their pay and benchmark salaries.

While the graph is dense in information, it uses cord blue as the primary color combined with other shades of lighter cord blue to highlight certain areas and serve as a differentiator between the comparisons and the main information, the use of white also makes it look modern, professional and aesthetically pleasing.

After reviewing the data from the table above 5 usability problems in the interface were found, based on the goal set. A table detailing the issues is available above and 3 minor usability problems and 2 superficial problems rated here prompted about 8 recommendations to improve the usability of the tool.

Powered by Fruition