with the top four reasons all relating to product usability: frequent requests for changes by users, overlooked tasks, users' lack of understanding of their own requirements, and insufficient user analysis communication and understanding (Lederer & Prassad, 1992).
the ATM's screen. 2. The user takes a valid Huntington bank card from their wallet. 3. The user slides the bank card fully into the marked slot. 4. The user waits five seconds for the ATM to respond. Feedback: The ATM displays "Please enter your four-digit personal identification number" on the screen. 5. Using the physical keypad attached to the ATM, the user correctly enters their four-digit PIN. 6. The user presses the Enter key. […] 7. The user removes their bank card and returns it to their wallet. 8. The user watches the screen for 15 seconds. Feedback: The ATM redisplays the welcome message. 9. The customer leaves.
developers tend to adopt a "satisficing" strategy that focuses on initial, satisfactory, but less than optimal, solutions. Never be satisfied with a single opinion or the first idea. It is best to "saturate the design space" with ideas before making decisions and to consider alternatives (i.e., better design solutions, throughout the design process). Ball, L.J., Evans, J.B.T. And Dennis, I. (1994), Cognitive processes in engineering design: A longitudinal study, Ergonomics, 37(11), 1753-1786.
you typically find in usability testing - confusing concepts, poor terminology, layout problems, lack of feedback, etc. • Missing (or misspecificed) functional requirements. Users often have needs that the development team isn't aware of, or the team may have a mistaken assumption about what functionality will satisfy a user requirement. • Preference for one design alternative. Sometimes there are multiple ways to provide a function and they're equally easy to implement. But users may have a clear preference for one way over another. http://www.paperprototyping.com/what_examples.html
My (current user) info 4. Other users on this account 5. My sales rep contact info 6 Current account plan 7. Link to change search preferences 8. Date account was created 9. People rarely view or change insurance info 10. Any user can edit anything except other users' info 11. Changing password is the most likely action 12. People might come here to change search preferences (which are on a separate page) http://37signals.com/papers/introtopatterns/
users on this account 5. My sales rep contact info 6. Current account plan 9. People rarely view or change insurance info 10. Any user can edit anything except other users' info 10. Any user can edit anything except other users' info 10. Any user can edit anything except other users' info 10. Any user can edit anything except other users' info 3. My (current user) info 11. Changing password is the most likely action 10. Any user can edit anything except other users' info A B C D E F 8. Date account was created G 7. Link to change search preferences 12. People might come here to change search preferences (which are on a separate page) H
change insurance info 10. Any user can edit anything except other users' info B 4. Other users on this account 10. Any user can edit anything except other users' info D 6. Current account plan 10. Any user can edit anything except other users' info F 1. Company info 10. Any user can edit anything except other users' info A 3. My (current user) info 11. Changing password is the most likely action 10. Any user can edit anything except other users' info C 5. My sales rep contact info E 8. Date account was created G 7. Link to change search preferences 12. People might come here to change search preferences (which are on a separate page) H