Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

13 Signs Your UX Needs an Exorcism


Published on

Making simple, elegant solutions is HARD and often invisible. These are some of the most common things I hear come out of people’s mouths when heading for a bad UX decision.

Published in: Technology
  • Be the first to comment

13 Signs Your UX Needs an Exorcism

  1. 13 SignsYour UX Needs an ExorcismCrystal Beasley . @skinny
  2. This is a one-oh-one.And before any veteran designers go ripping me a new one, these are rules of thumbintended for a 101 audience. They do not apply in every circumstance. However, you mustknow the rules to know when to break them, and that requires varsity-level skills.
  3. things people sayMaking simple, elegant solutions is HARD and often invisible. These are some of the mostcommon things I hear come out of people’s mouths when heading for a bad UX decision.
  4. 1 “ Ive got this really great idea for a site.”Ive seen entire sites built to do something no one wants, and its more common than youwould believe. How, you may ask, does this happen? You start with a solution and then gofind a problem it solves as justification. We get ourselves into this situation because of a lackof insight into where peoples needs and frustrations lie.
  5. 2 “Ive got this really great idea for a feature.”Developing new features is most often at odds with making an interface thats easy to use.Features have a technical cost, but the UX cost is much higher. Make the happy pathsupremely happy by rigorously pruning off features from the UI that are wanted by only 2% ofusers. For features 20% of users will need, you should still maybe build them but its ok tomake that flow a bit more lengthy. Youre optimizing for the sweet spot of tasks 80% of userswill need. Im sure *you* have never been guilty of having a pet feature. Im sure everyone willwant to use it. Avoid long fights on where in the 80/20/2 scheme the feature falls byemploying a/b metrics and user testing. Otherwise, the loudest or HIPO (highest paidopinion) in the room will likely prevail.
  6. UI complexity feature setEach feature you build adds UI complexity. There are successful sites all along the orangeline. The degree to which you can add features without adding UI complexity, rising abovethe orange line, is the degree to which your site feels like magic.
  7. Low # of features, low UI complexity. barelyhas buttons. There’s only one page. There are no user accounts. You can use it by justrefreshing the page. Yet, people love it. It was so successful it spawned its own book!
  8. High # of features, high UI complexity. NYTimes employs the best in the business to tweakevery dial of this UI. The algorithms that determine where articles are placed have to be nuts.Be aware that every step feature you add means exponentially more UI complexity. It cancertainly be done, but know what you’re committing to.
  9. 3 “Lets put a sentence under the button to explain.”You cant document your way out of a confusing UI. Remove half the words. Then removeanother half. Kinks in the UI can usually be resolved by the next bullet point...
  10. 4 “ What were doing here is so novel.”Reuse existing UI paradigms. People dont want to read unless required, so use patterns tomake reading mostly unnecessary. The user must recognize which mental model is in use orelse be able to quickly and correctly learn the model. Breaking a paradigm is serious, varsity-level stuff. Find someone whos trained if you are convinced you need a novel pattern.
  11. Yahoo’s design pattern library is a great place to get the common UI building blocks. Even ifyou are making something from outer space, you’ll still need to make use of most of these.
  12. 5 “ I think the button should be on the right.”Its not about opinion. Heres how you make design decisions. Step 1. Adhere to patterns inyour designs. Ahem, we just covered that. Step 2. Test. Users are weirder and moreinteresting than you can imagine. Step 3. Go back to step 1 and refine with what yourlearned. Even pros (especially pros) test their designs. You cant afford not to validate yourassumptions. You MUST test with real people to escape your biases. Additionally, when youmake a decision independent of data, you have a process that is vulnerable to organizationalpolitics and maneuverings.
  13. 6 “ I dont want the user to do the thing they want to do.”If your users want to do something you dont want, its time to closely examine why. Fix theroot cause. Chances are this is damn hard or you wouldve already done it. Still, theres nobetter solution. Fighting your users is never a winning strategy.
  14. What do you think the most clicked element on this page is?
  15. Trick question, because it’s not even above the fold. The tiny light grey link down in thefooter “contacting us” received thousands of clicks and generated hundreds of email everyday.
  16. To their credit, they’re moving sites over to a contact us box in the right sidebar.
  17. 7 “ Maybe we need a FAQ.”Only put the information where/when the users will need to use it. In a flow, there should bea clear path for the user to take (either a CTA or a clear choice). The most importantinformation on each page should be OBVIOUS. Think of every page a user would likely landon from search as a mini-homepage. Your site should have a purpose, and it should be clearto the user. Users should have enough context to know where they are within the structure ofthe site and what other related info is available.
  18. FAQs are an admission of defeat.
  19. 8 “ Cant we just pop up a confirm dialog?”Confirm dialogs are of the devil. Prevent errors. Support undo. Again, dont document thatsomething is dangerous if you can fix the danger. Instead of putting a sign up saying theresa giant hole in the road, repair the hole or let the driver hit the magic button to fix themuffler that fell off.
  20. What kills me is that they know the correct answer. It says so right in the dialog. “Deleting asurvey task cannot be UNDONE.” Again, supporting undo would be the correct choice here.
  21. 9 “Lets split this up into different steps so it seems smaller.”Dont lie to users. Set expectations appropriately. Wizards are usually not the answer. Makethe flow smaller. Every field you ask from users reduces conversions.
  22. This new version puts the content right up front, allowing the users to immediatelyunderstand the purpose of the site, grab what they want and go.
  23. 10 “ Make it red so it will really stand out.”There comes a time in every designers life where they have to learn about the birds andbees. Red is a very wonderful color in the palette. Its saved for that special person, i.e. errortext, critical system warnings. If you must use red because youre a fire department or OhioState University, use yellow for errors.
  24. Chrome’s visual design is pretty and I suspect it hits the target customer’s aesthetic, but theUX is poor. They’re using red for everything because it’s the brand color. If you MUST do so,reserve yellow for errors.
  25. How many errors are there on this page?
  26. How many errors didyou see?
  27. Double highlighting will call attention to the error fields so users can quickly complete theirtask.
  28. You’re not saying nearlyenough about this stuff.
  29. 11 navigationYour site should be organized in the way your users think about it. If your nav mirrors yourorg chart, you didnt make the decision with data. I guarantee users dont think of yourproduct the way you do. To escape your own bias, youll need metrics and analytics tounderstand what the most common tasks your users are trying to solve. Then, card sorts andtree testing can distill that into the correct, mutually-exclusive taxonomy with jargon-freelabels.
  30. 12copy
  31. Add-ons, extensions, plugins... Who can tell the difference? I’m sure there’s animplementation level reason for these names, but users can’t be expected to parse that. Toknow what your users call things, you have to ask them. Those card sorts sound stupid easy,right? So go do it.
  32. from Jakob NielsenJakob Nielsen has great guidelines for writing for the web. In short, keep it short. Users scanin a F shape, so keep keywords toward the beginning of the line and especially in theheaders. This is no place for cutesy language.
  33. 13login
  34. Give users a way to gradually engage with your site. Do you really need login or can you dothe same thing with a cookie? Delay it until absolutely necessary even if so. They wont makean account until they understand the value.
  35. A registered user is like gold, so treat them as such. Nothing will destroy your engagement ofreturning users faster than forgetting who they are, so persist user sessions FOREVER. Goassign yourself that bug to make links from your emails automatically log them in.
  36. That’s it!@skinny
  37. ResourcesSteve Krug Don’t Make Me ThinkLou Rosenfeld Information Architecture for the WWWLuke Wroblewski Web Form DesignJakob Nielsen useit.comthese slides and more at