Design

Lean UX: Creating Great Products with Agile Teams

Lean UX: Creating Great Products with Agile Teams

  • Downloads：1333
  • Type：Epub+TxT+PDF+Mobi
  • Create Date：2021-10-11 09:19:15
  • Update Date：2025-09-07
  • Status：finish
  • Author：Jeff Gothelf
  • ISBN：1098116305
  • Environment：PC/Android/iPhone/iPad/Kindle
  • Download

Summary

Lean UX is synonymous with modern product design and development。 Designers， product managers， developers， and Scrum Masters around the world are combining human-centric design， Agile ways of working， and a strong business sense， making Lean UX the leading approach for digital product teams today。

Inspired by Lean and Agile methods， this book helps you focus on the actual product experience rather than deliverables。 Lean UX shows teams how to collaborate， gather feedback early and often， and focus on learning and user feedback。 You'll be able to drive the design in short， iterative cycles to assess what works best for businesses and users。 Lean UX guides you through this change--for the better。


Facilitate the Lean UX process with your team
Ensure every project starts with clear customer-centric success criteria
Understand the role of the designer on a Scrum team
Write and contribute design and experiment stories to the backlog
Ensure design work takes place in every sprint
Build product discovery into the team's "velocity"
Make sure the team is designing and building products that customers love

Download

Reviews

Caroline ，

Definitely a lot of valuable advice and concepts for doing more effective UX work and create better products。 I do wonder about the practicality of having the whole team spend time talking together about everything - this means more meetings and less time to focus on the nitty gritty of my heads-down work， the design details or working through coding challenges。 These alone have a lot to them as well。 It does mean less time on handoffs though， but work must be aligned perfectly， where everyone i Definitely a lot of valuable advice and concepts for doing more effective UX work and create better products。 I do wonder about the practicality of having the whole team spend time talking together about everything - this means more meetings and less time to focus on the nitty gritty of my heads-down work， the design details or working through coding challenges。 These alone have a lot to them as well。 It does mean less time on handoffs though， but work must be aligned perfectly， where everyone is always available to work concurrently。 。。。more

Alok Pepakayala ，

A very concise and effective book on the process， techniques and team setup。 A must read for any ux designer though you will be familiar with many of these principles in one form or the other， the compound presentation of these topics under one book is a good refresher。

Vanessa Castilho ，

The web-driven economies of today， dominated by software-based products， have led to ever-decreasing product life cycles， as the continuous nature of software has made rapid product updates essential。 To keep ahead of the curve， it’s key to experiment constantly while seeking user feedback， tasks that Lean UX is perfectly suited to tackle through its collaborative dialogic approach。

Dale Moore ，

This was a great intro to UX in a lean/agile methodology。 I’ll have to go back and re-read it because I didn’t get the full value out of it that I need due to limited time， but it’s a short read and has some good ideas。 Definitely not how things are done in my organization， or most similar ones， unfortunately （still a waterfall approach）， maybe that can change （or I just need to work elsewhere 😂）。

Julian Moreno ，

Another of the fundamental and mandatory aspects for a solid foundation in relation to user-centered design in agile environments。 It will change the chip in several ways！Warning: don't read it eagerly！ It is not for an ephemeral and quick read！ It is a methodological book that deserves to be understood， analyzed， questioned， appropriate， and applied。 This is one of the great reasons why I have reread it many times and continue to review its latest versions since the paradigm shift proposed by t Another of the fundamental and mandatory aspects for a solid foundation in relation to user-centered design in agile environments。 It will change the chip in several ways！Warning: don't read it eagerly！ It is not for an ephemeral and quick read！ It is a methodological book that deserves to be understood， analyzed， questioned， appropriate， and applied。 This is one of the great reasons why I have reread it many times and continue to review its latest versions since the paradigm shift proposed by the authors is relatively complex to apply depending on the culture and type of organization where you work。 。。。more

Nicoara ，

good book on overall lean practice， but since it is published in 2015，many books address different parts with newer more complete techniques。

Jonas Stehli ，

