Cognitive approach to software quality
summary
Talk claims humanity is a technical requirement and offers concrete cognitive findings to act on: change blindness, Dunning Kruger effect, and attention span 12 to 8 seconds are cited as reasons to simplify interfaces, surface clear error handling, and avoid task switching. Recommends early and continuous testing, heuristics-driven reviews, localization teams (Ukraine India Argentina Poland) and light feedback bots used at Alex group and I CRO to remind teams to communicate; gives form and UX examples and practical measures to test whether changes actually reduce user errors.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:34We, human development team
- 11:40Heuristics and schemas reasoning
- 15:26Perceptual limitations
- 16:25Software quality ingredients
related talks
25mIt's easy to create good looking products, but how about useful ones?
10mA philosophical approach to UX
41mIt’s easy to create good looking products, but what about useful ones
21mTaste Driven Development
27mWhat Makes Good UI Work: Lessons from Cognitive Psychology
12mDesigning AI To Scale Human Thought
38mDesign for Cognitive Bias: Using Mental Shortcuts for Good
44mIt’s Easy To Create A Good-Looking Product, But How About A Useful One?