Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Image Unavailable
Color:
-
-
-
- To view this video download Flash Player
-
-
VIDEO -
-
UX for Lean Startups: Faster, Smarter User Experience Research and Design 1st Edition
| Price | New from | Used from |
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
- ISBN-109781449334918
- ISBN-13978-1449334918
- Edition1st
- PublisherO'Reilly Media
- Publication dateJune 25, 2013
- LanguageEnglish
- Dimensions6 x 0.73 x 9 inches
- Print length233 pages
Customers who viewed this item also viewed
From the Publisher
|
|
|
|
|
|
|
|---|---|---|---|---|---|---|
| Running Lean | Lean Analytics | Lean Enterprise | Lean UX | Lean Customer Development | Lean Branding | |
| Find further titles in this series | Iterate from Plan A to a Plan That Works | Use Data to Build a Better Startup Faster | How High Performance Organizations Innovate at Scale | Designing Great Products with Agile Teams | Building Products Your Customers Will Buy | Creating Dynamic Brands to Generate Conversion |
Editorial Reviews
Amazon.com Review
Q&A with Laura Klein, author of "UX for Lean Startups"
Q. Why is your book timely-- what makes it important right now?
A. We’re seeing a massive increase in the demand for well-designed, easy-to-use products. At the same time, we’re seeing an incredible shortage of designers who can work at the sort of fast-paced, data-driven, innovative startups that are popping up. UX for Lean Startups helps teach founders and entrepreneurs the basics of research, design, and UX so that they can build products people love and companies that can grow.
Q. What information do you hope that readers of your book will walk away with?
A. I hope that everybody who reads the book will be able to learn from their customers and turn that information into products that people will actually buy. I want startups to stop building things people don’t want and can’t use. This book can help them do that.
Q. What's the most exciting and/or important thing happening in your space?
A. I think the addition of data is the most important change to design that I’ve seen. By incorporating real data into the design process, we can understand exactly what effect our changes have on our users’ behavior. It used to be that design was about opinion and compromise. Now it’s about proving that the work we do has a positive impact on the company’s bottom line.
Laura's top 5 tips for readers:
1. Talking to users is not as good as listening to users, which is not as good as observing users. The best way to truly understand your user experience is to watch people trying to use your product. Do this as often as possible. It can be painful, but it’s always useful.
2. Know that something you believe may be wrong. The most important thing you can do is to identify which of your beliefs are assumptions and validate them. Before you spend a lot of time designing and building a feature, spend a little time validating whether or not the feature will help your business.
3. Quantitative research tells you what. Qualitative research tells you why. Things like A/B testing and funnel analysis (quant) are useful for explaining things like which design caused people to buy more products and where people fell out of the purchase funnel. Things like observational research and usability testing (qual) can tell you why users responded better to a particular design and why users are getting dropping out of the purchase funnel. Use them together for the best results.
4. An MVP is not half of a big product. It’s a whole small product. Don’t build something crappy and unusable and then claim it’s a minimum viable product. Build a good, but limited, version of your product that solves a serious problem for people.
5. Lean Startup is about learning, not landing pages. Whenever you’re wondering whether you should use a specific Lean Startup tactic, like a landing page or an MVP or an A/B test, ask yourself what you hope to learn from it and whether there is a cheaper, faster, more effective way to get that learning. Just measuring things doesn’t make you lean. The only way to truly be a Lean Startup is to Build, Measure, and Learn (and then Iterate).
About the Author
Product details
- ASIN : 1449334911
- Publisher : O'Reilly Media; 1st edition (June 25, 2013)
- Language : English
- Hardcover : 233 pages
- ISBN-10 : 9781449334918
- ISBN-13 : 978-1449334918
- Item Weight : 1 pounds
- Dimensions : 6 x 0.73 x 9 inches
- Best Sellers Rank: #1,494,885 in Books (See Top 100 in Books)
- #189 in Lean Management
- #411 in User Experience & Website Usability
- #620 in Industrial & Product Design
- Customer Reviews:
Important information
To report an issue with this product, click here.
About the author

