Thanks for the summary of the Heuristics, your video helped me gain a deeper understanding of Nielsons 10 Usability heuristics so that i could finish up a particularly difficult class in my bachelors degree program.
01) Visibility of system status (0:06) 02) Match between system and the real world (0:38) 03) User control and freedom (1:18) 04) Consistency and standards (1:49) 05) Error prevention (2:18) 06) Recognition or recall (2:54) 07) Flexibility and efficiency of use (3:24) 08) Aesthetic and minimalist design (4:07) 09) Help users recognize, diagnose and recover from errors (4:45) 10) Help and documentation (5:06)
For your notes: 1. Visibility of system status: the system should always keep the user informed about what is going on for appropriate feedback within reasonable time 2. Match between system and the real world: the system should speak the user's language with words and concepts that are familiar to the user 3. User control and freedom: users often make mistakes and that they will need a clearly marked emergency exit to get back to where they really want to be 4. Consistency and standards: users should not have to wonder whether different words or situation mean the same thing in that you should therefore have a convention and continually across your entire platform 5. Error prevention: the best designs don't only have great error recovery but prevent users from making those errors 6. Recognition or recall: systems should minimize the user's memory load by making objects, actions, and options more visible (prioritize recognition over recall) 7. Flexibility and efficiency of use: our system should incorporate accelerators which are unseen to the novice user but that allow the expert user to navigate faster with frequent actions 8. Aesthetic and minimalist design: dialogues should not contain irrelevant information 9. Help users recognize, diagnose and recover from errors: error messages would be expressed in plain languages and precisely indicate the problem 10. Help and documentation: even though the system can be used without documentation it may be necessary to provide help and documentation
This video is an OK intro into Nielsen's 10 Heuristics but it does make some rather confusing examples here and there. I recommend NN Group's own videos series for a better understanding of the subject. Linked here: th-cam.com/play/PLJOFJ3Ok_idtb2YeifXlG1-TYoMBLoG6I.html BTW the Ikea example was not really good. Those who have assembled Ikea furniture know that those nicely designed instructions are actually REQUIRED and not optional when you are putting an Ikea piece together...
Great summary, although I think there's a misunderstanding with the "Recognition rather Recall"... I think it should be more in the way of using behaviors that the user already know vs teaching new ones
It's right in the video, it's about how it's much easier to remember when you have key words/icons/phrases than nothing at all. Recognition is easier than recalling!
This reminds me of the tiktok where the girl makes her own Wes Anderson short, and also of Grand Budapest hotel. Aka I might make a comp vid of GBH scenes to this audio.
I am not sure about your assumptions about children's interfaces. Yes, they need to be crystal clear in terms of navigability. But many of the new interfaces (see nosycrow.com/apps/) do not assume outcomes.
This video is terrible. The audio quality sucks. The blue slides are confusing because the video's title indicates a quantity of 10, but there were 25 of these slides, and none of them were numbered. Additionally, the slides have multiple misspellings, grammatical errors, Randomly Capitalized Text, and English syntax errors. This is not a good video to show in any academic or educational context.
Saying it's "terrible" is a bit harsh. The content is good, the examples are good, and the delivery is good. Although the audio quality could be better.
0:06 - Visibility
0:40 - Match System & Real World
1:18 - User Control
1:49 - Consistency
2.18 - Error Prevention
2:54 - Recall
3:24 - Flexibility
4:07 - Minimalist Design
4:45 - Error Recovery
5:06 - Help
thank boom
er
lemme guess.... you got the same college assignment
12 years later, still helps!
Cheers Bro
Thanks for the summary of the Heuristics, your video helped me gain a deeper understanding of Nielsons 10 Usability heuristics so that i could finish up a particularly difficult class in my bachelors degree program.
A very clear and concise video with examples. Top marks!
Bravo Jakokb! You even followed your own advice and got it across simply and clearly. THANK YOU FOR POSTING THIS!
Thank you. No other video demonstration can be better than this. Your examples rock!
01) Visibility of system status (0:06)
02) Match between system and the real world (0:38)
03) User control and freedom (1:18)
04) Consistency and standards (1:49)
05) Error prevention (2:18)
06) Recognition or recall (2:54)
07) Flexibility and efficiency of use (3:24)
08) Aesthetic and minimalist design (4:07)
09) Help users recognize, diagnose and recover from errors (4:45)
10) Help and documentation (5:06)
Thanks for this video. It was super easy to understand and very simple. Also those short phrases like "oops" really made it easy to remember
For your notes:
1. Visibility of system status: the system should always keep the user informed about what is going on for appropriate feedback within reasonable time
2. Match between system and the real world: the system should speak the user's language with words and concepts that are familiar to the user
3. User control and freedom: users often make mistakes and that they will need a clearly marked emergency exit to get back to where they really want to be
4. Consistency and standards: users should not have to wonder whether different words or situation mean the same thing in that you should therefore have a convention and continually across your entire platform
5. Error prevention: the best designs don't only have great error recovery but prevent users from making those errors
6. Recognition or recall: systems should minimize the user's memory load by making objects, actions, and options more visible (prioritize recognition over recall)
7. Flexibility and efficiency of use: our system should incorporate accelerators which are unseen to the novice user but that allow the expert user to navigate faster with frequent actions
8. Aesthetic and minimalist design: dialogues should not contain irrelevant information
9. Help users recognize, diagnose and recover from errors: error messages would be expressed in plain languages and precisely indicate the problem
10. Help and documentation: even though the system can be used without documentation it may be necessary to provide help and documentation
great examples , better than multiple websites who all quote the same thing. Thank you!
This made Usability Heuristics much easier to understand. Thanks!
Watching this video for the second time, this really help me in my "Human Computer Interaction"
thanks a lot Dear Sir :)
from 2023, I appreaciate what you done
What's with the creepy yellow man bear pig at the end D:
I think that's Mr. Oizo!
Loved this explanation! Very clear and concise and love the visuals! Thank you!
Yelllow Djungelskog
Yelllow Djungelskog
This video is really helpful for me understand the 10 usability heuristics. thank you so much:)
Great explanation.. many thanks
This was so helpful!
Really helpful.
such a wonderfull explanation!!!! KUDOSSSSS TO U
This video is an OK intro into Nielsen's 10 Heuristics but it does make some rather confusing examples here and there. I recommend NN Group's own videos series for a better understanding of the subject. Linked here: th-cam.com/play/PLJOFJ3Ok_idtb2YeifXlG1-TYoMBLoG6I.html
BTW the Ikea example was not really good. Those who have assembled Ikea furniture know that those nicely designed instructions are actually REQUIRED and not optional when you are putting an Ikea piece together...
What was the song in the background? It made the video's message seem INTENSE! It was also pretty cool. :)
Nice and understandable examples. Thank you! :D
Thanks for the great examples. So much easier to understand now. :D
Great summary, although I think there's a misunderstanding with the "Recognition rather Recall"... I think it should be more in the way of using behaviors that the user already know vs teaching new ones
It's right in the video, it's about how it's much easier to remember when you have key words/icons/phrases than nothing at all. Recognition is easier than recalling!
Great video! But what up with the creepy doll at the end? :S
This reminds me of the tiktok where the girl makes her own Wes Anderson short, and also of Grand Budapest hotel. Aka I might make a comp vid of GBH scenes to this audio.
I am not sure about your assumptions about children's interfaces. Yes, they need to be crystal clear in terms of navigability. But many of the new interfaces (see nosycrow.com/apps/) do not assume outcomes.
Thank you. I thought I was the only one thinking this...
When you're working on software, it's easy to forget a lot of this stuff. More people should have an understanding of it tbh.
Nielsen Norman Group did part of it - And this video is based on Nielsen's work. So...
..AMAZING!! U helped me to get it tanx
That is Flat Eric famous for his appearance in the music video Flat Beat by Mr. Oizo.
oooh, I thought that WAS Mr. Oizo!
thank you sir nice example for kids to understand
request -voice in not clear
Whoever did UI research for Microsoft Windows 8 should watch this video
Haha, definitely!
well done
13 years later and helping me study for my Computer Science exam (in about an hour😭)
not me?
Id say that W8 follows those rules to the letter.
Good video. I liked the examples. I believe his name is pronounced Yakob, not Jacob.
Is it though? Or is that a common misconception?
thanks :)
Im just another scrub pushing through *Compsci 345* content..... sigh
Wow...woaaa
Music is too loud.
Haahaha, I really like this. Good use of examples :)
fredick lwe
Music and voice together are annoying!!!!!!!!!
sounds like a nerd!
This video is terrible. The audio quality sucks. The blue slides are confusing because the video's title indicates a quantity of 10, but there were 25 of these slides, and none of them were numbered. Additionally, the slides have multiple misspellings, grammatical errors, Randomly Capitalized Text, and English syntax errors. This is not a good video to show in any academic or educational context.
Thanks for your feedback Gregg !
Saying it's "terrible" is a bit harsh. The content is good, the examples are good, and the delivery is good. Although the audio quality could be better.
Bad UX - annoying background music