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 Fogg Behavior Model shows that three elements must converge at the same moment for a behavior to occur: Motivation, Ability, and Trigger. When a behavior does not occur, at least one of those three elements is missing. [caption id="attachment_...
Interaction personas focus instead on the touchpoints and the user’s mental state and the context in these specific moments, pinpointing crucial elements that could help to improve the product. It’s a very effective way to explore the possibil...
A cognitive map (sometimes called a mental map or mental model) is a type of mental representation which serves an individual to acquire, code, store, recall, and decode information about the relative locations and attributes of phenomena in their ev...
A tendency to interpret shaded or dark areas of an object as shadows resulting from a light source above the object. Humans are biased to interpret objects as being lit from a single light source from above. This bias is found across all age range...
The User-centered design (UCD) process outlines the phases throughout a design and development life-cycle all while focusing on gaining a deep understanding of who will be using the product. The international standard 13407 is the basis for many U...
Testing of prototypes, products, or interfaces by users of a system in design development This gauges human expectations against a designed artifact, determining whether something is useful, usable, and desirable. Testing should collect per...