Designing for myself, but I’m not the user: tales of a UI/UX Designer
Designing for myself, but I’m not the user: tales of a UI/UX Designer
As a UI/UX designer, it’s easy to fall into the trap of designing with ourselves in mind. After all, we spend hours scrutinising every pixel, and it’s tempting to think that if it works for us, it’ll work for everyone. Spoiler alert: It doesn’t. Here’s a playful recount of some of the most relatable mistakes I’ve made along the way, the biases we often hold as designers, and practical solutions to overcome them. Join me as I navigate the whimsical world of design, where our reflections can sometimes lead us astray, and discover how to truly design for the user.
As a UI/UX designer, it’s easy to fall into the trap of designing with ourselves in mind. After all, we spend hours scrutinising every pixel, and it’s tempting to think that if it works for us, it’ll work for everyone. Spoiler alert: It doesn’t. Here’s a playful recount of some of the most relatable mistakes I’ve made along the way, the biases we often hold as designers, and practical solutions to overcome them. Join me as I navigate the whimsical world of design, where our reflections can sometimes lead us astray, and discover how to truly design for the user.
1. The Colour Conundrum
1. The Colour Conundrum
“Pastel colours are so soothing, everyone will love them!”
I once designed an entire app interface using light pastel colours. The palette was soft, calming, and I found it absolutely delightful. But as user feedback started rolling in, the comments were clear: “It’s hard to read,” “The contrast is too low,” “I can barely see the buttons.”
Bias: We often assume our favourite colours will appeal to everyone.
Solution: Test your colour schemes with a diverse group of users. Conduct A/B tests to see which colours resonate best. Utilise accessibility tools to ensure colour contrast meets standards, making the design usable for everyone, including those with colour vision deficiencies.
Lesson Learnt: Just because you love a colour doesn’t mean your users will. Accessibility and user preference should guide your colour choices.
“Pastel colours are so soothing, everyone will love them!”
I once designed an entire app interface using light pastel colours. The palette was soft, calming, and I found it absolutely delightful. But as user feedback started rolling in, the comments were clear: “It’s hard to read,” “The contrast is too low,” “I can barely see the buttons.”
Bias: We often assume our favourite colours will appeal to everyone.
Solution: Test your colour schemes with a diverse group of users. Conduct A/B tests to see which colours resonate best. Utilise accessibility tools to ensure colour contrast meets standards, making the design usable for everyone, including those with colour vision deficiencies.
Lesson Learnt: Just because you love a colour doesn’t mean your users will. Accessibility and user preference should guide your colour choices.
2. Font Fiasco
2. Font Fiasco
“Cursive fonts are so elegant, they’ll make my app look classy.
Fonts are another area where personal taste can lead us astray. I once chose a beautiful cursive font for a navigation menu, thinking it added a touch of elegance. It did, but it also added a touch of confusion. Users struggled to read it, especially on smaller screens.
Bias: We believe that stylish fonts enhance user experience just because they appeal to us.
Solution: Opt for clean, legible fonts that are easy to read across all devices and screen sizes. Test with actual users to get feedback on readability. Remember to prioritise function over form.
Lesson Learnt: Legibility trumps aesthetics. Choose fonts that are easy to read on all devices and sizes.
“Cursive fonts are so elegant, they’ll make my app look classy.
Fonts are another area where personal taste can lead us astray. I once chose a beautiful cursive font for a navigation menu, thinking it added a touch of elegance. It did, but it also added a touch of confusion. Users struggled to read it, especially on smaller screens.
Bias: We believe that stylish fonts enhance user experience just because they appeal to us.
Solution: Opt for clean, legible fonts that are easy to read across all devices and screen sizes. Test with actual users to get feedback on readability. Remember to prioritise function over form.
Lesson Learnt: Legibility trumps aesthetics. Choose fonts that are easy to read on all devices and sizes.
3. Hidden Hazards
3. Hidden Hazards
“I always know where to find the buttons, so everyone else will too.”
In an effort to create a clean, minimalist design, I once hid essential navigation buttons in a hamburger menu. I found it intuitive, but users were lost. Important features were buried, and frustration levels soared.
Bias: We assume our navigation habits are universal.
Solution: Ensure critical functions are visible and easily accessible. Conduct usability tests to identify any navigational challenges users might face. Use common design patterns that users are familiar with to reduce the learning curve.
Lesson Learnt: Visibility is key. Important actions should be easily accessible without unnecessary clicks or searches.
“I always know where to find the buttons, so everyone else will too.”
In an effort to create a clean, minimalist design, I once hid essential navigation buttons in a hamburger menu. I found it intuitive, but users were lost. Important features were buried, and frustration levels soared.
Bias: We assume our navigation habits are universal.
Solution: Ensure critical functions are visible and easily accessible. Conduct usability tests to identify any navigational challenges users might face. Use common design patterns that users are familiar with to reduce the learning curve.
Lesson Learnt: Visibility is key. Important actions should be easily accessible without unnecessary clicks or searches.
4. Feature Frenzy and Content Chaos
4. Feature Frenzy and Content Chaos
“More features and content mean a better app, right?”
There was a time I packed an app with features I thought were cool and useful, resulting in a cluttered interface and overwhelmed users. This issue became even clearer when I designed an EdTech platform. Believing that more content would enhance the learning experience, I ended up creating a maze of uncategorised material. Users struggled to navigate, select courses, and complete learning paths, leading to frustration and abandonment.
Bias: We think adding more features and content increases value.
Solution:
1. For Features: Prioritise based on user needs and feedback. Focus on core functionalities using user journey mapping and minimal viable product (MVP) strategies. Simplify the interface.
2. For Content: Organise into clear categories and subcategories. Implement intuitive navigation and search functionalities. Refine the structure based on user feedback.
Lesson Learnt: More isn’t always better. Prioritise essential features and keep the interface clean and focused. Well-organised content ensures users can navigate easily and stay engaged.
“More features and content mean a better app, right?”
There was a time I packed an app with features I thought were cool and useful, resulting in a cluttered interface and overwhelmed users. This issue became even clearer when I designed an EdTech platform. Believing that more content would enhance the learning experience, I ended up creating a maze of uncategorised material. Users struggled to navigate, select courses, and complete learning paths, leading to frustration and abandonment.
Bias: We think adding more features and content increases value.
Solution:
1. For Features: Prioritise based on user needs and feedback. Focus on core functionalities using user journey mapping and minimal viable product (MVP) strategies. Simplify the interface.
2. For Content: Organise into clear categories and subcategories. Implement intuitive navigation and search functionalities. Refine the structure based on user feedback.
Lesson Learnt: More isn’t always better. Prioritise essential features and keep the interface clean and focused. Well-organised content ensures users can navigate easily and stay engaged.
5. Embracing User Feedback
5. Embracing User Feedback
“I know what’s best for the user; they just don’t see it yet.”
Confidence in our designs is important, but it’s crucial to balance it with openness to feedback. I once launched a design, believing users would eventually see its brilliance. However, their feedback highlighted areas for improvement that I hadn’t considered.
Bias: We often believe we understand user needs better than the users themselves.
Solution: Actively seek and incorporate user feedback throughout the design process. Use tools like surveys, user testing, and feedback forms to gather insights. Be willing to iterate on your designs based on real user experiences. Additionally, conduct User Acceptance Testing (UAT) with friends, family, or office employees who are unfamiliar with the app. Observe their reactions without guiding them to gain genuine user insights.
Lesson Learnt: Listen to your users. Their feedback is invaluable and often highlights issues you might overlook, leading to a better overall design.
“I know what’s best for the user; they just don’t see it yet.”
Confidence in our designs is important, but it’s crucial to balance it with openness to feedback. I once launched a design, believing users would eventually see its brilliance. However, their feedback highlighted areas for improvement that I hadn’t considered.
Bias: We often believe we understand user needs better than the users themselves.
Solution: Actively seek and incorporate user feedback throughout the design process. Use tools like surveys, user testing, and feedback forms to gather insights. Be willing to iterate on your designs based on real user experiences. Additionally, conduct User Acceptance Testing (UAT) with friends, family, or office employees who are unfamiliar with the app. Observe their reactions without guiding them to gain genuine user insights.
Lesson Learnt: Listen to your users. Their feedback is invaluable and often highlights issues you might overlook, leading to a better overall design.
6. Integration Overload: Navigating Third-Party Pitfalls
6. Integration Overload: Navigating Third-Party Pitfalls
“This third-party software will make our app feature-rich and efficient.”
Developing a fintech app often requires integrating third-party software for services like payments, analytics, and security. I once depended heavily on these integrations, which complicated the development process. The result was a long, tedious flow that frustrated users and increased the potential for errors.
Bias: We think adding more integrations will enhance functionality and user experience.
Solution: Simplify by choosing reliable, well-documented third-party services. Map out user flows to identify potential pain points caused by these integrations. Prioritise seamless experiences and minimise the number of steps required for key tasks. Conduct end-to-end testing to ensure the integrations work smoothly without disrupting the user experience.
Lesson Learnt: Third-party integrations can add complexity. Balance the need for additional features with the importance of maintaining a smooth and intuitive user experience.
“This third-party software will make our app feature-rich and efficient.”
Developing a fintech app often requires integrating third-party software for services like payments, analytics, and security. I once depended heavily on these integrations, which complicated the development process. The result was a long, tedious flow that frustrated users and increased the potential for errors.
Bias: We think adding more integrations will enhance functionality and user experience.
Solution: Simplify by choosing reliable, well-documented third-party services. Map out user flows to identify potential pain points caused by these integrations. Prioritise seamless experiences and minimise the number of steps required for key tasks. Conduct end-to-end testing to ensure the integrations work smoothly without disrupting the user experience.
Lesson Learnt: Third-party integrations can add complexity. Balance the need for additional features with the importance of maintaining a smooth and intuitive user experience.
Conclusion: Embrace the User’s Perspective
Conclusion: Embrace the User’s Perspective
Designing for yourself might seem like a shortcut, but it’s deceptive. Our preferences can cloud our judgment, leading to designs that don’t resonate with users. The key is empathy — understanding their needs and being open to feedback.
Designing for yourself might seem like a shortcut, but it’s deceptive. Our preferences can cloud our judgment, leading to designs that don’t resonate with users. The key is empathy — understanding their needs and being open to feedback.
By learning from these mistakes and recognising our biases, we can create designs that are aesthetically pleasing, user-centric, functional, and accessible. So, next time you think, “I love this, so everyone will,” step back and ask, “But what about the user?”.
By learning from these mistakes and recognising our biases, we can create designs that are aesthetically pleasing, user-centric, functional, and accessible. So, next time you think, “I love this, so everyone will,” step back and ask, “But what about the user?”.
Remember, you are not the user. And that’s perfectly okay!
Let me know if you’ve faced similar situations or if you’ve sailed in similar boats as me. As designers, sharing our experiences helps us grow and create better user experiences together.
