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?
Wizard of Oz prototyping. Wizard of Oz prototyping (WOZ prototyping) is a design methodology used in rapid product development to improve the user experience (UX). WOZ prototyping requires developers to create a rudimentary model of the completed pro...
The design-thinking ideology asserts that a hands-on, user-centric approach to problem-solving can lead to innovation, and innovation can lead to differentiation and a competitive advantage. This hands-on, user-centric approach is defined by the desi...
Reporting and analyzing user queries submitted as search criteria on a site Analyzing words and phrases entered into a search provides insight into what people are looking for in order to evaluate how well content meets those needs. Site Se...
Think-aloud (or thinking aloud) protocol (also talk-aloud protocol) is a protocol used to gather data in usability testing in product design and development, in psychology and a range of social sciences (e.g., reading, writing, translation research, ...
Eye tracking is the process of measuring either the point of gaze (where one is looking) or the motion of an eye relative to the head. An eye tracker is a device for measuring eye positions and eye movement. Technical information documenting whe...
A heuristic evaluation is a usability inspection method for computer software that helps to identify usability problems in the user interface (UI) design. It specifically involves evaluators examining the interface and judging its compliance with rec...