1. Visibility of System Status with examples

Today I want to write about the first of Jakob Nielsen’s Ten Usability Heuristics 'Visibility of System Status'. I will try to cover the topic by explaining some examples.

Definition: The visibility of system status refers to how well the state of the system is conveyed to its users. Ideally, systems should always keep users informed about what is going on, through appropriate feedback within reasonable time.

Let's jump into a simple example to understand the definition easily. Whenever we try to upload our files into google drive or any other cloud system, we see it's telling us how much the uploading is done or the remaining time by showing percentage (%), number file or a bar. Look at the images below:

This principle states that the user should know what’s going on inside the system. The system is providing enough feedback after pressing the UPLOAD button. If the system provide the feedback in reasonable time, it allows user to find the error and fix it as soon as it made.

Here is another example that we see while purchasing a product online. Imagine we are trying to buy Jeans from a retail shop. First, we choose a Jeans from products page, select its color, size, fit (slim fit, straight fit, skinny fit etc). Then click on ADD TO CART button.

How do feel when you see the item is not available or the size is not available in Cart List? Do you become angry after not getting any feedback by clicking ADD TO CART button? The system not giving feedback on the action you did.

You saw the item in the products list but something gone wrong now. Look at the above screenshots. The system keeps telling the user which size is available, which color is out of stock. After selecting the item you get a pop up 'Your item is added to cart', now you feel comfort in using the system as you know what state are you in the system and you continue the shopping.

Some other examples showing how to give feedback to users in appropriate time. We can do that by image, illustration, text even with sound. After posting on twitter, emailing from mail application we hear a 'swoosh' sound, its also a good example.

I want to add the conclusion from NN Group article : The visibility of system status is a basic tenet of a great user experience. At its core, this heuristic encourages open and continuous communication, which is fundamental to all relationships — whether with people or devices. Users who are uninformed about the system’s current status cannot decide what to do next in order to accomplish their goals, nor can they figure out if their actions were effective or if they made a mistake. Don’t blindfold your users!

Thanks for reading! I will write the second heuristics 'Match between system and the real world' soon. Let's make the experience great!

Reference : Neilsen Norman Group

Medium Article