Home » Blog » Never publish a design that you haven’t tested on users

Never publish a design that you haven’t tested on users

Morehard to find a UX designer who axes you to test your designs with real users. The problem is that we can’t explain well enough why you should test with users (or how to find the time to do it). We say it as something that goes without saying, an obvious no-brainer that any decent person knows is the right thing to do. Like “be a good person” or “be kind to animals”. If it was that obvious, there would be a lot more user testing in this world.

Let me be very specific about why user

testing is essential. As long as you are in an online business, you are exposing your work to users.

If you are already among the supporters of user testing, this may seem obvious, but it often happens that we overlook something that is not so clear: what impact does user testing have on the communication of interested parties (hereinafter referred to as stakeholders) and how do we ensure that user incorporated testing into projects even when it seems impossible.

The most insidious usability issues are those that haven’t even appeared as potential problems until now; you won’t find all possible usability issues just by looking at the design. And it is user testing that makes it possible to be present when problems arise. You will be able to make sure that everything you have created works as you intended, best practices and common sense are not enough. If you want to innovate, you have to test, otherwise it’s hard to know if people will take what you’re presenting. Or whether they want to. The point is to see if you’ve created something truly intuitive.

Testing in advance saves time

Last fall, I was preparing for a meeting with one of our long-term clients, the charitable and non-governmental non-profit organization (NGO) Plan International in Norway. We had a pretty clear idea of ​​a very different login form than what they were using. But the existing one worked quite satisfactorily, so any reasonable client will be a little skeptical of the innovative idea. Why fix it if usa phone number data it ain’t broke, right? When we were preparing for the meeting, we figured that our idea might be rejected in advance without getting a chance to try it out.

phone number data

 

We discussed what worked well and what could be improved. The conversation that followed the base on your analytics presentation was rational and constructive. Together, we and our partners from the Plan organization discussed various ways to improve the initial design, we did not delve meticulously into details that did not present  difficulties cmo email list in the test. It ended up being one of the best client meetings I’ve ever had. targeted conte.

Scroll to Top