Programming Books C Java PHP Python Learn more Browse Programming Books
Buy New
  • List Price: $24.99
  • Save: $10.50 (42%)
FREE Shipping on orders over $35.
In Stock.
Ships from and sold by
Gift-wrap available.
Add to Cart
Want it Monday, April 21? Order within and choose Two-Day Shipping at checkout. Details
Trade in your item
Get a $5.64
Gift Card.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

Lean UX: Applying Lean Principles to Improve User Experience Hardcover

See all 3 formats and editions Hide other formats and editions
Amazon Price New from Used from Collectible from
"Please retry"
Rent from
"Please retry"
$13.39 $14.26

Frequently Bought Together

Lean UX: Applying Lean Principles to Improve User Experience + The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses
Price for both: $29.13

Buy the selected items together

Technology Books from O'Reilly Media
Brush up on topics from programming to electronics for readers of all levels in the O'Reilly Media bookstore. Browse titles in the animal books, "Missing Manuals," "Head First," series, and more.

Product Details

  • Hardcover: 152 pages
  • Publisher: O'Reilly Media; 1 edition (March 11, 2013)
  • Language: English
  • ISBN-10: 1449311652
  • ISBN-13: 978-1449311650
  • Product Dimensions: 9.2 x 6.4 x 0.6 inches
  • Shipping Weight: 12.6 ounces (View shipping rates and policies)
  • Average Customer Review: 4.4 out of 5 stars  See all reviews (77 customer reviews)
  • Amazon Best Sellers Rank: #7,467 in Books (See Top 100 in Books)

Editorial Reviews Review

Jeff Gothelf on How to Do Lean UX in 5 Easy Steps

  1. Solve problems together: Ensure that every member of your team is present during brainstorming for new projects. Give your teams problems to solve, not solutions to implement. The outcome will be a far more efficient and productive team creating higher quality products and experiences.

  2. Sketch: Introduce the team to sketching in order to help them visualize their ideas and come to a consensus.

  3. Prototype: Get to a product experience as quickly as possible. Use prototypes of varying fidelities to get a sense of what your product's experience will be and validate that with customers to ensure you're headed down the right path.

  4. Pair your developers and designers: Have developers and designers pair up to create the user interfaces. Each will learn from the other and build the trust necessary for greater team collaboration and productivity.

  5. Create a style guide: Codify your design elements in pattern libraries and code repositories so creating new pages and workflows in your product is as easy as picking the pieces from the style guide. It also allows the team to quickly piece together experiences for prototypes and empowers your developers to build interfaces without constant review with the UX designer.

About the Author

Jeff Gothelf is a designer & Agile practitioner. He is a leading voice on the topics of Agile UX & Lean UX and a highly sought-after international speaker. He is currently a Managing Director in Neo's New York City office. Previously, Jeff has led teams at TheLadders, Publicis Modem, WebTrends, Fidelity, & AOL.

More About the Authors

Discover books, learn about writers, read author blogs, and more.

Related Media

Customer Reviews

4.4 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See all 77 customer reviews
Pretty short and thin book, that makes it really easy to read and understand the book.
I love how this book emphasizes iteration and calls out user experience designers are not rock stars, they are facilitators of the user-centered design process.
This book is a great, practical guide to applying lean and Agile concepts to the UX design process.
Bob Gower

Most Helpful Customer Reviews

40 of 44 people found the following review helpful By Joe Kleinwaechter on May 6, 2013
Format: Hardcover Verified Purchase
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.
3 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
7 of 7 people found the following review helpful By S. Nay VINE VOICE on August 14, 2013
Format: Hardcover Vine Customer Review of Free Product ( What's this? )
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.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
9 of 11 people found the following review helpful By Nicolas Dao on March 20, 2013
Format: Kindle Edition Verified Purchase
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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
8 of 10 people found the following review helpful By Maraspin Stefano on March 23, 2013
Format: Hardcover
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!
1 Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
3 of 3 people found the following review helpful By Amazon Customer on August 12, 2013
Format: Hardcover Verified Purchase
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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Product Images from Customers

Most Recent Customer Reviews