Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.

  • Apple
  • Android
  • Windows Phone
  • Android

Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.

Prix Kindle : EUR 17,35

Économisez
EUR 9,87 (36%)

TVA incluse

Ces promotions seront appliquées à cet article :

Certaines promotions sont cumulables avec d'autres offres promotionnelles, d'autres non. Pour en savoir plus, veuillez vous référer aux conditions générales de ces promotions.

Envoyer sur votre Kindle ou un autre appareil

Envoyer sur votre Kindle ou un autre appareil

UX for Lean Startups: Faster, Smarter User Experience Research and Design par [Klein, Laura]
Publicité sur l'appli Kindle

UX for Lean Startups: Faster, Smarter User Experience Research and Design Format Kindle

4.0 étoiles sur 5 1 commentaire client

Voir les formats et éditions Masquer les autres formats et éditions
Prix Amazon
Neuf à partir de Occasion à partir de
Format Kindle
"Veuillez réessayer"
EUR 17,35

Longueur : 241 pages Word Wise: Activé Langue : Anglais

Polars Polars


Descriptions du produit

Présentation de l'éditeur

Great user experiences (UX) are essential for products today, but designing one can be a lengthy and expensive process. With this practical, hands-on book, you’ll learn how to do it faster and smarter using Lean UX techniques. UX expert Laura Klein shows you what it takes to gather valuable input from customers, build something they’ll truly love, and reduce the time it takes to get your product to market.

No prior experience in UX or design is necessary to get started. If you’re an entrepreneur or an innovator, this book puts you right to work with proven tips and tools for researching, identifying, and designing an intuitive, easy-to-use product.

  • Determine whether people will buy your product before you build it
  • Listen to your customers throughout the product’s lifecycle
  • Understand why you should design a test before you design a product
  • Get nine tools that are critical to designing your product
  • Discern the difference between necessary features and nice-to-haves
  • Learn how a Minimum Viable Product affects your UX decisions
  • Use A/B testing in conjunction with good UX practices
  • Speed up your product development process without sacrificing quality

Détails sur le produit

  • Format : Format Kindle
  • Taille du fichier : 2519 KB
  • Nombre de pages de l'édition imprimée : 241 pages
  • Pagination - ISBN de l'édition imprimée de référence : 1449334911
  • Utilisation simultanée de l'appareil : Illimité
  • Editeur : O'Reilly Media; Édition : 1 (2 mai 2013)
  • Vendu par : Amazon Media EU S.à r.l.
  • Langue : Anglais
  • ASIN: B00CMFJZ1Q
  • Synthèse vocale : Activée
  • X-Ray :
  • Word Wise: Activé
  • Composition améliorée: Non activé
  • Moyenne des commentaires client : 4.0 étoiles sur 5 1 commentaire client
  • Classement des meilleures ventes d'Amazon: n°62.735 dans la Boutique Kindle (Voir le Top 100 dans la Boutique Kindle)
  •  Voulez-vous faire un commentaire sur des images ou nous signaler un prix inférieur ?

click to open popover

Commentaires en ligne

4.0 étoiles sur 5
5 étoiles
0
4 étoiles
1
3 étoiles
0
2 étoiles
0
1 étoile
0
Voir le commentaire client
Partagez votre opinion avec les autres clients

Meilleurs commentaires des clients

Format: Relié Achat vérifié
Excellent ouvrage, très pratique, le style de l'auteur est assez direct :)

