{"id":1833,"date":"2021-05-29T10:27:00","date_gmt":"2021-05-29T10:27:00","guid":{"rendered":"http:\/\/nyxditech.com\/blog_staging\/?p=1833"},"modified":"2021-07-02T05:10:45","modified_gmt":"2021-07-02T05:10:45","slug":"lean-ux-basics","status":"publish","type":"post","link":"https:\/\/nyxditech.com\/blog_staging\/lean-ux-basics","title":{"rendered":"A Basic Introduction To Lean UX"},"content":{"rendered":"\n

Lean UX has been debated and discussed in a variety of forums. Some have seen it as a condemnation of extensive documentation while others have said it\u2019s a rebranding of techniques they\u2019ve been practising for years. Lean UX is about 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. <\/p>\n\n\n\n

Lean UX is deeply collaborative and cross-functional because we no longer have the luxury of working in isolation from the rest of the product team. We can\u2019t continue to ask our teams to wait for us to figure it all out. We need daily, continuous engagement with our teams if we are going to be effective. This continuous engagement allows us to strip away heavy deliverables in favor of techniques that allow us to build shared understanding with our teammates.<\/p>\n\n\n\n

The Lean UX Cycle<\/h2>\n\n\n\n

The cycle contains three phases, and they are Thinking, Making, and Checking or Testing.<\/p>\n\n\n\n

1. Thinking<\/h2>\n\n\n\n

Instead of exactly knowing what you would build, you start with something that might work, so, you build a hypothesis and then find the fastest way to validate that hypothesis.<\/p>\n\n\n\n

In this phase, your team collaborate with different teams in the organization, this is not interrogative but a collaborative effort to generate more ideas or hypothesis to work on. This creates transparency between teams.<\/p>\n\n\n\n

2. Making<\/h2>\n\n\n\n

After building the hypothesis, now you work on the way to validate it, and the best way to validate is to test it with the users of your product in real-time, but before that, we have to build something. This is where the concept of MVP(minimum viable product) comes into the picture. MVP is the smallest possible thing that we can build to help us to learn whether or not our hypothesis is true. That smallest thing could be wireframes, mockups, or working prototypes. The goal of MVP is to validate the hypothesis before committing a huge amount of resources to them.<\/p>\n\n\n\n

3. Checking\/Testing<\/h2>\n\n\n\n

In this phase, we test what we have built (our MVP) with users in real-time, we monitor them while they use our products and provide us with feedback. The goal of this phase to learn, whether a feature\/product likely to succeed before you put resources to completely build it.<\/p>\n\n\n\n

Key Facts About Lean UX<\/h2>\n\n\n\n