Commencez à lire Lean UX: Applying Lean Principles to Improve User Experience sur votre Kindle dans moins d'une minute. Vous n'avez pas encore de Kindle ? Achetez-le ici Ou commencez à lire dès maintenant avec l'une de nos applications de lecture Kindle gratuites.

Envoyer sur votre Kindle ou un autre appareil


Essai gratuit

Découvrez gratuitement un extrait de ce titre

Envoyer sur votre Kindle ou un autre appareil

Tout le monde peut lire les livres Kindle, même sans un appareil Kindle, grâce à l'appli Kindle GRATUITE pour les smartphones, les tablettes et les ordinateurs.
Lean UX: Applying Lean Principles to Improve User Experience
Agrandissez cette image

Lean UX: Applying Lean Principles to Improve User Experience [Format Kindle]

Jeff Gothelf , Josh Seiden

Prix conseillé : EUR 15,44 De quoi s'agit-il ?
Prix éditeur - format imprimé : EUR 23,36
Prix Kindle : EUR 9,80 TTC & envoi gratuit via réseau sans fil par Amazon Whispernet
Économisez : EUR 13,56 (58%)


Prix Amazon Neuf à partir de Occasion à partir de
Format Kindle EUR 9,80  
Relié EUR 23,39  
Broché --  
-40%, -50%, -60%... Découvrez les Soldes Amazon jusqu'au 5 août 2014 inclus. Profitez-en !

Descriptions du produit

Présentation de l'éditeur

The Lean UX approach to interaction design is tailor-made for today’s web-driven reality. In this insightful book, leading advocate Jeff Gothelf teaches you valuable Lean UX principles, tactics, and techniques from the ground up—how to rapidly experiment with design ideas, validate them with real users, and continually adjust your design based on what you learn.

Inspired by Lean and Agile development theories, Lean UX lets you focus on the actual experience being designed, rather than deliverables. This book shows you how to collaborate closely with other members of the product team, and gather feedback early and often. You’ll learn how to drive the design in short, iterative cycles to assess what works best for the business and the user. Lean UX shows you how to make this change—for the better.

  • Frame a vision of the problem you’re solving and focus your team on the right outcomes
  • Bring the designers’ toolkit to the rest of your product team
  • Share your insights with your team much earlier in the process
  • Create Minimum Viable Products to determine which ideas are valid
  • Incorporate the voice of the customer throughout the project cycle
  • Make your team more productive: combine Lean UX with Agile’s Scrum framework
  • Understand the organizational shifts necessary to integrate Lean UX

Lean UX received the 2013 Jolt Award from Dr. Dobb's Journal as the best book of the year. The publication's panel of judges chose five notable books, published during a 12-month period ending June 30, that every serious programmer should read.

Détails sur le produit

  • Format : Format Kindle
  • Taille du fichier : 3059 KB
  • Nombre de pages de l'édition imprimée : 152 pages
  • Utilisation simultanée de l'appareil : Illimité
  • Editeur : O'Reilly Media; Édition : 1 (22 février 2013)
  • Vendu par : Amazon Media EU S.à r.l.
  • Langue : Anglais
  • ASIN: B0074KA0A4
  • Synthèse vocale : Activée
  • X-Ray :
  • Classement des meilleures ventes d'Amazon: n°49.654 dans la Boutique Kindle (Voir le Top 100 dans la Boutique Kindle)
  •  Souhaitez-vous faire modifier les images ?

En savoir plus sur les auteurs

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Commentaires en ligne 

Il n'y a pas encore de commentaires clients sur
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoiles
Commentaires client les plus utiles sur (beta) 4.4 étoiles sur 5  83 commentaires
47 internautes sur 51 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 Mostly redundant 6 mai 2013
Par Joe Kleinwaechter - Publié sur
Format:Relié|Achat vérifié
If you are a:
UX person AND have read Lean Startup - skip this book. It will be largely redundant.

UX person and haven't read Lean Startup - Read Lean Startup instead. How to apply UX should be a fairly obvious extension of Eric's ideas.

Not a UX person but are interested in learning about Lean UX - by all means, this is a good start to appreciate what is needed.

Unfortunately, I found most of the ideas very much surface thinking. I am sure these guys made a conscious choice to stay at the surface to appeal to a wider audience, but I wanted deeper understanding of the tradeoffs and obstacles companies will face.

Also, I thought their Design Studio concept a pretty average representation of one way to design/innovate. 10 minutes to sketch out six ideas on the spot? There are a lot of ways to generate diverge/converge cycles of ideation and just throwing one out there made it feel as if this was the Lean way.