Rien a signaler sur le vendeur, livre en parfait état. Bonne lecture
Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
Signaler un abus

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 4.3 étoiles sur 5 62 commentaires
23 internautes sur 24 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 Applied Lean Theory 26 août 2013
Par Trevor Burnham - Publié sur Amazon.com
Format: Relié Commentaire d‘un membre du Club des Testeurs ( De quoi s'agit-il? )
It's difficult to evaluate this book because, depending on who you are, it could either be completely common-sensical or completely revelatory. There's very little "meat" in terms of case studies. Instead, the entire book assumes that you're a product manager who's interested in practicing the lean startup methodology and either haven't read Eric Ries' The Lean Startup or don't understand its implications for UX methodology.

The methodology advocated by the book boils down to:

1. If a feature would be expensive to implement, establish the need for it first by talking to users.
2. Once a feature is implemented, use metrics to test the hypothesis that it's solved the problem it was intended to solve.

To the book's credit, it provides good advice on how to validate proposed features without asking leading questions like "We're thinking of implementing Feature X. Do you think Feature X would be useful?" It also advocates talking to small groups of users frequently, rather than doing large-scale user testing occasionally or, worse, sending out surveys (a grossly overused tool for startups).

Overall, this is a light and sensible read, but don't expect any dazzling insights.
49 internautes sur 58 ont trouvé ce commentaire utile 
2.0 étoiles sur 5 Skip it... Ignore the "LEAN MAFIA" 5 star reviews 17 août 2013
Par Wildman Keith - Publié sur Amazon.com
Format: Relié Commentaire d‘un membre du Club des Testeurs ( De quoi s'agit-il? )
This book is filled with a lot of obvious advice.
It's as if somebody wrote a book on running a bar and advised you to have a good supply of beer and whiskey.
Or if you were going to start a painting business and they said to have some brushes, rollers, ladders and a sprayer for those times you wanted to spray on paint.
Inside this book you get such gems of wisdom as "do a little research" or "test your applications."
Want some more things you should do... "fix a bug, deal with an error, tweak an existing design, build a whole new product."
Gee, so just throwing something online and not bothering to fix it is not the right way to go??? Really??? Glad I read this book to find that out.
So I decided to check into a few of the people that gave this thing 5 star reviews.
The ones that I read their previous reviews were all fans of other "Lean" books such as Lean Analytics or they knew the author of other books in the series or so on.
It's a "you give my book a 5 star rating and I'll give yours a 5 star rating " club.
Maybe somebody can write a UX for BLOATED and OVERWEIGHT Startups. Sell it on the Weight Watchers web site maybe.
61 internautes sur 75 ont trouvé ce commentaire utile 
2.0 étoiles sur 5 Poorly Written, Get Your Return Label Ready 18 juin 2013
Par mic check one two one two - Publié sur Amazon.com
Format: Relié Achat vérifié
As a software entrepreneur with a background in both visual design and complex web programming, I am currently reading The Lean Startup while developing my next product. I pre-ordered this book because I wanted to give this author the opportunity to speak about user-experience in tandem with the lean startup philosophy.

Most reviews I read on the book were here on Amazon, and all of them were 5 stars except one. Two things gave me pause-I couldn't understand how the book would have 5 stars even though it wasn't out yet, and there was 1 review that said this book was a "skip it". I went ahead and ordered it anyway, thinking that, if it wasn't that good, I'll simply return it.

I returned it.

The only thing this book has in common with The Lean Startup is its name. Unfortunately, it is written very poorly, and the author (or editor, I don't know) comes across as if they were simply trying to fill pages with text, as opposed to actually having something notable to write. For example, there is a methodology in presentations where you do 3 things: tell people what you are about to say, say it, and then tell people what you've said.

This author took that blueprint and applied it to this book literally, by writing sentences that describe what she is about to say in the next sentence, when she could have simply just said what she wanted to say from the beginning!

Kind of like the following sentence (this isn't out of the book but it's very similar to its writing):

--
Okay, so what I'm about to say is really important. Oh, and as a professional you may have already heard this. If you heard this then you'll know that this is important. You really need put your customers first because it's very important.
--

This is like a middle school book report.

Another thing that could stand to improve is the over-use of sarcasm. Maybe it was the author thinking that she's writing in her own "voice" but to me it came off as surly and unfunny. Here's an example of what is written in the book:

--
Have you ever used Amazon? Sure you have, you're human.
--

Those are 10 words that this book could have done without, and there are many, many more.

Also, there are so many platitudes throughout this book it's aggravating, and you can even see them in many of the 5 star reviews on this site. The main one is this:

--
If you are looking for a how-to on graphic design this isn't the book for you.
(or)
If you are looking for a how-to on starting a business this isn't the book for you.
(or)
If you are looking for a how-to on [insert specific expertise or topic] this isn't the book for you.
--

I'd suggest that the author not waste time speaking about who this book is not intended for and just focus on who it "is" for. This is basic technical writing structure! This book isn't for graphic designers...well it isn't for painters or plumbers or trapeze artists or rappers or bull terriers either! You could go down the list of who this book isn't for. Focus on who it "is" for, and the pre-requisites your readers are expected to have.

In addition, the suggestions in this book are highly generic. Using stock pre-built websites, email capture forms, and plug-in play shopping carts can have value but if someone doesn't understand WHY they are doing these things, they will, in fact, be wasting their time, and be just as lost as before they opened this book for guidance.

Anyway, I hope that Eric Reis has some much better quality control, or just kills this whole Lean Series Spinoff idea because books like this really become noise among his signals. If the author of this book is reading this, I think you should get some more people on your team to tell you the truth because this book is unacceptable. An expert making the affiliation with The Lean Startup book should be able to write something much better than this.

So I agree with that 1 review that mysteriously disappeared that suggested skipping this book and just reading The Lean Startup.

Lastly, Eric, it would be much better if the authors of these books came from other camps than your own, or if they did come from your own, they should talk about something completely different. Every time this author made reference to IMVU, it made me feel like this book was a product of nepotism. Again, they can come from your camp but they should at least offer something completely and utterly different than what you've already offered in The Lean Startup.

Skip this book and read The Lean Startup. This book is noise among signal.

Anyway, I hope this review helps to balance the other sterling ones.

Take care!
11 internautes sur 14 ont trouvé ce commentaire utile 
2.0 étoiles sur 5 No concept, full of unicorns 17 juin 2013
Par thomas - Publié sur Amazon.com
Format: Relié
This book reads like a compilation of loose blog posts with no real concept behind it. It switches from high-level user research to an introduction to Twitter's bootstrap framework to landing page optimization without giving the reader any hint to what the umbrella topic really is. The diction with all it's know-it-all verbiage and countless references to unicorns makes me feel that even the author doesn't take the whole book seriously.
I think following a couple of growth-hacking and UX blogs is a way better introduction to this field.
2 internautes sur 2 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 In a word: Wow! 3 septembre 2013
Par atmj - Publié sur Amazon.com
Format: Relié Commentaire d‘un membre du Club des Testeurs ( De quoi s'agit-il? )
As an HF engineer working in an Agile environment, I can tell you this book is the read deal.
Based on the authors commentary, she knows her stuff.
Better yet it is fun to read.

Now to put it in practice.

I have post-it-notes all over this book for ideas. This book is full of them, plus there are references for some great tools and services out there to help you do this.
I've paraphrased a few of the great ideas below:
* Create a button on your site for a product you're thinking about and measure the number of button clicks. Or create a bogus landing page to do the same.
* Making a prototype, knowing that you are going to toss it (as you can't reuse the code) allows you to be less inclined to keep it, if a full redesign is needed
* Do some quick usability tests on your prototype with a few users and tweak to eliminate the big usability issues. Continue to test with the more refined prototype after for the more subtle issues.
* Use Design patterns and Frameworks as this stuff is not rocket science...a duh moment, but why reinvent the wheel?.
* Even with rough framed in Prototypes put in the components(such as text and product info) so users can get what the site is offering versus bogus info.
* Some good prototype references for PC and Mac users.
* Testing Function over Form. Not making the UI pretty allows for quick testing and less angst when it is overhauled.
* The concept of Minimum Viable Product is a great idea when you think how many products get delayed and tanked due to feature creep.
* Site design standards, help the team get a basic graphic design right, in lieu of expensive custom graphics.

Agile is a minefield for UX issues. Since it promises quick to get to market, the urgency it engenders leads to unresearched great ideas going out with little product or process validation. Often the UX team is pressured to do quick UX design for the real code with dressed up graphics. Then, when testing shows there is a problem; any problem from product, to process, to usability, suddenly in this rush-rush process, a fix is needed. Given the urgency often this is only a band aid fix. You end up with unvalidated products, poorly performing processes that are less than usable, that look like a Franken-product. I know it's not that bad, but to the UX team it sure feels that way.

This book is a great way to put the UX and product validation in front, so the ideas that get out are well honed and worthwhile. The steps are basic. However they are not directed to the student in the classroom with a white paper project, but real entrenched UX people living Agile.

The first part of this book is about Validation. Making sure you have the right product
The second part is about design and the mid-design tweaking that all products should have.
The third part is about the product and testing that you did it right.

I laughed when I read a few of the criticisms of this book and other lean books. I swear it was verbatim what I heard a product manager say one day that wanted to get yet another Franken-product out the door and felt this process was a waste of time. Mind you he is rewarded for "Getting her done". He doesn't care whether it is what people want, is easy to use or really for that matter, works. It also puts control of the end product in the hands of the user, where it always was.
Ces commentaires ont-ils été utiles ? Dites-le-nous