Today， I finally finished reading “Lean UX” by Jeff Gotthelf and Josh Seiden。 Even though I am not planning to become a UX expert， this was an interesting read。 Even if you are not a UX designer， I believe that having the user at the center of your work is crucial for all of us。The two chapters in “Part I: Introduction and Principles” are a fantastic introduction to lean and agile principles。 I strongly recommend those twenty pages to anyone who is interested in the subject。 “Chapter 8: Making O Today， I finally finished reading “Lean UX” by Jeff Gotthelf and Josh Seiden。 Even though I am not planning to become a UX expert， this was an interesting read。 Even if you are not a UX designer， I believe that having the user at the center of your work is crucial for all of us。The two chapters in “Part I: Introduction and Principles” are a fantastic introduction to lean and agile principles。 I strongly recommend those twenty pages to anyone who is interested in the subject。 “Chapter 8: Making Organizational Shifts” should be an interesting read for people who actually try to implement those principles in a real-word organization。The book is very hands-on and written in an easy-to-read and often entertaining way。 Some of my favorite quotes are:Get out of the deliverables business。It is time to break down the silos， unite the clans， and get to work。Building a pixel-perfect specification might be a route to rake in six-figure consulting fees， but it’s not a way to make a meaningful difference to a real product that is crucial to real users。We know that our first attempt will inevitably require revision。 You know that you’re not going to get it right the first time。Collaboration creates better work。 Revision and iteration make for better products。Traditional “get it all figured out first” approaches are simply not workable。The assumption in Lean UX is that the initial product designs will be wrong。Lean UX values making over analysis。Our goal is not to create a deliverable。 It’s to change something in the world - to create an outcome。Every project starts with assumptions。In general， it’s better to ask questions than to share opinions。Make sure that you know what you’re trying to learn。Nothing is more humbling （and motivating） than seeing a user struggle with the software you just built。Your entire product development engine is going to need to change if you want to create a truly agile organization。Two words: proactive communication。 If you want your stakeholders - both those managing you and those dependent on you - to stay out of your way， make sure that they are aware of your plans。Teams must ask， “why are we working on this project？” And， “how will we know we’ve done a good job？”Silos are the death of collaborative teams。In fact， just have team meetings。Get it done。 Get it out there。 Discuss。 Move on。Fall in love with the problem， not the solution。To make Lean UX work in an agency， everyone involved in an engagement must focus on maximizing two factors: increasing collaboration between client and agency， and working to change the focus from outputs to outcomes。Lead with conversation， and trail with documentation。Try asking for forgiveness rather than permission。 Try out some ideas and prove their value with quantifiable success。 （。。。） If your manager still doesn’t see the value in working this way and you believe your organization is progressing down a path of continued “blind design”， perhaps it’s time to consider alternative employment。You must constantly reach out to members of your organization who are not currently involved in your work to make them aware of what’s coming down the pike。 。。。more

Lindsey ，

This was an interesting and practical read explaining the business applications of Lean UX。 Jeff Gothelf did an excellent job of explaining each point and providing examples of the implementations in realistic job scenarios。 His experience in the field shows。 This is a great book for companies， managers， and team leads who are interested in applying more UX methodologies in software development。

Teresa ，

Very similar to "The Lean start up"， and "Sprint"。 Very similar to "The Lean start up"， and "Sprint"。 。。。more

Rachel Willis ，

Useful overview。

Cuong Nguyen Michael ，

A quick and useful read for the Professional Scrum with User Experience exam

Bjorn Martensson ，

The book has some good advice。 I missed a stronger "story"。 The book has some good advice。 I missed a stronger "story"。 。。。more

Aral Roca Gomez ，

I thought that as a software engineer this book would provide me with knowledge of UX design to complement my work， but I see that it only explains the processes that designers follow to plan and test their designs and it has given me very little。

Ragad ，

الكتاب قيم ،، الترجمة مرهقة جدًا انصح بقراءته باللغة الانجليزية

Gökhan Kantar ，

