15
DELIVER VALUE NOT QUANTITY, A LEAN UX APPROACH Oana Mangiurea UX/UI Designer at Veritech.io

Deliver value not quantity, a Lean UX approach

Embed Size (px)

Citation preview

DELIVER VALUE NOT QUANTITY, A LEAN UX

APPROACHOana Mangiurea

UX/UI Designer at Veritech.io

USER EXPERIENCE WHAT?

WHAT’S LEAN UX?

Lean UX is a simplified process focused on

removing waste from our design deliverables,maximizing team work and actually use rapidexperimentation and measurement, instead onrelying only on the designer’s last night dream.

PS: our aim is to get things to work not writing thenext best seller 60 pages documentation novel

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

IT’S THIS FASTOR EVEN FASTER

LEAN VS AGILE VS TRADITIONAL UX

TIME TO PUT IT AT WORK

1. Identify the problem

2. Define your personas

3. Sketch

4. Build

5. Measure/Validate

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

MEET OUR PERSONA

TIME TO SKETCH

Intermediary sketch

Before that we used the

whiteboard for about 30 minutes

and 3 websites for inspiration

THE BUILD

I work quick in Photoshop but

you could use any tool you

want: HTML, Axure, Balsamiq,

Flash (emm, maybe not that)

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

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

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

THANKS! QUESTIONS?

Sometimes I tweet about UX, follow me: @Caelea