"Practice of bringing the true nature of a product to light faster, in a collaborative, cross-functional way that reduces the emphasis on thorough documentation while increasing the focus on building a shared understanding of the actual product experience being designed."

LEAN UX - Definition

Friday 7 March 14

Design Thinking• Practical, solution-focused process• Observation & creativity• Improved future (added value)

LEAN UX - Foundations

Agile Methodology• Better respond to unpredictability• “Inspect and adapt”• Iterative, incremental, collaborative

Lean Startup• Continuous validated learning• Eliminate waste• Create business value

Friday 7 March 14

LEAN UX - Principles

Continuous discovery• Customer validation (GOOB) • Small batch, short iterations• Permission to fail (try & learn)• Externalize (expose your work/ideas to teammates, peers, stakeholders, users)

Outcome over output• Experience > product• Solving problems > building features• Shared understanding > deliverables• Eliminate waste

Friday 7 March 14

Optimal profile• Cross-functional• Small (“2 pizza team” rule)• Dedicated (throughout the project)• Colocated (no barriers)

LEAN UX - TEAM

Mindset• Teamwork• No hero• Skills over roles• Open lines of communication

Friday 7 March 14

LEAN UX - tools

Other tools• Style guide (accessible, actionable, continuously improved)• Proto-personas (contin. improved)• Prototypes (from paper to code)• Non-prototypes MVPs

Collaborative design• Either informal session (conversation)• Or Design Studio with whole team:

1. Problem definition + constraints2. Individual idea generation3. Presentation & critique4. Iterate & refine5. Team idea generation

Friday 7 March 14

1. Problem statementBusiness goals, problem, improvement request

2. State business/user assumptionsCapture what team thinks is true

3. Prioritize assumptionsRisky/Unknown first

4. (Sub)Hypothesis statementAssumption, feature, user, outcome, feedback

5. Create MVPMax. amount of insight with min. effort! NOT a lightweight version of the product

6. Collaborative/Continuous discoveryTeam on the field/lab: interview, user testingKeep distance hypothesis/validation short

7. Making sense of the feedbackAs soon as possible & as a teamLook for patternsCheck against other sources

LEAN UX - process

Declareassumptions

Create an MVP

Run an experiment

Research& feedback

As ateam

Friday 7 March 14

In an Agile process• Sprint as structured iteration• 1 sprint = 1-2 iterations of the 4 steps• Validation as part of the planning

LEAN UX - making it work

In a web agency• 3 validation levels: team/users/client• Proactive communication• Client must feel involved in the team• Organizational/company culture shift (team, project sales/mngt...)

Friday 7 March 14

Within the team• Lean UX seen as lazy UX

• no vision• no responsibility• no discipline• going too fast (no research / retro)

• Loosing sight of the big picture• Distributed teams

LEAN UX - pitfalls

With our clients• Fixed scope / roadmap• Collaboration• No time/money/will for user validation

Friday 7 March 14

Congratulation!you didn’t fall asleep

QUESTIONS ?cheers?

Hugs?

Donations?

LEAN UX - the end

Friday 7 March 14