There is a lot of info and sugessted practices in this book， I tried on my product as a product manager and loved the first results！

Olivia Law ，

Read this for work （i work in tech now lol） and LOVE the concepts of this， was super useful。 However， definitely dragged on a bit， like after a while， you just get it。 Didn't feel like I got much out of the last 1/3 of the book。 Read this for work （i work in tech now lol） and LOVE the concepts of this， was super useful。 However， definitely dragged on a bit， like after a while， you just get it。 Didn't feel like I got much out of the last 1/3 of the book。 。。。more

Emilia ，

There was a chapter that explained every concept you need to know to understand Lean Ux。 It was the most useful information， and yet the author decided to put this chapter towards the end of the book。 I was confused most of the time reading Lean UX， because I didn’t have the vocabulary to understand what the author was trying to explain to me。 It would have been helpful if the chapter I talked about was the first one in the book。

Momo ，

Interesting book on how to apply the lean method to UX and build a lean way of working among teams。

Marius Colacioiu ，

Amazing book: really takes Product design to a new level。 It is the part I was missing to take cross-functional teams to a new level while developing successful web products in a timely manner。

Vazdooh ，

Reads like a series of blog posts。If it's you first time reading about concepts such as lean and agile it's a decent enough book。 For people who are familiar， it brings nothing new。 Just the basics rebranded as "lean ux"。 Reads like a series of blog posts。If it's you first time reading about concepts such as lean and agile it's a decent enough book。 For people who are familiar， it brings nothing new。 Just the basics rebranded as "lean ux"。 。。。more

L ，

First half is still super important， super true， super re-readable and worth quoting to your team and especially bosses again and again。Second half seems a bit like filler to make this into a book of decent size。

Oliver ，

The interesting aspect of this book is the integration of User Experience Design in an agile workflow。 I like the idea of collaborative design and collaborative evaluation。 I'm not sure if research and analysis as it is described in this process isn't perhaps a bit too lean， especially when quite a complex task is to be solved。 The interesting aspect of this book is the integration of User Experience Design in an agile workflow。 I like the idea of collaborative design and collaborative evaluation。 I'm not sure if research and analysis as it is described in this process isn't perhaps a bit too lean， especially when quite a complex task is to be solved。 。。。more

Basma ，

Great book！ Loved it and enjoyed reading it and learned so much！ Although felt that some stuff that are mentioned might be a bit outdated as of now， and if you enjoyed reading the sprint book I think you might enjoy Lean UX as they are pretty much similar in concept。

Ruchil ，

