Lean UX is focused on the experience under design and is less focused on deliverables than traditional UX. It requires a greater level of collaboration with the entire team. The core objective is to focus on obtaining feedback as early as possible so that it can be used to make quick decisions. The nature of Agile development is to work in rapid, iterative cycles and Lean UX mimics these cycles to ensure that data generated can be used in each iteration.
Lean UX Process
Vision, framing, and outcomes
Start with assumptions instead of requirements. Create and test hypotheses:
- Assumptions: what we believe to be true
- Hypotheses: more granular descriptions of our assumptions that target specific areas of the product or workflow
- Outcomes: the signal we seek from the market to help (in)validate the hypothesis
- Personas: models of the people for whom we believe we are solving a problem
- Features: the changes or improvements we believe will drive the outcomes we seek
- Everybody gets to design
- Low fidelity artifacts increase collaboration
- Build shared understanding
- Design studio
- Style guides and pattern libraries
- Collaboration for distributed teams
MVP’s & Experiments
- Determine product focus: deliver value or increase learning
- MVP: Do people need it? Will it provide value? Will it be usable?
- Prototype: Who will interact? Learning what? Time available?
- Experiments without prototypes: email, google AdWords., landing page, a button to nowhere
Feedback and research
- Collaborative research techniques
- Continuous research techniques (3 users every Thursday)
- What to test, what results to expect
- Incorporate the customer’s voice
- A/B testing
- Reconcile contradictory feedback
Basically, the whole idea behind Lean UX is to be as efficient as possible. The goal is to reduce the amount of time that comes with writing the traditional UX documents and spending long hours analyzing different cases in a meeting. Instead, the team focuses on regular interactions with real customers through UX interviews and early testing.
Design only what you need. Deliver it quickly. Create enough customer contact to get meaningful feedback fast.
- Cross-functional teams
- Small, dedicated, colocated
- Progress = outcomes, not output
- Problem focussed teams
- Remove waste
- Small batch sizes
- Continuous discovery
- Getting out of the building
- Shared understanding
- Antipattern: Rockstars, Gurus & Ninjas
- Externalising the work
- Making over analysis
- Learning overgrowth
- Permission to fail
- Getting out of the deliverables business
The Lean UX Manifesto
- Early customer validation over releasing products with unknown end-user value
- Collaborative design over designing on an island
- Solving user problems over designing the next “cool” feature
- Measuring KPIs over undefined success metrics
- Applying appropriate tools over following a rigid plan
- Nimble design over heavy wireframes, comps or specs
- Summary Lean UX
- A Simple Introduction to Lean UX
- The Lean UX Manifesto: Principle-Driven Design
- Why should you adopt Lean UX principles?
The cognitive walkthrough is a usability evaluation method in which one or more evaluators work through a series of tasks and ask a set of questions from the perspective of the user. The focus of the cognitive walkthrough is on understanding the syst...
An interview in qualitative research is a conversation where questions are asked to elicit information. The interviewer is usually a professional or paid researcher, sometimes trained, who poses questions to the interviewee, in an alternating series ...
In research of human subjects, a survey is a list of questions aimed at extracting specific data from a particular group of people. Surveys may be conducted by phone, mail, via the internet, and sometimes face-to-face on busy street corners or in mal...
A persona in user-centered design and marketing is a fictional character created to represent a user type that might use a site, brand, or product in a similar way. Marketers may use personas together with market segmentation, where the qualitative p...
The usability of a system is improved when its status and methods of use are clearly visible. The more visible functions are, the more likely users will be able to know what to do next. Incontrast, when functions are "out of sight," it makes the...
A tendency to find forms that appear humanoid or exhibit humanlike characteristics appealing. In 1915, worried that their straight-sided bottle could be easily confused with those of imitators, the Coca-Cola company set out to create a distinctive n...