To gain a fuller understanding of the Lean UX and the full process, pick up a copy of Lean UX and read it for yourself. To create good outcomes, Lean UX shifts away from what designers think is required of a product to their assumptions. Assumptions are simply your belief or expectation based on what you know about your users. Yes, these are filled with risk and can be outright wrong. There are four types of assumptions: Business outcomes.
|Published (Last):||16 October 2006|
|PDF File Size:||8.39 Mb|
|ePub File Size:||15.94 Mb|
|Price:||Free* [*Free Regsitration Required]|
To gain a fuller understanding of the Lean UX and the full process, pick up a copy of Lean UX and read it for yourself. To create good outcomes, Lean UX shifts away from what designers think is required of a product to their assumptions. Assumptions are simply your belief or expectation based on what you know about your users.
Yes, these are filled with risk and can be outright wrong. There are four types of assumptions: Business outcomes. This is what done looks like. How do you know your product was successful? Who are they? User outcomes. This is what your users want from your product. What are their pain points? How can your product solve them? How you will improve your product going forward in order to give your users the desired outcome. This involves turning your assumptions into hypotheses statements.
Example: We believe our users are middle-aged homemakers who need help with their housework. The hypotheses is a great way to establish what you believe you know about your users and what they need. This is the groundwork for your work going forward. Design This is where you begin to actually design your product. This might also be the time where you can test your hypotheses.
Remember: You must design collaboratively. For example, the teams from across departments must sketch and create wireframes together, and everyone must feel comfortable giving their feedback on everything. Designers should see themselves as facilitators to these conversations and meetings.
There are a variety of different ways you can structure your meetings and conversations as your designs progress. For more, check out chapter four of Lean UX. All of this work becomes part of the minimum viable product. The idea is to get a simple product out to see how your target audience reacts to it. Here are a few: Wireframes. Low-fidelity versions of your product.
Higher-fidelity, full-scale versions of your product complete with designs, colors, and icons. Very basic version of your product with minimal functionality and design. For more, check out our guide on rapid prototyping. You need to build your MVP based on your assumptions and hypotheses. Research and learning This part of the process is all about validation. Are you on the right track? Is your product giving your users what they need? What needs to be changed? Research and learning requires two things to be effective in Lean UX: Continuous.
The goal is for your organization to gain insights in a quick but comprehensive way. This can only happen if you research frequently and collaboratively. Work better together using InVision Cloud. Your users will be a part of this process as well, whether through conversations, interviews, surveys, or whatever else. The conversations you get will validate your hypotheses. Should you use Lean UX?
While there are plenty of great benefits to Lean UX, there are five that might sway you to trying it out for yourself: Increased collaboration.
Lean UX – Getting Out Of The Deliverables Business
A Collaborative Lean UX Research Tool When combined with serial waterfall development methodologies, these design deliverables end up consuming an enormous amount of time and creating a tremendous amount of waste. Waste is defined as anything that is ultimately not used in the development of the working product. Engaging in long drawn-out design cycles risks paralysis by internal indecision as well as missed windows of market opportunity. Image by Claire Murray.
Start free Blinkist trial Upgrade to Premium Read or listen now Synopsis Lean UX is a guide to applying lean principles to interactive design workspaces. Key idea 1 of 7 The three foundational principles of Lean UX are design thinking, agile software development and lean startup. Do you ever see the designers that work for your company? If your business is like most, it likely keeps the design team separate from everyone else, which means that they work in their own little bubble. But what do these terms all mean? First, design thinking is the idea that every aspect of a business can be approached with design in mind. For instance, when a company encounters an issue, it can solve it like a designer would.