Traditionally UX design is generally deliverables-based including:
It generally follows a waterfall development approach and looks like this:
Define Design Develop Test Deploy
Lean UX design moves away from traditional deliverables based design as it tends to make designers become documentation experts, rather than putting focus on the quality of the final user experience.
Deeply Collaborative and Cross-Functional
Lean UX needs daily (or as often as possible), continuous engagement with your teams to be effective. It strips away all of the heavy deliverables and increases a team’s ownership for the work by giving opportunity for all opinions to be heard much earlier in the process. Instead of talking about features and documents, teams can talk about what works. Combined with market feedback it allows us to reframe design conversations and allows us to measure what works. Then it’s just a matter of learning, and adjusting.
Typical Lean UX Design Process
This is the planning phase of the UX design process. It involves many meetings to brainstorm what the product will look like, how it functions, and most importantly if it is a good user experience.
There are 2 key concepts to put into practice at this phase and throughout the rest of the UX process. The first is creating a hypothesis. The second is called MVP (Minimum Viable Product).
A prototype is a representation of what the user experience will be. Choosing which tool to use for your prototype depends on:
Different Types of prototypes:
User Testing (Validate Internally, Test Externally & Learn from user behavior)
User testing in Lean UX is much like user testing in traditional UX environments. The difference is that results need to be delivered before the next Agile Sprint starts; so there is much less focus on heavily documented user-testing results. The results can then be looked at to determine the changes going into the next Sprint.
Repeat as necessary...