Book Image

Fixing Bad UX Designs

By : Lisandra Maioli
Book Image

Fixing Bad UX Designs

By: Lisandra Maioli

Overview of this book

Have your web applications been experiencing more hits and less conversions? Are bad designs consuming your time and money? This book is the answer to these problems. With intuitive case studies, you’ll learn to simplify, fix, and enhance some common, real-world application designs. You’ll look at the common issues of simplicity, navigation, appearance, maintenance, and many more. The challenge that most UX designers face is to ensure that the UX is user-friendly. In this book, we address this with individual case studies starting with some common UX applications and then move on to complex applications. Each case study will help you understand the issues faced by a bad UX and teach you to break it down and fix these problems. As we progress, you’ll learn about the information architecture, usability testing, iteration, UX refactoring, and many other related features with the help of various case studies. You’ll also learn some interesting UX design tools with the projects covered in the book. By the end of the book, you’ll be armed with the knowledge to fix bad UX designs and to ensure great customer satisfaction for your applications.
Table of Contents (14 chapters)

Getting stakeholders involved

The cost of investing in a great UX should be clear to your company, and, as we saw before, there are many different studies to show it. By not focusing on UX, your company can decrease sales, increase the number of dissatisfied customers, and disengage employees. As we saw before, there are loads of studies to demonstrate the importance of UX and they should be used to not only convince your company about that, but also to get stakeholders involved.

As explained by Smartsheet.com (https://www.smartsheet.com/) in their article What Is Stakeholder Analysis and Mapping and How Do You Do It Effectively?, you should consider all the interested parties in a project as stakeholders, which means not only everyone who might affect and also influence the project itself, but also everyone who might be influenced by it. 

In the book, Articulating Design Decisions: Communicate with Stakeholders, Keep Your Sanity, and Deliver the Best User Experience, the author Tom Greever explains the stakeholder needs and the importance of gaining their support. The summary of his book is that, as in any project, designers will need the stakeholder recognition of the value of fixing UX issues and the importance of investing in these tasks. By not having such support, the project might risk losing funding or even never going beyond the prototyping stage.

To ensure that stakeholders are involved can be one of the major success factors in integrating UX practices into services or product development processes and organizations, as pointed out in the paper Stakeholder Involvement: A Success Factor for Achieving Better UX Integration. One example of how important it is to get the stakeholders involved was mentioned by Adaptive Path in the study, Leveraging Business Value: How ROI Changes User Experience: After falling behind their competition online, Bank of America, a design team, in collaboration with a product manager, identified that customers were having a hard time completing the online enrollment process. The design team led a collaborative process that included stakeholders from IT, legal, product, and other departments, and was able to increase the yield by 45%.

It is important to know that the top three reasons projects get derailed are poor communication, lack of clarity, and expectation management amongst stakeholders, as pointed out by NNGroup. However, although it is easy to understand the importance of building stakeholder buy-in, it is something hard to do well, because of lack of knowledge, politics, time, poverty, or even lack of interest. The good news is that there are ways to build strong, mutually supportive relationships with your stakeholders that are tried and tested, before and we will talk about these in this book.

But when exactly should we get them involved? A panel of UX experts, organized by UXmatters, has discussed in one of their editions ways of involving stakeholders at different stages of a project in one of their books. One of the panellists, Dana Chisnell—principal consultant at UsabilityWorks and co-author of Handbook of Usability Testing—pointed out that we should bring in stakeholders as soon as you know who they are.

In an article published on the Xwerx blog, the company's senior UX analyst Murray Nolan reminds us that there's often a misunderstanding at the start of a UX project. In the article, Nolan mentions Xwerx's Head of UX, John Mooney, who reminds us that some stakeholders may believe that they already know what their users want and need, besides having no clue of what UX is and how UX can help their business. Nolan also mentions the author of Lean UX, Jeff Gothelf, statement:

"By creating interactions between product managers, developers, QA engineers, designers, and marketers, you put everybody on the same page and on the same level."