A least they captured their ideas in a book that could be read in one sitting.
10 internautes sur 10 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 Perhaps a quick read, but there's plenty here to implement 15 août 2013
Par S. Nay - Publié sur
Format:Relié|Commentaire client Vine pour produit gratuit (De quoi s'agit-il?)
I'm a technical writer who has often been involved with UX, and both writing and UX are often left out of the scrum team when product development departments move to Agile, so I was glad to see how these authors addressed the UX component. They present ideas, answer questions, and address concerns that UX designers and other team members will probably have when trying to fit UX into sprints that already seem too short.

Several other reviewers have commented that this is a relatively thin book, and therefore it's a quick read, but A does not necessarily follow B here. Make it a quick read if you like, but I think you'll only get out of it what you put into it. Even if it is a "quick read," it's not a "quick implement." Several of the ideas put forth are major changes from waterfall development and the way that designers have traditionally worked, and it will take some time and a few false starts before a team finds their comfort zone with this. You should find yourself referring back to the book frequently as you switch over.

The authors say that Lean UX is a mindset, and they support that position with a chapter that describes Lean UX principles. Unfortunately, they list 3 foundations and 15 "key principles" that are "critical to the success of Lean UX." They seem to have forgotten one basic design principle, which is that people can't remember more than a few things from a list, perhaps 7 at the most. It's just not possible to focus on 15 principles at the same time and try to make sure that your processes reflect all of them. Some of these principles are high level (such as "Progress = Outcomes, not Output") and others are the result of, or an aspect of applying those, such as "Removing Waste." While all the principles are valuable, that chapter could have been reworked somewhat.

Is it redundant of the "Lean Startup?" I see it as a focused drill-down on how Lean Startup looks in one discipline, so I think it's a valuable addition. Definitely, though, don't try to bring in Lean Startup principles by starting with Lean UX if your company isn't already doing Lean Startup, or moving towards it.
13 internautes sur 15 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 If you've already read Lean Startup by Eric Ries, skip this book 20 mars 2013
Par Nicolas Dao - Publié sur
Format:Format Kindle|Achat vérifié
After having read Lean Startup by Eric Ries, Lean UX falls short of expectations. There are some good use cases and more concrete ways on how to implement some practices that are just theoretically explained in Lean Startup. All in all that book was just ok.
8 internautes sur 10 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Finally! 23 mars 2013
Par Maraspin Stefano - Publié sur
I've always thought agile development loses much of its potential when implementation strictly covers what has already been designed. Where does learning from feedback happen in such a context? Is it still agile? Or barely iterative? In such situations it's also easy to have UX practitioners creating expensive designs (from a technical point of view), because they do not have a grasp of underlying technical complexity. Less costly design decisions could bring to equally satisfying products, but the lack of communication between the two teams brings to the development of the least efficient solution.

It's for these reasons that it always appeared weird to me that UX and Dev Teams were allowed to be different beasts. Agile should be about individuals, interactions, feedback... where does all of this happen, if we keep such teams separate?

I loved this book for being the first (I am aware of) to point out the shortcomings and pitfalls of such common practice, and also to offer practical hints to achieve Lean UX - IE having a single team of professionals with different skills and backgrounds (designers, developers, marketers) working together, as a unique team, to achieve a unique goal: digital product success.

Book can be read in a really short amount of time, and still offers lots of piratical, tactical and strategic hints. Despite we adopt most of the techniques suggested herein already, not only I've been happy to find some confirmation on our practices, but I've also been able to get some precious tips and practical suggestions, that we'll be able to immediately apply on the Field. Book's really what I had been looking for, for a long time and I'm now glad to have it on my bookshelf!
3 internautes sur 3 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 A Great Read for All (Not Just UXers) 12 août 2013
Par Amazon Customer - Publié sur
Format:Relié|Achat vérifié
Even though I am not directly involved in the UX world, most of our projects have at least one or more UX resources involved. Being a Scrum person in terms of execution, I've always struggled with how to best incorporate those UXers into the mix. This book not only lays out a much "leaner" approach than the typical User Centered Design (UCD) process, but gives real world examples on what this looks like in terms of a project setting.

Although I did find the chapter of integrating LeanUX + Scrum lacking (hence the 4 instead of 5 stars), the book itself was a wealth of knowledge for all readers (not just those involved in UX). It opened my eyes to cross functional teams where the UX resource will become more of a facilitator and the developers could easily assist with being research assistants, scribes, and partnering with the UXers.

It has spawned my interest in how I can better assist in reducing documentation and fixating on the end product.
Ces commentaires ont-ils été utiles ?   Dites-le-nous

Discussions entre clients

Le forum concernant ce produit
Discussion Réponses Message le plus récent
Pas de discussions pour l'instant

Posez des questions, partagez votre opinion, gagnez en compréhension
Démarrer une nouvelle discussion
Première publication:
Aller s'identifier

Rechercher parmi les discussions des clients
Rechercher dans toutes les discussions Amazon

Rechercher des articles similaires par rubrique