Final considerations (Garrett) — DAY 19

Yep, as Garrett introduced us to a 5 plans structure in his book: The elements of user experience — user-centered design for the web and beyond, and as we have already covered all of them: Strategy, Scope, Structure, Skeleton and Surface, it’s time for the final considerations. In this last chapter, Garrett tried to give us a summary about all his concepts, and I will do my best to list some of the main points (in my opinion):

The difference between success and failure in UX comes from:

  • Understand what is the problem that you are trying to solve, and which plan the problem belongs to: strategy, scope, structure, skeleton, surface;
  • Understand what are the consequences from your solution, being aware for possible ripple effects.

Most of the time, the choices designers make about user experience falls into one of the following scenarios:

  • Design by default: the structure of your user experience follows the current practices of the organization, not to real user needs;
  • Design by mimicry: It’s about conventions. The UX structure don’t really care for users’ needs, but to current conventions from other products, softwares and so on;
  • Design by fiat: when personal preferences from the stakeholders lead the process. This is a dangerous position.
  • User experience design is a large collection of very small problems to be solved.
  • It’s important to follow the process to create consistent UX results.
  • User Experience is about trade-offs.
  • Sometimes a solution impact in other parts of the website, and you have to choose the one where you better serve the users.
  • You should ask ‘Why did I do it this way?’.
  • Don’t gloss over the UX fundamentals to save money.
  • Do informal usability test if you can’t do the formal one. But do it.
  • Never wait ‘the end’ of the project comes up to test usability, this should be used in every step.
  • Research on your own database, it’s cheaper and it’s definitely about your user.
  • Test and apply UX concepts since the very first begin of the project.
  • Testing is very important, but it will never substitute a thoughtful, informed, user experience design process.
  • While testing you get to know what you want to discover, and go towards users needs. As long as you know what you are looking for gets easier to find solutions.
  • Don’t base all your UX decisions only in tests, as they are only able to tell you what your user already know.
  • Don’t leave UX aspects to chance!
  • Don’t leave your own development process to chance!
  • UX is a lot about project management.
  • Never eliminate levels!
  • By following the full UX process in your project, the results are conscious and explicit decisions, where you ensure that the product works to fulfill both your strategic goals and users’ needs.
  • The final objective is: Understand the user needs better than they understand it themselves.

So, for me, was a pleasure to review and share a little bit about this book, which I believe is one of the bibles for UX designers. If you have any suggestions, criticism, ideas, other points of view, please share it with us here, on facebook, or on instagram.

#100daysaboutusers

Roberto Pesce — aboutusers.com

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.