Log In
Or create an account -> 
Imperial Library
  • Home
  • About
  • News
  • Upload
  • Forum
  • Help
  • Login/SignUp

Index
Tragic Design: The Impact of Bad Product Design and How to Fix It Foreword Preface
About This Book O’Reilly Safari Comments and Questions Acknowledgments
Jonathan Cynthia
1. Introduction
The Interface that Killed Jenny The Role and Responsibilities of Designers
The Client Paradox Understanding and Identifying Hidden Costs
Conclusion Key Takeaways
2. Design Can Kill
Stupid Errors Versus Stupid Users Case Study 1: Therac-25
Interface Diagnosis
First issue Second issue Third issue
Testing Is Not Optional
Case Study 2: Ferry Crash in New York City
Use Appropriate Visual Feedback
Case Study 3: Ford Pinto
Diverging from the Original Question
Case Study 4: Flight 148 Alternatives to Modes Fault Tree Analysis Conclusion Key Takeaways
3. Design Can Anger
Why Should You Care About Emotions? Characteristics of Impolite Technologies
Impolite Technologies Are Selfish
Xbox’s frequent updates Google Calendar event reminders
Impolite Technologies Are Lazy
Self-checkout
Impolite Technologies Are Gluttons
iTunes’s silent downloads
Impolite Technologies Are Attention Freaks Case Study: Microsoft Office Assistant Polite Technologies
Dark Patterns
Bait and Switch Fake Content Forced Continuity Friend Spam Misdirection Roach Motels Bonus: Trick Question The Drawbacks
It can cost your company money It will hurt other metrics
Winning the Argument Persuasion Is Not Deception
Conclusion Key Takeaways
4. Design Can Sadden
The “Dribbblelisation” of Our Users Inadvertent Cruelty Self-Blame and Humiliation “Power User” Features
Shortcuts Make the Settings are Understandable
Allowing for Abuse How to Prevent Causing Sadness
Avoid Confusing a Change of Emotion with a Change of State in a Database Don’t Underestimate the Power of Symbols Remember that Every User Will Die Use the Sad Sheriff Reprioritize Feature Development Organize Catastrophic Brainstorms Change Your Usual Testing Scenarios
Raising the stress level Performing usability testing in context
Design for Failure
Conclusion Key Takeaways
5. Design Can Exclude
Accessibility
A Case for Accessible Design
It affects a lot of people It is good for business It benefits everyone It’s required by law It’s simply the right thing to do
Making Your Service Accessible
Don’t rely on color to convey information Pick high-contrast text colors Use alt text Avoid text embedded in images Provide context for hyperlinks Simplify your textual content Avoid automatic image sliders (or carousels) Design accessible forms Consider accessibility outside of the browser Treat internet access as a human right
Inspiring Change Within Your Organization
Diversity, Inclusive Design, Design for All
Words, Powerful Words Diversity-Conscious Design: Challenging the Status Quo
Injustice
Food Stamps Parking Tickets Prison Visiting The Fate of a Nation
Conclusion Key Takeaways
6. Tools and Techniques
Gather as Much Data as You Can
Search for People Who Hate Your Product Quantitative Versus Qualitative: Going Above and Beyond Likert Scales
Learn to Recognize Emotions
Decoding Expressions of Emotion and Body Language Presenting These Observations Mapping Emotional Data
Plutchik’s wheel Customer journeys
Conclusion Key Takeaways
7. What We Can Do
What We All Can Do
Vote Speak Up Support Others Share Good Examples Start Your Own Company Practice Empathy Everyone Is a Designer
What Designers Can Do
Work Where You Are Needed Learn to Raise Your Voice Take a Stand Be a Great Designer
Be a world-class communicator. Use the user-centered design methodology. Use data as ammunition. Keep a student’s mindset. Teach and mentor others. Polish your process. Take your time. Be engaged. Take a step back. Branch out. Contribute. Ask who is losing and who is winning.
Stop Reading This Book... (Soon!)
What are you passionate about? Allocate your time. Find an outlet. Tell a friend.
8. They Are Doing Good
Physical Good Emotional Good Inclusion Justice What Will You Do?
A. Companies, Products, and Links About the Authors Colophon Index Copyright
  • ← Prev
  • Back
  • Next →
  • ← Prev
  • Back
  • Next →

Chief Librarian: Las Zenow <zenow@riseup.net>
Fork the source code from gitlab
.

This is a mirror of the Tor onion service:
http://kx5thpx2olielkihfyo4jgjqfb7zx7wxr3sd4xzt26ochei4m6f7tayd.onion