The Hidden Requirements: Exploring Emotions with Placebos
summary
Claim: user emotions drive acceptance and market success, so emotional requirements must be explicit. Evidence: literature reviews and experiments, interviews, surveys, observation, UDUM ethnography, DEQ/PMEmo questionnaires and a usability‑of‑emotions matrix. Surprising numbers: almost half the office thermostats are fake and one third of NYC crosswalk buttons are disconnected show simple placebos change feeling. Case: Brazilian social workers get a rewritten system centered on satisfaction and embrace it — placebos like progress bars, fake save buttons and slowed CoinStar machines also improve perceived experience.
AI-written summary · about
chapters (14)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 1:20Introduction: Why Emotions Matter in Software
- 5:10Damian's Background & Relevance to Emotional Software
- 7:30The Importance of Emotions in Software Development
- 14:00Exploring Placebos: What They Teach Us About User Behavior
- 19:35Emotional Responses & Their Impact on Decision-Making
- 24:50Supporting the Claim: Emotions in Software with Famous Quotes
- 29:00What is the Purpose of Software? A Deep Dive
- 33:30Identifying Emotional Requirements in Software
- 38:15Practical Tips for Emotional Requirement Gathering
- 46:50Case Study: Brazilian Social Workers and Emotional Software
- 59:30Emotional Requirements: Integrating Them into Software Development
- 1:14:15How to Test Emotional Requirements in Software
- 1:25:40Conclusion: Why Emotional Software is Critical for Success
related talks
41mOnce more with feeling: the role of emotions in design
32mUnderstanding and Measuring User Emotions: The Missing Puzzle Piece
27mYour Emotions Are Not an Anti-Pattern
38mYour Emotional API
37mProgramming Empathy: Emotional State Machines
27mYour emotions are not an anti-pattern
23mHacking Your Emotional API
03mUnderstanding the Design of Emotionally Impactful Game Feel