Discover more of the author’s books, see similar authors, read author blogs and more
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonReviews with images
Submit a report
- Harassment, profanity
- Spam, advertisement, promotions
- Given in exchange for cash, discounts
Sorry, there was an error
Please try again later.-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
"If you get nothing else from this book, please remember these three key points: (1) User research. Listen to your users. All the time. I mean it. (2) Validation. When you make assumptions or create hypotheses, test them before spending lots of time building products around them. (3) Design. Iterate. Iterate. Iterate."
"Climbing to the top of the hill you're on gets you higher, but it doesn't always maximize your altitude. Sometimes you need to find a taller hill."
"It's probably not worth your time to fret and sweat over every single pixel on every single new page, mostly because you should always plan on iterating. When you're a startup, any new feature may be killed or transformed in a week's time."
"...visual design can screw up interaction testing. If your tester has an immediate positive or negative reaction to the visuals, you're going to get different information than you would if she could effectively ignore the visuals. Grayscale wireframes or Balsamiq-style sketches make it much easier to ignore the look and concentrate on the interactions."
"Visual design is how something looks. Interaction design is how something works."
"A useful wireframe, in my opinion, needs to include all the copy, buttons, calls-to-action, and navigation elements of a real product. It doesn't have any visual design yet. That comes later. But it's definitely where you're taking all the elements that you sketched out and making sure that they not only fit together on one screen but that they also hold up throughout an entire feature or product."
"Lean UX always has a measurable goal, and you should always figure out how to measure that goal before you start designing. If you don't, how will you know that your design worked?"
"Trust me, people will forgive ugly faster than they'll forgive unusable. Whatever you decide to cut, don't cut getting customer feedback during your development process. If you ship something that customers can't use, you can go out of business almost as fast as if you hadn't shipped anything at all."
"Patterns start to emerge in usability research after the first few tests. After five, you're really just hearing all the same stuff over and over again."
"The single greatest mistake you can make at this point is to start off by telling the test subject what you're working on and how great it will be for him. Nothing will bias a session faster than you trying to sell him on your ideas. You're not there to talk. You are there to listen."
"Start off by asking them to show you how they currently perform some tasks that relate to the problem you're trying to solve."
"...this may sound cryptic, but sometimes the best types of problems to solve are the ones that the users don't really know are problems until you fix them."
I recommend this book for anyone working on a startup or even just in general working in web development. Even larger, established web companies need to start thinking more like lean startups in today's digital environment.
The introduction of the book talked about what Lean UX is and isn’t. It was compared to Agile Design and User-Centered Design, which meant nothing to me, to be honest. The actual definition was irrelevant to why I was reading this book - I care more about the practice and benefits of Lean UX. But the rest of the book got into the meat of that.
Lean UX can be summarized into 3 principles:
1. Do research. Ask questions, make hypotheses.
2. Validate. Answer questions, test hypotheses.
3. Iterate. Take answers and data, and then make adjustments.
Research is extremely important not just because it tells you whether your product or service is viable, but because it saves you time and money. The key to Lean UX is doing research and avoiding problems before they come up. Don't waste your resources.
"Lean UX isn’t about adding features to a product, it’s about figuring out which metrics drive a business.”
The author talked about the 2 different kinds of research you can do: quantitative and qualitative. "Quantitative research tells you what your problem is. Qualitative research tells you why you have that problem."
Quantitative research is about getting statistically significant data about a potential feature or workflow - like A/B testing. Qualitative research is about listening to what the user has to say. You have to pay attention to what they do and how they use your product. Looking over someone's shoulder while they use your product is a great way to do user research.
The best way to figure out if you product is any good is to hand your product over to the people and observe how they use it. The worst way is to ask people if they would use it. The main reasons for this are because we as consumers don't really know what we want and our dollars speak louder than our words.
Another thing I liked from this book was this set of questions we should ask when determining if a landing page has good UX:
1. What does the user think this product does?
2. Who does the user think the product is for?
3. Can the user figure out how to get the product?
It seems simple, but those questions are golden. I think they apply not just to UX designers and marketers, but also to authors, video producers, and a whole slew of other people. Think about The Start-up of You: Adapt to the Future, Invest in Yourself, and Transform Your Career by Reid Hoffman. Make sure you can answer these questions about yourself as a professional.
Another important aspect of UX design is making sure that you're starting with problems, not solutions. Bad starting point = "Let's add commenting functionality to the product page!" Good starting point = "Users aren't able to communicate with each other, which affects their engagement with the product."
All in all, good book. This is extremely accessible to lay people and most valuable to anyone working in the startup realm (especially marketers and business dev folks). If you're already a UX designer or you've read a fair amount of stuff on UX, you probably won't find this novel at all.
Top reviews from other countries
The book starts by offering advice on how to conduct qualitative research on the idea to check if customers really need that and then moving on to landing pages to confirm the hypothesis and then to A/B testing to get statistically significant data on whether proposed changes increases certain metrics or not.
Between the various ideas, the books talks about how to speed up things aka faster user research, faster design etc. emphasizing the "lean" concept of doing just enough and thus avoiding wastage.
Other key takeaways for me were designing the test first, when to use qualitative vs quantitative tests, tips on creating various types of MVP including landing page, Wizard of Oz, Fake door test etc.
The books content might be good for early beginners. But again the tone is quite unwelcoming.
And each chapter could be summarized in a couple of paragraphs.
Don’t know why this book is on The lean series.
The tone is such so different from the others.
- Walks you through the practice of Lean UX in easy to follow steps
- Lists useful tools and web sites to support your UX work
- Full of practical advice, sometimes in pretty harsh language but always clearly based on a lot of real world experience
I guess it's less useful for Lean Startup beginners, but very good when you want more hands-on advice.








