My Reflection
– “Making space for our users begins with understanding our biases-something all of us have.”
Design for Real Life most definitely stood out to me out of all the texts. The approach matches the way I want to build web applications. I do not want to build web applications for the 'perfect' user, but people with real lives, identities and feelings.
I chose this text because it made me rethink how we treat “edge cases”. Meyer and Wachter-Boettcher argue that edge cases are often the people most affected by bad design. This idea resonated with me. Technology should help everyone, not leave people out just because they don't fit the norm. Reading this chapter reminded me that good design starts with humility and being aware of my own assumptions.
The section, about Understand Your Bias made me think about my habits. The authors explain that System 1 thinking is quick and based on assumptions. System 1 thinking shapes many of our choices and designs. I realised I often picture the 'default' user without meaning to. When I design interfaces it's easy to assume others think, read or feel the way I do. But the chapter showed me that people can experience my website or product in different ways and emotional states. Some might be stressed, anxious, tired, in a hurry, grieving, or even dealing with a sensitive part of their identity. A design choice that seems fine to me could actually cause problems or even harm for someone else. With this in mind, it makes me want to slow down, be more thoughtful and empathetic -also known as System 2 thinking.
Design for Real Life also changed the way I think of 'simple'. Designers often value simplicity. The chapter shows what simple is for one person can be complicated for another person. Take users with Dyslexia or ADHD, they may struggle to read your content because of the way it's laid out across the screen and also because of the style of your chosen fonts – this can also include the font size, line spacing and word spacing. Another example was the gender selector in the chapter. A choice like male or female seems straightforward, but it can be emotionally hard or unsafe for people who don't identify as male or female. This helped me see that 'simple' shouldn't mean 'oversimplified'. Simplicity that leaves people out isn't simple. It shows a lack of understanding of human experiences. When I build web applications, in the future I want to remember that simplicity and inclusion must go together. Clean design matters, but clean design must not cost a person's identity or safety.
Another lesson that shaped my thinking is to ask for what's truly needed. The Robustness Principle shows that a system should be flexible and forgiving, not strict and demanding. I noticed that many online forms ask for personal details to help the system but the user. That reminder is clear: every field, data request and step can affect real people. When I design interfaces, I want to respect the user time, privacy and choices. I think that if information isn't necessary, I should not ask of it.
I want to make products that notice the details of life. The authors point out compassion, as a design tool. They noted that people often miss compassion when people chase innovation or simplicity. When designing interfaces, I want look beyond demographics and personas and think about how people feel and go through.
Design for Real Life gave me more than just design advice, it gave me a new way to think. It showed me that design is a responsibility! Choosing Design for Real Life was about linking my values as a designer, with the belief that the digital experiences should include everyone, especially thinking of those who are often left out.