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?
Weighted Decision Matrix. A weighted decision matrix is a tool used to compare alternatives with respect to multiple criteria of different levels of importance. It can be used to rank all the alternatives relative to a “fixed” reference and thus ...
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_...
A systematic examination of the material, aesthetic, and interactive qualities of objects It asks what objects say about people and their culture, time, and place rather than focusing on what people say about the products and systems they use. ...
The Elito method was the first analysis method we used, and it is basically based on brute force thinking. The nature of this method is definitely data analysis since you use it to analyze data. The context that you will use this method is if you ...
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...
This is used to document observable human activities and personal characteristics, interactions, time spent at fixed locations or in transit, and details of environmental context. A sketch map or architectural floor plan is used as the underla...