Notes“Teams are pushing new code to production as fast as you can save a Photoshop file”“This continuous engagement allows us to strip away heavy deliverables in favor of techniques that allow us to build shared understanding with our teammates。Lean UX also lets us change the way we talk about design。 Instead of talking about features and documents， we can talk about what works。 In this new reality， we have more access to market feedback than ever before。 This feedback allows us to reframe desig Notes“Teams are pushing new code to production as fast as you can save a Photoshop file”“This continuous engagement allows us to strip away heavy deliverables in favor of techniques that allow us to build shared understanding with our teammates。Lean UX also lets us change the way we talk about design。 Instead of talking about features and documents， we can talk about what works。 In this new reality， we have more access to market feedback than ever before。 This feedback allows us to reframe design conversations in terms of objective business goals。 We can measure what works， learn， and adjust。”“Lean UX is three things。 It’s easiest to understand as a process change for designers。 But it’s more than that。 It’s a mindset that lets us approach our work in new ways。 It’s also a way of thinking about managing software。 Chapter - 2 : Principle“Lean UX stands on three foundations。 The first foundation is design thinking。Tim Brown， CEO and president of legendary design firm IDEO， described design thinking as “innovation powered by。。。direct observation of what people want and need in their lives and what they like or dislike about the way particular products are made， packaged， marketed， sold， and supported。。。[It’s] a discipline that uses the designer’s sensibility”“The second foundation of Lean UX is Agile software development。 Software developers have been using Agile methods for years to reduce their cycle times and deliver customer value in a continuous manner。 Although Agile methods can”Agile principles “of Lean UX。 Lean UX applies the four core principles of Agile development to product design:Individuals and interactions over processes and tools。 To generate the best solutions quickly， you must engage the entire team。 Ideas must be exchanged freely and frequently。 The constraints of current processes and production tools are eschewed in favor of conversation with colleagues。Working software over comprehensive documentation。 Every business problem has endless solutions， and each member of a team will have an opinion on which is best。 The challenge is figuring out which solution is most viable。 By building working software sooner “solutions can be assessed for market fit and viability。Customer collaboration over contract negotiation。 Collaborating with your teammates and customers builds a shared understanding of the problem space and proposed solutions。 It creates consensus behind decisions。 The result？ Faster iterations， real involvement in product making， and team investment in validated learning。 It also lessens dependency on heavy documentation， as everyone on the team has already participated in making the decisions that were used to require written communication and defense。”Responding to change over following a plan。 The assumption in Lean UX is that the initial product designs will be wrong， so the goal “should be to find out what’s wrong with them as soon as possible。 Once we discover what’s working and what’s not， we adjust our proposals and test again。 This input from the market keeps us agile， constantly nudging us in a “more right” direction。The third foundation of Lean UX is the Lean Startup method founded by Eric Ries。 Lean Startup uses a feedback loop called “build-measure-learn” to minimize project risk and gets teams building quickly and learning quickly。 Teams build Minimum Viable Products （MVPs） and ship them quickly to begin the process of learning as early as possible。“The practice of Lean UX is: Lean UX is the practice of bringing the true nature of a product to light faster， in a collaborative， cross-functional way that reduces the emphasis on thorough documentation while increasing the focus on building a “shared understanding of the actual product experience being designed。”PrinciplesIn the rest of this chapter， I’ll lay out the principles behind Lean UX。 As you explore the Lean UX approach， keep these principles in mind。 Think of your experience with Lean UX as a learning journey。 Use these principles to keep you and your team on course。Principle: Cross-Functional TeamsWhat is it？ Cross-functional teams are made up of the various disciplines involved in creating your product。 Software engineering， product management， interaction design， visual design， content strategy， marketing， and quality assurance （QA） should all be included in a Lean UX team。 Lean UX demands a high “level of collaboration between these disciplines。 Their involvement must be continuous， from day one of the project until the end of the engagement。Why do it？ The creation of these diverse teams collapses the gated-handoff process known as waterfall。 Insight on each idea is brought in from all relevant disciplines earlier in the process。 Conversation is encouraged across functional silos， which drives greater team efficiency。”“Principle: Small， Dedicated， ColocatedWhat is it？ Keep your teams small—no more than 10 total core people。 Dedicate them to one project and staff it all out of the same location。Why do it？ The benefit of small teams comes down to three words: communication， focus， and camaraderie。 Smaller teams are easier to keep current on”GOOB : “What is it？ It may sound like a baby’s first word， but GOOB is actually an acronym for what Stanford professor， entrepreneur， and author Steve Blank calls “getting out of the building。” It’s the realization that meeting-room debates about user needs won’t be settled conclusively within your office。 Instead， the answers lie out in the marketplace， outside of your building”“Principle: Anti-Pattern: Rockstars， Gurus， and NinjasWhat is it？ Lean UX advocates a team-based mentality。 Rockstars， gurus， ninjas， and other elite experts of their craft break down team cohesion and eschew collaboration。Why do it？ Rockstars don’t share—neither their ideas nor the spotlight。 Team cohesion breaks down when you add individuals with large egos who are determined to stand out and be stars。 When collaboration breaks down， you lose the environment you need to create the shared understanding that allows you [to avoid repetition] to move forward effectively。”“Principle: Permission to FailWhat is it？ In order to find the best solution to business problems， Lean UX teams need to experiment with ideas。 Most of these ideas will fail。 The team must be safe to fail if they are to be successful。 Permission to fail means that the team has a safe environment in which to experiment。 That philosophy applies to both the technical environment （they can push out ideas in a safe way） and the cultural environment （they won’t be penalized for trying ideas that don’t succeed）。Why do it？ Permission to fail breeds a culture of experimentation。 Experimentation breeds creativity。 Creativity， in turn， yields innovative solutions。 When teams don’t fear for their jobs if they get something wrong， they’re more apt to take risks。 It is from”“Why do it？ Documents don’t solve customer problems—good products do。 The team’s focus should be on learning which features have the biggest impact on the their customers。 The artifacts the team uses to gain that knowledge are irrelevant。 All that matters is the quality of the product， as measured by the market’s reaction to it”Part II : Processes “This is the day-to-day rhythm of Lean UX: a team working collaboratively， iteratively， and in parallel， with few handoffs， minimal deliverables， and a focus on working software and market feedback。 In this section， you’ll see how it’s done”“Chapter 3。 Vision， Framing， and Outcomes”“Our goal is not to create a deliverable， it’s to change something in the world—to create an outcome”“AssumptionsA high-level declaration of what we believe to be true。HypothesesMore granular descriptions of our assumptions that target specific areas of our product or workflow for experimentation。OutcomesThe signal we seek from the market to help us validate or invalidate our hypothesis。 “These are often quantitative but can also be qualitative。PersonasModels of the people for whom we believe we are solving a problem。FeaturesThe product changes or improvements we believe will drive the outcomes we seek。”Hypothesis Testing “Sometimes—if not most of the time—you will discover that your hypothesis is too big to test with one test。 It will contain too many moving parts， too many subhypotheses。 When this happens， I find it helpful to break the hypothesis down into smaller and more specific parts。 Though there are many ways to do this， for product work I have found that this format is very helpful:We believe that[doing this/building this feature/creating this experience]for [these people/personas]will achieve [this outcome]。We will know this is true when we see[this market feedback， quantitative measure， or qualitative insight]。The first field is completed with the feature or improvement you’re considering making to your product。 The second field describes exactly which of your target customers will benefit from this feature。 The last field speaks to the benefit those”“Proto-personas are our best guess as to who is using （or will use） our product and why。 We sketch them on paper with the entire team contributing—we want to capture everyone’s assumptions。 Then， as we learn from our ongoing research， we quickly find out how accurate our initial guesses are， and how we’ll need to adjust our target audience （and persona）—and thus our design”Chapter - 4。 Collaborative DesignAs you navigate through the rest of your life， be open to collaboration。 Other people and other people’s ideas are often better than your own。 Find a group of people who challenge and inspire you， spend a lot of time with them， and it will change your life。”“Finally， collaborative design builds team-wide shared understanding。 It is this shared understanding that is the currency of Lean UX。 The more the team collectively understands， the less it has to document in order to move forward。”Style GuidesOne tool that makes collaborative design easier is the style guide。 A style guide is a broadly “accepted pattern library that codifies the interactive， visual， and copy elements of a user interface and system。 Style guides （also known as pattern libraries） are a living collection of all of your product’s customer-facing components。 If it’s made of pixels， it goes in the style guide。 Headers， footers， grids， forms， labels， button logic， and everything else that goes into your product’s user experience goes in the style guide。”“Interaction and visual designers benefit as well。 They no longer have to recreate representations of experiences that already exist。 They become free to focus on new design challenges—novel interaction problems or extending the visual system to new elements。 Approval cycles are streamlined because the repetitive elements （e。g。， the treatment of the global navigation） are no longer up for debate。 Reviews become more focused on the core product challenge and broader views of the proposed solution。”“On the whole， men become aroused a lot faster than a woman。 And while a man can rape a woman， the reverse is not true as she can’t force him to achieve an erection though that’s not to say， as studies have shown， that a woman can’t coerce a man into having sex even if she can’t physically force him into doing so。 But still， all these factors have to be integrated in how humans act when it comes to entering the sexual continuum。And let’s face it， the man still is the one expected to push the sexual side of the relationship forward。 That’s not to say that there aren’t plenty of women who aren’t afraid of being sexually assertive but they also understand that they risk turning the man they’re with off if they come on too strong”“use where and at what size/weight）。 The same attributes of what， where， and when provided for interaction design elements should also be included here。Finally， ensure that copywriting styles are codified as well。 Capture the tone of your brand， specific words you will and won’t use， grammatical choices， tolerated （and not tolerated） colloquialisms， along with button language （OK？ Yes？ Go？ etc。） and other navigation language （previous/next， more/less， etc。）。”Types of design “Separate your TOC into interaction design， visual design， copywriting， branding guidelines， accessibility needs， and any other high-level sections that make sense for your business。The big bang approach （in which your team creates the entire style guide in advance of any project） works well if you have a young product or a relatively simple one”“The slow drip approach works well if you have a legacy or complex product。“Creating an MVPWhen you start planning your MVP， the first thing you have to do is consider what you’re trying to learn。 It’s useful to think about these three basic questions:Is there a need for the solution I’m designing？Is there value in the solution and features I’m offering？Is my solution usable？”“Be clear and conciseSpend your time distilling your idea to its core value proposition and present that to your customersPrioritize ruthlesslyIdeas， like artifacts， are transient。 Let the best ones prove themselves。”“Stay agileInformation will come in quickly， so make sure that you’re working in a medium that allows you to make updates easily。Measure behaviorBuild MVPs that allow you to observe and measure what people actually do， not just what people say。 In digital product design， behavior trumps opinion。”“Chapter 6。 Feedback and ResearchResearch is formalized curiosity。 It is poking and prying with a purpose。—Zora Neale Hurston”“Collaborative research techniques that allow you to build shared understanding with your teamContinuous research techniques that allow you to build small， informal qualitative research studies into every iterationWhich artifacts to test and what results you can expect from each of these testsHow to incorporate the voice of the customer throughout the Lean UX cycleHow to use A/B testing （described later in this chapter） in your researchHow to reconcile contradictory feedback from multiple sources” 。。。more

