Have you ever noticed how many products appear to be designed by someone who has never used a product of that kind before? The Thoughtless Design of Everyday Things by Karl Wiegers presents more than 160 examples of products that violate 9 fundamental design principles. These examples of thoughtless design reveal 70 specific lessons that can help designers craft the user experience. There are also nearly 50 examples of products with particularly good designs. The book describes numerous specific practices for enhancing product usability through usage-centered design strategies. This is an engaging and insightful read for designers, product development managers, and thoughtful and curious consumers.

Requirements and Business Analysis

• No One Expects the Requirements Inquisition: Asking Next-Level Questions
• We Don't Need No Stinkin' Code: Testing Software Requirements
• Tracking Project Status with Requirements
• Specifying Requirements for Outsourced Projects
• Five Requirements Prioritization Methods
• Elements of Requirements Style
• Modeling System States: State-Transition Diagrams and State Tables
• It's Only Logical: Decision Tables and Decision Trees
• Six Tips for Writing Unambiguous Requirements
• Improve the User Experience with Dialog Maps
• 10 Requirements Traps to Avoid
• The Making of a Business Analyst
• Modeling System Events: Action, Reaction, Protection
• How Detailed Should Requirements Be?
• Defining Project Scope: What's In, What's Out
• Revealing Invisible Requirements
• The Fuzzy Line Between Requirements and Design
• The Habits of Effective Business Analysts
• Agile Requirements: What's the Big Deal?
• Hearing the Voice of the Customer

Project Management

• Are We There Yet? Defining Product Release Criteria
• But I Don't Have Time!
• Seven Starting Points for the New Manager
• Rethinking the Triple Constraint: Five Project Dimensions
• Project Retrospectives: Looking Back to Look Ahead
• Motivate Your Team with Recognition and Rewards
• Good Money after Bad: Some Projects Should Die
• Why Is Software Always Ninety Percent Done?
• Six Estimation Safety Tips

Other Topics

• Designing Around Bad Actors and Dangerous Actions
• Perfect Your Designs With Prototypes
• Seven Characteristics of Meaningful User Messages
• Modes of Consulting: What's Your Preference?
• The Core Question about Building Better Software
• The Seven Deadly Sins of Software Reviews
• 66 Lessons from 50 Years of Software Experience
• Making Money While You Sleep: A Passive Income Success Story
• Making Peer Reviews Work for You
• Growing a Culture of Software Quality
• Building a Healthy Software Engineering Culture
• 10 Survival Tips for the Business Traveler
• Six Unobvious Writing Success Tips
• Mind the Crap Gap
• Leverage Your Intellectual Property for Fun and Profit
• The Soft Side of Peer Reviews
• Are You Being Blackmailed by Change Resisters?
• Win-Win Negotiation for Consultants and Trainers
• Twelve Tips For Becoming a Confident Presenter
• Negotiating Achievable Commitments
• Learning from Experience