A small presentation about what is Lean UX, describing principles and methods. It includes a light case study.

1. DELIVER VALUE NOT
QUANTITY, A LEAN UX
APPROACHOana Mangiurea
UX/UI Designer at Veritech.io

2. USER EXPERIENCE WHAT?

3. WHAT’S LEAN UX?
Lean UX is a simplified process focused on
removing waste from our design deliverables,
maximizing team work and actually use rapid
experimentation and measurement, instead on
relying only on the designer’s last night dream.
PS: our aim is to get things to work not writing the
next best seller 60 pages documentation novel

4. TOP PRINCIPLES
o Cross-Functional Teams (and keep it small)
o Problem-Focused Teams (trying to solve problems, not implement new functionalities)
o Small Batch Size
o Continuous Discovery (aka ask thy client)
o Anti-Pattern: Rockstars, Gurus, and Ninjas
o Externalizing Your Work (just show me what you’ve got)
o Making over Analysis

5. IT’S THIS FAST
OR
EVEN FASTER

6. LEAN VS
AGILE VS
TRADITIONAL UX

7. TIME TO PUT IT AT WORK
1. Identify the problem
2. Define your personas
3. Sketch
4. Build
5. Measure/Validate

8. THE PROBLEM
You have to scroll
horizontally on a laptop
Hard to keep track of the
train information
You need one more click
to see the prices

9. MEET OUR PERSONA

10. TIME TO SKETCH
Intermediary sketch
Before that we used the
whiteboard for about 30 minutes
and 3 websites for inspiration

11. THE BUILD
I work quick in Photoshop but
you could use any tool you
want: HTML, Axure, Balsamiq,
Flash (emm, maybe not that)

12. MEASURE
Can’t show you my friends pictures while testing my interface, because of beer
But here are the techniques I used on this particular case:
o Heatmap
o Small survey
o One to one interviews

13. LEAN MY AGILE WORLD
Cross Functional Teams
o Developers, designers, product owners work together
o Greater accountability + faster design process
Limited Documentation
o Enough to communicate the design
o Since requirements may change, easier to manage documentation

14. SO
Keep in mind that if you are a programmer that doesn’t mean you don’t have a word
to say, so don’t hide
It’s better to give the user something and watch them using it, than to build
“perfection” which nobody cares about
Doesn’t matter how it’s named, if it’s purely Agile, Waterfallish, Lean or not, just test
your interfaces with more than thy self

15. THANKS! QUESTIONS?
Sometimes I tweet about UX, follow me: @Caelea