![\"Checking](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2019\/06\/image5-720x450.png\")
It often occurs to me how avoiding usability mistakes would take so much less effort. After so many projects, I realized\u00a0I’m making common mistakes way before I actually design a single thing. Usability issues had been forming silently in the background while I focused on the design. They took root in my workflow and now I\u2019m trying to revamp how I work.<\/b><\/p>\n
<\/p>\n
In this article you can learn more about:<\/span><\/p>\n I was reading up on how to avoid usability mistakes while designing an online store a few months ago. After a few days, I kept finding the same old articles over and over again. Obviously, they all collected the same mistakes on purpose: Frequently appearing and easily avoidable mistakes deserve to be mentioned.<\/span><\/p>\n Problematically, they seemed like temporary solutions since the basic properties of my project kept changing on a weekly basis \u2013 the information architecture, the navigation mechanics, everything. I was searching for new tips every week so I decided to look for the nature of usability mistakes instead of a way to avoid them.<\/span><\/p>\n Identifying a usability mistake<\/a> can take a lot. It affects effectivity, efficiency and convenience in a negative, compromising way. A minor issue can make the user feel unpleasant while completing a task. A massive one can make even completing the task impossible. <\/span>In this article, I\u2019ll talk about them as<\/span> incorrect design choices.<\/span><\/i><\/p>\n The problem lies in that usability issues come in many different forms and levels of severity. So why not just categorise and prioritise them? It can’t take that much, right? Not long ago I thought exactly that. Creating order in the chaos would make perfect sense, but when it comes to usability mistakes, this concept fails. <\/span><\/p>\n Making groups or listing the most commonly made ones doesn\u2019t provide an effective solution. Why? UX design is ever changing<\/a> and has multiple variables. Just think about how the way we interact with interfaces has changed in the last two decades. <\/span><\/p>\n We have moved from monitors to small mobile screens while tablets and smart watches with circular screens have broadened the palette. And that looks at just one variable in a way more complex equation. <\/span><\/p>\n That said, no rule or principle lasts forever in the constantly shifting field of design. This means that finding and sorting the most frequent mistakes supplies just a temporary solution. It may work but not for long. To prepare for everything in the distant and blurry future of UX design, look at your workflow for an ultimate answer.<\/span><\/p>\n I used to not browse design trends to keep them from influencing me. Just checking mood boards and color combinations instead, I completely ignored navigation structures and other UX solutions<\/a>. I believed we subconsciously give up our innovative ideas after looking at popular solutions.<\/span><\/p>\n After all these years, the whole concept has flipped around in my mind. Ignoring current user behavior patterns<\/a> and technological changes, you won\u2019t just not expose yourself to the possibility of making critical design mistakes. You\u2019ll also miss out on all other opportunities to make your design really useful.<\/span><\/p>\n OK, so you map your future users\u2019 behavior, but you have to follow through. Conducting exploratory interviews as a method makes for a good start. Asking questions and discovering motivations behind pain points and desires gives you the perfect material to work with: background information. <\/span><\/p>\n This becomes a gold mine when designing an interface. The sheer amount of data it produces might look scary. You may find it hard to organise or to work with but the hidden possibilities always lie inside.<\/span><\/p>\n Find a feasible way of acquiring some juicy background information. If you lack time for your own interviews, find case studies of similar products and pick out the findings. Take a look at existing benchmark studies or successful features of similar products. While not quite the same, they give you something to work with. Doing this research before even thinking about wireframes lets you design <\/span>for<\/span><\/i> the user.<\/span><\/p>\n I was designing a food delivery app and wanted to experiment with the position of the button that takes you to the complete list of restaurants. I tried many variations through several tests but didn\u2019t pay much attention because the user had several other ways to do that. Although the following tests went well (so the subject could complete the tasks) the experience still didn\u2019t satisfy. Finding out why made for a hard nut to crack since they couldn\u2019t identify the problem (not their job anyway).<\/span><\/p>\n A few days later I was watching my girlfriend order food on a totally unrelated site. I noticed how specifically she avoided predefined categories and recommended restaurants. She said they looked like ads. She considered the homepage<\/a> a controlled environment so she proceeded to the restaurant list where she could sort and filter them without feeling controlled. This held the key to my project: control. I had missed this during the tests because of my preconception of how users <\/span>should <\/span><\/i>use the app.<\/span><\/p>\n The easiest way to make a risky design decision? Stay unaware of how your desktop and mobile device users <\/span>want<\/span><\/i> to use your product. Building <\/span>for<\/span><\/i> users and not telling them how they should think always comes easier. Mapping how your target audience expects to interact with your product will help you create an intuitive interface while avoiding critical mistakes simply. It makes for a good trade.<\/span><\/p>\n Designers prove themselves just as human as the users they design for. Hard as it comes, we have to accept this fact. That tiny mistake haunts me to this day. Accept your mistakes, especially you perfectionists. We just can\u2019t perform at one hundred percent all the time. <\/span><\/p>\n Moreover, we can\u2019t avoid smaller usability problems there and no one can design without them coming up. They just make up part of the process. Of course, using various proven practices or (in this case) revamping workflow helps avoid critical issues. But we most likely can\u2019t tackle satisfaction-related inconveniences. Because we perceive the world in unique ways, we expect outcomes and behaviors differently.<\/span><\/p>\n Analyse what went wrong and why. Understanding the reason behind a bad design choice brings us way more than the mistake itself. This takes us back to the \u201cinefficiency\u201d of simply sorting usability mistakes. If you can tell why you\u2019ve made a mistake in the first place, you can avoid making the same one in the future regardless of the platform or the audience. <\/span><\/p>\n Tracking back your mistakes might lead you to a habit (or the opposite, a lack of a habit) in your workflow that causes a lot of trouble later. In my case, designing with presumptions led to a lot of minor usability issues. In turn, they affected the overall user experience in a significantly compromising way. So I\u2019m writing this article. Looking at your mistakes as a byproduct of how you work could help improve methods and get rid of easily-uprooted problems. <\/span><\/p>\n Uprooting mistakes alone, however, doesn\u2019t cut it. Just like designing and testing, reconstructing your workflow requires validation<\/a>, too. We can do this only via various follow-up techniques. You can decide whether to send a simple email to the client, create a full-fledged questionnaire, or even do another round of testing. Determining the most effective way to gain relevant info about your work depends on your project\/client.<\/span><\/p>\n Get some kind of feedback on your work to see the amount of improvement. This way you can measure the effectiveness of your changes and finetune them to achieve better results in case the first round doesn\u2019t satisfy. Besides, it also gives you some good material for your CV, but that just comes as a bonus. \ud83d\ude09<\/span><\/p>\n So here follow in no particular order my tips to improve usability by revamping your design workflow. They rather provide a guide to where they should come in handy. Let\u2019s do a quick recap to see them together:<\/span><\/p>\n I\u2019m still trying to properly integrate these tips in improving your workflow and it takes a lot to accurately measure. But my output already feels more strategic and prepared. I hope it helps you as well.<\/span><\/p>\n Want to learn more about user-centric design and explore the basic principles of our proven lean UX process? Take a look at our <\/span>Product Design book<\/span><\/a> written by our CEO, David Pasztor.<\/span><\/p>\n\n
The inefficiency of sorting usability mistakes<\/b><\/h2>\n
![\"Convenience](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2019\/06\/image3-720x450.png\")
How to improve a workflow with usability mistakes in mind<\/b><\/h2>\n
![\"Usability](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2019\/06\/image2-720x450.png\")
1. Integrate awareness into your workflow<\/b><\/h3>\n
2. Acquire background information<\/b><\/h3>\n
![\"UX](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2019\/06\/image1-720x450.png\")
<\/p>\n3. Deconstruct your preconceptions<\/b><\/h3>\n
![\"product](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2019\/11\/ebook-for-managers-banner.png\")
<\/a><\/p>\n4. Accept your mistakes<\/b><\/h3>\n
![\"Sticky](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2019\/06\/image4-720x450.png\")
<\/p>\n5. Understand your mistakes and build on them<\/b><\/h3>\n
6. Validate your changes<\/b><\/h3>\n
![\"Ux](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2019\/06\/image6-720x450.png\")
<\/p>\nConclusion and recap<\/b><\/h2>\n
\n
Continue learning with UX studio<\/b><\/h2>\n