RegularGeek post: Confusion As A Usability Defect http://t.co/t7dbI4XX
As a software engineer, you should always be looking for the location of the next defect or at least clues that something is wrong. The problem is that most developers have been trained to wait for feedback from the QA team. In many cases, the QA team is following a script or has been trained on how to use the system, so some clues get lost in the familiarity. Michael Bolton has an interesting post regarding confusion as an oracle. When the QA team is confused, that points to potential issues and should be used as a heuristic.
Link – Trackbacks