{"id":1939,"date":"2019-03-01T00:07:07","date_gmt":"2019-03-01T03:07:07","guid":{"rendered":"https:\/\/ember.com.br\/?p=1939"},"modified":"2024-06-22T05:16:43","modified_gmt":"2024-06-22T08:16:43","slug":"uma-lista-abrangente-e-honesta-de-cliches-de-ux","status":"publish","type":"post","link":"https:\/\/ember.com.br\/en\/uma-lista-abrangente-e-honesta-de-cliches-de-ux\/","title":{"rendered":"A comprehensive (and honest) list of UX clich\u00e9s."},"content":{"rendered":"

<\/p>\n

<\/div>\n

<\/amp-ad><\/p>\n

A guide for newcomers.<\/em><\/h4>\n
\n
\n
\n
\n
\n

\u201c"You are not your user"\u201d<\/strong>
\nA reminder that you're not designing the product for people like you. Usually used as a way to encourage more user research into a project.<\/p>\n

\u201c"If Henry Ford had asked people what they wanted, they would have told him faster horses."\u201d
\n<\/strong>Used as a counter-argument to the previous statement, when you begin to realize that you won't have the time or money to do enough user research.<\/p>\n

\u201c"We're testing the design, not your skills."\u201d
\n<\/strong>A disclaimer given to users at the start of a user testing session to make them feel better about being stupid.<\/p>\n

\u201c"Designers should have a seat at the table."\u201d
\n<\/strong>When you can't prove your strategic value to the company based on your everyday actions and behaviors, and you have to beg to be invited to important meetings.<\/p>\n

\u201c"The options should be limited to 7 plus or minus 2."\u201d
\n<\/strong>A nicer way of saying that the choices should range from 5 to 9, without sounding too broad. When, in reality, every good designer knows that the options should range from 1 to 2.<\/p>\n

\u201c"People don't want to buy a quarter-inch drill bit; they want a one-centimeter hole."\u201d
\n<\/strong>Wait, do they really want a hole? Or do they want wireless Bluetooth, so holes aren't necessary?<\/p>\n

\u201c"UX should be a mindset, not a step in the process."\u201d<\/strong>
\nWhen you realize the deadline is approaching and you haven't been able to complete your deliverables. Used to retroactively try to convince the PM to extend the project timeline.<\/p>\n

\u201c"Content is king"\u201d
\n<\/strong>A very strong argument to convince everyone to push back the deadline, because you haven't received the content that will go on the page you're designing.<\/p>\n

\u201c"Never underestimate the stupidity of the user."\u201d<\/strong>
\nAn efficient way to outsource your own responsibility is to give users enough context so they know what to do (also known as being a good designer).<\/p>\n

\u201c"I'm wondering if this breaks accessibility standards."\u201d<\/strong>
\nUsed as a last resort when you're running out of arguments to convince other designers that your design isn't working.<\/p>\n

\u201c"A user interface is like a joke; if you have to explain it, it's not so good."\u201d<\/strong>
\nAn easy way to kill that idea of a step-by-step assistant\/explanation that your stakeholders are asking for. Be aware of the backfire: others may agree with your argument and blame you for the fact that the product isn't working so well.<\/p>\n

\u201c"People don't roll"\u201d
\n<\/strong>The most offensive statement you can throw at a designer.<\/span><\/p>\n

\u201c"People are used to scrolling; think about the way you use Instagram."\u201d
\n<\/strong>A polite counter-argument to the previous statement. The Instagram example can be replaced with any other feed-based product that your interlocutor might be addicted to.<\/p>\n

\u201c"The fold doesn't exist"\u201d
\n<\/strong>If you can't convince them, confuse them.<\/p>\n

\u201c"UI vs. UX"\u201d
\n<\/strong>Usually followed by even more clich\u00e9d analogies of ketchup bottles or unpaved walkways.<\/p>\n

\u201c"All pages should be accessible in 3 clicks"\u201d
\n<\/strong>Just. No.<\/p>\n

\u201cShould designers code?\u201d
\n<\/strong>A common wildcard when the audience is running out of questions in a Q&A session at a design event.<\/p>\n

\u201c"If you think good design is expensive, you should look at the cost of bad design.".
\n<\/strong>A passive-aggressive way of explaining to customers that you will not lower your price. Usually ineffective.<\/p>\n

<\/p>\n

<\/div>\n

<\/amp-ad><\/p>\n

\u201c"You can't design an experience; experiences are too subjective to be designed."\u201d
\n<\/strong>An argument used by coworkers who are running out of things to say, but somehow still want to appear intelligent.<\/p>\n

\u201c"Let the users decide"\u201d<\/strong>
\nNone of us will win this endless argument, so we should take this to the user test. But I'll still prove you wrong in the end.<\/p>\n

\u201c"No one enters a website through the homepage anymore."\u201d
\n<\/strong>Popular at the peak of the SEO era (2005-2008), the argument was used to break up endless short meetings where a large group of stakeholders is trying to design their homepage by committee.<\/p>\n

\u201c"The only other industry that names its users as its customers" are drug traffickers.<\/strong>
\nIt's impossible to explain why this exists. Widely used when the term UX emerged in the early 2000s, it's becoming quite popular again in the era of "design for addition".<\/p>\n

\u201c"When escalators break down, they really do turn into stairs."\u201d<\/strong>
\nOriginally used to explain the concept of\u00a0graceful degradation<\/a>\u00a0, The quotation mark began to be adopted by developers to convince the product owner that certain bugs do not need to be fixed.<\/p>\n

\u201c"Mobile device users are distracted"\u201d
\n<\/strong>Just a generalization made by someone who still thinks the primary use case for mobile devices is on the go, while shopping and simultaneously trying to tame a wild giraffe.<\/p>\n

\u201c"You don't know what you don't know."\u201d
\n<\/strong>Honestly, nobody knows.<\/p>\n

\u201c"Leave your ego at the door."\u201d<\/strong>
\nAn inspirational quote to use before entering a user testing session or a collaborative work session with your colleagues. It looks particularly great if written in Helvetica, printed and framed, and hung by the entrance of truly collaborative office spaces.<\/p>\n

\u201c"Double diamond"\u201d
\n<\/strong>Hey, we need a slide in this deck that represents our design process \u2013 can you think of something relatively simple to understand that makes us seem less chaotic than we actually are?<\/p>\n

\u201c"Users don't read"\u201d<\/strong>
\nAn argument that's overused to convince clients and stakeholders to cut copy length in half. If you've made it this far in the article, you're living proof that this claim is false.<\/p>\n<\/div>\n<\/div>\n<\/section>\n

\n
\n
\n<\/div>\n
\n
\n

Is there any clich\u00e9 missing from the list? Please add them in the comments.<\/h4>\n<\/div>\n<\/div>\n<\/section>\n<\/div>\n<\/div>\n