{"id":6828,"date":"2022-06-13T14:47:36","date_gmt":"2022-06-13T14:47:36","guid":{"rendered":"https:\/\/www.uxdesigninstitute.com\/blog\/?p=6828"},"modified":"2024-01-16T12:20:44","modified_gmt":"2024-01-16T12:20:44","slug":"what-is-lean-ux","status":"publish","type":"post","link":"https:\/\/www.uxdesigninstitute.com\/blog\/what-is-lean-ux\/","title":{"rendered":"What is lean UX and why does it matter? A complete guide"},"content":{"rendered":"

In 2013, Jeff Gothelf published a book called <\/span>Lean UX: Designing Great Products with Agile Teams<\/span><\/i><\/a>. In doing so, he introduced a revolutionary approach to the way products are designed and built.\u00a0<\/span><\/p>\n

Since then, lean UX has become quite the buzzword, favoured by startups and agile practitioners. But what does it all mean?\u00a0<\/span><\/p>\n

If you\u2019re looking for a no-nonsense, jargon-free guide to lean UX, look no further. We\u2019ll explain:<\/span><\/p>\n

    \n
  1. What lean UX is<\/span><\/a><\/li>\n
  2. The difference between lean UX and traditional UX<\/span><\/a><\/li>\n
  3. The principles of lean UX<\/span><\/a><\/li>\n
  4. The lean UX process<\/span><\/a><\/li>\n
  5. What\u2019s so great about lean UX<\/span><\/a><\/li>\n<\/ol>\n
    \n\t
    \n\t\t
    \n\t\t\t
    \n \n

    [GET CERTIFIED IN UX]<\/p>\n Take our Professional Diploma in UX Design course<\/span>\n <\/a>\n\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n<\/section>\n\n

    1. What is lean UX?<\/strong><\/h2>\n

    Lean UX is a collaborative, iterative way of designing and building products.\u00a0<\/span><\/p>\n

    It goes hand-in-hand with the agile methodology, which originated in the software industry. The agile methodology breaks a project up into short, rapid cycles in order to get things done quickly, with continuous testing and improvements along the way. Lean UX follows a similar approach, working in a constant loop of thinking, making, and testing.\u00a0<\/span><\/p>\n

    The purpose of lean UX is to harness the power of collaboration, to reduce waste (in terms of time, effort and resources), and to experiment and build rapidly in order to get feedback early on. With this feedback, the product can be improved incrementally.\u00a0<\/span><\/p>\n

    That\u2019s lean UX in a nutshell. We\u2019ll dive deeper into how lean UX works as we explore the process and principles underlying this increasingly popular approach.\u00a0<\/span><\/p>\n

    2. What\u2019s the difference between lean UX and traditional UX?<\/strong><\/h2>\n

    When following the typical <\/span>UX design process<\/span><\/a>, designers spend a lot of time understanding their users through user research, figuring out the problem space and defining product requirements before they get to actually designing anything. The focus is on scoping out the project fully and comprehensively enough so that when the product is designed and developed, it has a good shot at meeting the user\u2019s needs and adequately solving their pain-points.\u00a0<\/span><\/p>\n

    With lean UX, you\u2019re not looking to get it right (or even close) straight out of the gate. Rather than laying extensive groundwork before you can create something, lean UX has you building a minimum viable product (MVP) quickly and early on. This enables early and continuous feedback so the product can be improved iteratively \u2014 with each iteration (or version) bringing you closer to the end goal. This isn\u2019t to say that lean UX does away with <\/span>user research<\/span><\/a> and testing; they\u2019re just done with a more \u201cquick and dirty\u201d approach.\u00a0<\/span><\/p>\n

    It\u2019s often said that lean UX is more collaborative than the traditional UX process. Because lean UX works in short cycles, there\u2019s a constant back and forth between the designers, developers, product managers and other key stakeholders, as opposed to working in silos. Although “classic” UX is still highly collaborative, the sharing and testing of ideas and solutions is not as continuous as it is with lean UX.\u00a0<\/span><\/p>\n

    Ultimately, traditional UX favours a more thorough, deliverable and documentation-heavy approach prior to actually designing and building anything, while lean UX puts the emphasis on building early on, getting feedback, making quick decisions and improving along the way.<\/span><\/p>\n

    3. The golden rules and principles of lean UX<\/strong><\/h2>\n

    Lean UX is based on certain rules and principles. Let\u2019s take a look at some of the most important ones now.<\/span><\/p>\n

    Lean UX requires cross-functional collaboration\u00a0<\/span><\/h3>\n

    Rather than working in silos (i.e. in isolation), different departments and disciplines work together throughout. With everyone involved at each stage, lean UX helps to ensure a shared understanding of the product, the end users, the problem space and general processes.\u00a0<\/span><\/p>\n

    Lean UX prioritises problem-solving and solution-finding<\/span><\/h3>\n

    Not dissimilar to traditional UX, lean UX places problem-solving front and centre. The emphasis is not on designing or building features for the sake of an output. Rather, it\u2019s about making sure you\u2019re solving the right problem and empowering everyone to come up with solutions.\u00a0<\/span><\/p>\n

    Lean UX seeks to reduce waste<\/span><\/h3>\n

    Lean UX encourages you to skip any parts of the process that are time and resource-heavy (like excessive documentation) and to focus instead on creating an MVP (minimum viable product), which you can quickly learn from. The goal is to accelerate progress and, as the name suggests, make the process leaner and more streamlined.\u00a0<\/span><\/p>\n

    Lean UX says build early and quickly<\/span><\/h3>\n

    As we\u2019ve mentioned, lean UX has you creating an MVP as early as possible. The goal isn\u2019t to create a near-perfect or even great product right away, but rather to build something you can continuously and iteratively improve.\u00a0<\/span><\/p>\n

    \u2026and gives you permission to fail<\/span><\/h3>\n

    Designing and building in this way encourages experimentation and failure. With lean UX, it\u2019s absolutely fine to get it wrong. You\u2019ll learn soon enough because of the continuous feedback loops – and because you\u2019re building quickly –\u00a0 you\u2019ll be able to put it right. And, because you haven\u2019t invested too much time and resources in getting it perfect, the fallout of getting it wrong is minimal.\u00a0<\/span><\/p>\n

    4. The lean UX process<\/strong><\/h2>\n

    The lean UX process centres on three key phases: <\/span>Think<\/b>, <\/span>Make<\/b>\u00a0and <\/span>Check<\/b>. It\u2019s a cyclical process that keeps repeating, with the product improving each time the cycle begins anew.\u00a0<\/span><\/p>\n

    Lean UX phase 1: Think<\/span><\/h3>\n

    The process starts with your assumptions about –\u00a0 and understanding of –\u00a0 the problem space in question. Assumptions are usually gathered in a workshop or through a group brainstorming session and they basically sum up what you collectively assume or think you know.\u00a0<\/span><\/p>\n

    You can gather assumptions about who your users are, what the product you\u2019re designing is used for and when, what the most important functions and features will be and so on.\u00a0<\/span><\/p>\n

    Based on your assumptions, you\u2019ll then create a hypothesis (or multiple hypotheses). For example, you might come up with the following hypothesis:<\/span><\/p>\n

    We believe that online shoppers need to be able to place an order without creating a customer account. Providing this option will increase the number of completed orders \/ reduce the number of \u201cabandoned cart\u201d incidences. We can prove this if we are able to measure an increase in the order completion rate (which currently stands at 15%).<\/span><\/i><\/p>\n

    When writing hypotheses, it\u2019s important that you\u2019re able to set a clear and measurable goal for how each hypothesis can be tested. Otherwise, there\u2019s no way to determine if it\u2019s valid or invalid and therefore worthy of pursuing or not. <\/span>\u00a0<\/span><\/i><\/p>\n

    Lean UX phase 2: Make<\/span><\/h3>\n

    As we know, lean UX is about building early and that\u2019s the focus of the \u201cMake\u201d phase. You\u2019ll now create a minimum viable product (MVP), which is essentially the most basic version you will need in order to test your hypothesis and gather initial learnings and feedback.<\/span><\/p>\n

    The form your MVP takes will depend on your hypothesis and what you want to test. Taking the example of our online shopping hypothesis, the MVP could be an interactive <\/span>prototype<\/span><\/a> of the proposed new checkout process, featuring the additional option to place an order without having to create an account.\u00a0<\/span><\/p>\n

    Otherwise, an MVP might be a very basic wireframe or a website landing page. Anything that can be created quickly and used to test out your hypothesis.\u00a0<\/span><\/p>\n

    Lean UX phase 3: Check<\/span><\/h3>\n

    With your MVP in place, you have something tangible to test and evaluate. In the \u201cCheck\u201d phase, you gather feedback on your MVP in order to invalidate or validate your original hypothesis. You can do this through A\/B testing, site analytics and a variety of user and usability testing methods.\u00a0<\/span><\/p>\n

    Based on your learnings, you\u2019ll loop back to phase 1 (“Think”) and proceed accordingly. Maybe you need to scrap the initial hypothesis and explore a different problem or perhaps it\u2019s necessary to generate new ideas and angles for the same hypothesis. Either way, you\u2019ll build on the previous cycle and continue to steer the product towards success.\u00a0<\/span><\/p>\n

    5. What\u2019s so great about lean UX?<\/strong><\/h2>\n

    You\u2019ve read this far, so you probably already have a good idea of why lean UX is so popular.\u00a0<\/span><\/p>\n

    Compared to traditional UX, lean UX is hailed as a huge time and money saver \u2014 and, perhaps most importantly, it keeps designers focused on solving the right user problem at the right time.<\/span><\/p>\n

    With the traditional approach to UX, you might spend months designing a particular feature or solution, investing considerable time and resources along the way, only to find that by the time your designs are developed and tested, requirements have changed. The idea you came up with four months ago is no longer relevant or fitting, sending you right back to the drawing board.\u00a0<\/span><\/p>\n

    Now imagine how that changes if you take a lean approach. You would build and test your initial idea early on, making sure you\u2019re solving the right problem before you invest any more time and resources. By working in short cycles with continuous testing and feedback, you\u2019re able to adapt to changing requirements in real-time.\u00a0<\/span><\/p>\n

    Lean UX is especially popular with startups and teams who don\u2019t have infinite resources at their disposal. So, if you\u2019re a UX designer with aspirations of working in a startup or a company which follows the agile methodology, it\u2019s important to understand what lean UX is and how it works.\u00a0<\/span><\/p>\n

    Hopefully this guide has got you off to a good start! If you\u2019d like to dive deeper into lean UX, we can recommend <\/span>Jeff Gothelf\u2019s book on the topic<\/span><\/a>.\u00a0<\/span><\/p>\n

     <\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    Lean UX is a collaborative, iterative way of designing and building products – but why is it so important?<\/p>\n","protected":false},"author":24,"featured_media":6829,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[278],"tags":[321],"class_list":["post-6828","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-design","tag-lean-ux"],"_links":{"self":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/6828","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/comments?post=6828"}],"version-history":[{"count":8,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/6828\/revisions"}],"predecessor-version":[{"id":9719,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/6828\/revisions\/9719"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/media\/6829"}],"wp:attachment":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/media?parent=6828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/categories?post=6828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/tags?post=6828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}