Iga ，

It was good to read it again before a course about the topic， but I feel like the book would benefit from an update。

Peter ，

Meget let læslig。 Specielt første del er god og giver nogle gode overordnede pointer

Khai Sheng ，

I'll admit i went into this book with different expectations， hoping to learn about UX and how to make the process more UX。 Although the book does introduce typical UX techniques， it does not however introduce anything particularly groundbreaking towards my understanding of UX。 This may be because the book was written quite a while back in 2013 and it may be the pioneer of its time。What it does pretty well however is produce good examples of how a transformative framework can be applied to the w I'll admit i went into this book with different expectations， hoping to learn about UX and how to make the process more UX。 Although the book does introduce typical UX techniques， it does not however introduce anything particularly groundbreaking towards my understanding of UX。 This may be because the book was written quite a while back in 2013 and it may be the pioneer of its time。What it does pretty well however is produce good examples of how a transformative framework can be applied to the workplace， and how to shift the company's objectives to focus on iteration and collaboration。 3。5/5 。。。more

Ricardo Rincón ，

A must read if you work in product development at a startup， some things could be seen as outdated but I prefer to call it a timeless useful tool， specially if you want to apply good UX into an agile process of product building。

Viktor ，

The content is great， but have followed his and Pattons work for years and this was repetitive/repackaged content。

Zac Whitely ，

A great overall guide to UX processes and some of the pitfalls of introducing them in larger organisations。

Reference

google book https://www.google.com/search?tbm=bks&q=Lean UX: Creating Great Products with Agile Teams

hathitrust digital library https://babel.hathitrust.org/cgi/ls?q1=Lean UX: Creating Great Products with Agile Teams&field1=ocr&a=srchls&ft=ft&lmt=ft

The British Library https://bll01.primo.exlibrisgroup.com/discovery/search?query=any,contains,Lean UX: Creating Great Products with Agile Teams&tab=LibraryCatalog&search_scope=Not_BL_Suppress&vid=44BL_INST:BLL01&lang=en&offset=0