Attrecto

  • Home
  • What we do
        • Team as a Service

          Under Attrecto’s Team as a Service offering, clients get quick access to a cohesive team of cross-platform developers, UI/UX designers, QA professionals and support engineers

          LEARN MORE

        • Project Based Development

          Developing user-friendly and intuitive apps and web interfaces that are truly enjoyed by people for their quality, look, feel, colors and functionality – not just merely “used.”

          LEARN MORE

        • Pre-Development Planning

          Get a comprehensive technology and/or UX/CX review on your project through our pre-development workshop. Business value in just 48 hrs with a Deloitte fast 50 company!

          LEARN MORE

        • Chatbot

          Attrecto’s chatbots are state of the art automated agents that can be connected to selected messaging platforms.

          LEARN MORE

  • Who we are
  • Career
  • References
  • Contact
  • Blog
15-useless-product-designs11
Attrecto team

Attrecto team

Biggest UX flops in tech

The Biggest UX Fails in Tech History 

Even great teams fail. 

Even strong brands miss the mark. 

When a UX design goes wrong, everyone loses: the brand, the business, your reputation, your revenues, and, most of all, your users. 

You know, the people keeping the lights on?

In 2018, Icons8 lost 47% of their users thanks to a badly informed UI/UX design.

Walmart lost $1.85 million because of a failure to examine user experience surveys. This data is central to validating the central hypothesis of a UX design. 

And it’s not confined to companies — in 2011, the UK government was forced to scrap a £12 billion project for a patient records management system because of repeated issues. The web development company and teams consistently failed to meet targets on usage, functionality, and benefits. 

The Health Secretary Andrew Lansley had this to say about the failure: 

“The program let down the National Health Service (NHS) and wasted taxpayers’ money by imposing a top-down IT system on the local NHS, which didn’t fit their needs.”

UX fails come in all shapes and sizes because UX is not just about how it looks. UX is just as much about how it works. And it’s about the actual process behind the design. 

As you’ll see from these major fails (and one truly frustrating flaw that we still encounter today), it’s not just that the timing wasn’t right — the entire process matters, from the details of when to launch and how to meet customer expectations, to whether users have actually tested the prototype.team.

Download your free guide for development process in UX driven projects 

Google Wave (2009)

In 2009, Google was hot on the need for a new kind of project management with collaboration at its heart. 

But the design was not so hot.

Let’s say that this was the first wave of its attempt to improve collaboration across teams. The result not only bombed, it totally languished. 

This is what the first iteration looked like. 

Never mind the dated design; the problem was that Google failed to “Keep It Simple Stupid.” The platform was much too busy and felt complex — too complex for an individual to even want to try and navigate. 

This unnecessary complexity popped up again in the fact that Google was focusing on too many projects at once. It decided to launch Google Buzz before Google Wave was fully integrated. 

Coupled with its limited user adoption strategy, the project gained zero traction and was an unmitigated disaster. 

Live and learn, right?

Windows 8 (2012)

Three years later, the Windows 8 debacle proved to mobile development companies the power and importance of continuity and consistency. 

One of the prime principles of UI/UX design is to keep a user’s expectations alive. What a user expects, a user should receive — not least because, through your previous iterations, you’ve likely spent time and money educating your users about how your interface works. 

When Microsoft first released Windows 8, it was a clear shot at Apple who was quickly eating up market share. 

First big mistake: Trying to ape another platform’s functionality. 

From here, things got worse. Because Microsoft abandoned their initial interfaces entirely, users were completely unable to find the most basic functions. 

Navigation was a nightmare and these major changes came at the expense of their users’ expectations. 

Anyone using a Windows PC knows that the desktop and the Start menu are the main points from which to operate tasks and access the file system. 

Instead, Windows 8 users were subjected to an OS that was trying to fulfill the duty of two: It was intended to be both click and touch-friendly

The problem was that, in trying to accomplish both, it did neither well. 

First, Windows 8 removed the Start menu and the default Desktop screen, completely pulling the rug out from under users who, over years of loyal and expected use, now had ingrained expectations. 

After the ensuing chaos and uproar, the customer experience was completely diluted. Sure, Microsoft re-introduced the Start button in version 8.1 — but not before many chose to downgrade to Windows 7.

Now, does this mean that interfaces shouldn’t evolve or that visual identity shouldn’t keep up with modern design standards? No. Certainly not. 

But that’s why changes in UI/UX design need to…

  • Be incremental
  • Keep the main functionality alive, even if the look and feel changes
  • Be based on the results of tangible user testing 

The USB

It’s not scientifically proven or anything but, about 50% of the time, USBs are inserted incorrectly. The user sighs, frustrated, then pops it in again, fingers crossed, hoping and praying to the powers that be that this time, it’ll actually stay in. 

We all know how this story ends. 

The USB is a very common tool and we still rely on USB connected devices every single day. 

To this day, we’re never quite sure whether we’ve inserted it right.

This serious design flaw has a pretty simple fix. To understand it, just look to its predecessor: the plug. Sockets and outlets have their own configurations that are visible to the user, neatly indicating how plugs should be inserted. 

Or you could completely eliminate the USB connector once and for all and opt for a design that doesn’t depend on the orientation of the plug. 

Apparently, designers for Apple and Android phones agree: the latter introduced the lightning connector, while Android phones have developed the C-type USB. 

Source: Dignited

Conclusion

UI/UX’s power is the fact that anything, given enough time and thought, is ultimately changeable. 

Sometimes, all it takes is for UX designers to put themselves in their users’ shoes and look at it from their perspective. It’s why the stages of design — such as prototyping or running sprints — is so crucial to the process of good design. 

Avoiding pitfalls is a collaborative process and it calls for iteration. This iteration shouldn’t be avoided. But there is definitely a way to do prototyping right — prototyping for pros. 

Learn more about how to rapidly prototype for software development and bring a sense of business value to your design team.

Download your free guide for development process in UX driven projects

Share this post