How I overcame the fear of testing my design

Whether it is a simple visual test, usability test or A/B testing, putting your design to test is never fun. I mean who love the feeling of being rejected? Who love to find out that their idea doesn’t work? Not me, obviously.

We all hate to find out that the solution we scratch our heads a couple of days to come up with doesn’t even come close to solving that one usability problem. Yes I have been there. But everyone knows and everyone will tell you that in order to build a successful product you need to test it. And as OFTEN as needed (or as I like to frame it, as often as I saved my Sketch file). And that is just part of being a designer (especially when your team can’t afford to have separate team to do the testings, but even you have extra cash flow, doing testing on your own design is very powerful and helpful as designers). And over the years, and many testings later, I have learnt to better cope with the fear of testing my design.

Being mindful. Remind yourself why you should do the testing.

It is very crucial to understand and remind yourself the WHY. Because again, testing your design , putting your idea for failure is no fun. But having a strong purpose in mind put you in the ready and persevering mindset ( Yes I have read Simon Sinek “Start with Why”, that my workplace’s must-read-starter-kit book.) So why should you do design testings? I will outline some of the most common reasons but depending on the context and the type of tests you are running the WHYs may differ.

1. The most crucial aspect of a product is that it is usable. And that is the whole point of being a UX designer. We design to make the product more user-friendly, to make it practical and that our end-users enjoy using it, and that they can have meaningful interactions with the product. And there is no way to know that without testing. As much as we practice being empathetic with our users, our solutions (design) would just be hypothesis without testing it.
2. Testing enables us to improve our design. Design is not an end, it is a mean to an end — a good product. Testing allows us to be better at iterating our design as we get raws feedbacks from our users.
3. Testing during design phase is simply a must. It is the smartest and most cost-effective method to learn about what people (your users) think of your design and the product. Learning that your product or your design has flaws early will save you and your company a lot of time and effort along the way. Imagine finding out that your CTA doesn’t speak to your users after your app is already launched in App Store. How many users you would have lost, how much money and time you would have wasted due to the small flaw that you would have solved and identified much earlier on by simply do testing during the design phase?
4. Testing your design to see its feasibility. This is like a special trick to me. I would regularly test my prototypes with developers in addition to normal users. This is not so much about usability but to ensure that the awesome design I proposed is actually doable. It is also a smooth way to bring developers on board with your design, getting their inputs and make them champions of your design. That will save you a lot of trouble a long the way.

You are testing to find flaws in your design, to find opportunities for improvement.

I think this is textbook tip on how to get better at taking chances, or how not to be afraid of rejections in general. And I apply this mindset when I set out to do testings on my design. Telling yourself that you are doing this to find flaws in your design, make you a better tester, and a better designer. Because you are no longer obsessed with getting perfect results. Instead you have freed yourself of that self-expectations and your goal now is shifted to find flaws to improve your design. And trust me that feels more empowering.

Don’t take feedback personally.

This is one of those clichés that is easier said than done. But it works. Don’t let that single design work of yours and how people reacts to it defines your self-worth. Your career and value as a designer doesn’t come down to that “I don’t like it” feedback from the users. If you can detach yourself from your design (even though I know it is super hard, especially when you have put so much effort and brain power to it), you will be able to take the feedbacks more positively, as constructive feedbacks.

Also while writing this , I have encountered insightful article on “Managing Your Design Feedback” Highly recommended!

Prepare your test well

Beside from prepping yourself to take on the challenge of putting your baby (design works) out there, and expecting (not-so positive) feedbacks, it is also important to prepare your test well. Make sure that your prototype works well (to a level that can be tested, whether it is paper prototype, or Invision) so that you can test what you want to test. Set up all the necessary information or context that your users need to know before they start the test. This will eliminate all the unnecessary frustration that you may encounter during the test, especially YOUR frustration.

Overall, just like many things in life, to overcome your fear, you have to face it. Practice makes perfect. Do more tests and do them often and you will see your progress. I, myself am still nervous before each test. I still have to go through all the steps above myself. But you know it is natural to be nervous about something you care so much about.

Anyways, if you have other tips or something you want to shed lights on, please feel free to comments below. I decided to start writing because I want to document what I have learnt and also want to learn more from other designers.