Go from Bad to Awesome with Lean UX

Replace This image in master

Presentation

Ricardo LuizUX & UI Team Lead @ OutSystems

2

https://www.linkedin.com/in/uxluiz

ricardo.luiz@outsystems.com @UXLuiz

https://pt.pinterest.com/ricardoluiz102/

3

Why UX?(User Experience)

After all, we are a software company, not a design agency…

4

The cost of fixing an error after developing a solution is

100xmore expensive than if you test it early with users

Check Out: Why software fails by IEEE The ROI of User Experience with Dr. Susan Weinschenk

5

50%Of development time is spent on rework that could be avoided

Check Out: Why software fails by IEEE The ROI of User Experience with Dr. Susan Weinschenk

Agenda

● Why is an awesome UX so critical? The ROI of UX

● How to go from a screen to an experience?

○ Start small to win big

○ What an MVE is and what it does

● Why Lean UX?

○ How to

○ The key factors

○ What you gain by talking to users

● Our Process

● How to avoid UX traps and go after the rainbow

6

Why is an awesome UX so critical?

Why does Software Fail?

“Poor communication among customers, developers, and users”

“Badly defined system requirements”

8Check Out: IEEE

Why does Software Fail?

9

● Frustration: Big bang deployments “Uhhmmm, so after all this time, this is it? OK...”

● Not up to stakeholder’s standards and user expectations: “I was expecting something

great. Can you make it a little bit more like Slack?”

● It is expensive to rework: “Can we change this?”

Can UX help?

10

● “We need to impress”

● “This needs to look great”● “They already know what they want”

Can UX help?

11

● Requirements

● User Stories

Can UX help?

12

Consider the time, costs and quality impact of:

● Failing to address the end-users needs

● Not meeting client’s goals

● Not having any “visual” specifications

● Not testing and picking the best alternative

● Making future changes

● Fixing issues in production

Can UX help?

13

You can do it

Don’t Give Up

How to go from a screen to an experience?

Start Small to win Big

15

MVE: Minimum Viable Experience

16

MVE vs MVP

How to MVE?

17

Why Lean UX?

How to: Lean UX

● Short cycles (5 days max) with deliverables

● Small and focused iterations

● Test solutions with Users

● Fail fast or fail big

19Sources: Google Ventures Design Sprint

Google Design Sprints by Agile Marketing

Example

● Google Ventures Design Sprint

How to: Lean UX

20

Example

● UX @OutSystems

Kick-Off Meeting

Workshop Plan

Clarify Business Goals

DAY 1

Process Data

App Analytics

Detailed Analysis

Vision Document

DAY 2 DAY 3

Wireframes development

Share initial Vision with stakeholders

DAY 4

Usability Testing of Wireframes

with real users

Wireframes development

Describe Business Processes

User Interviews

App Walkthrough

DAY 5

Wireframes review

Process Feedback

Vision Presentation

The Key Factors

21Source: The Elements of User Experience

Example

● The Elements of User Experience

by Jesse James Garrett

Fit with the OutSystems

Method DAY 1

DAY 2

DAY 3

DAY 4

DAY 5

The Key Factors

22Sources: The 7 Factors that Influence User Experience

User Experience Design

Example

● The 7 Factors that influence User Experience (Peter Morville)

What you gain by talking to users

23

● You gain insights from those who will use the

system;

● They will probably have pains to report;

● They use shortcuts (some Shadow IT*);

● You gain a better understanding of who you are

building a solution for;

*Shadow IT = systems or apps that people use to accomplish a goal

but that are outside of the “official system”

What you gain by talking to users

24

What you gain by talking to users

25

The Lean UX Master

26Source: The Elements of User Experience

If you have a hammer, not everything is a nail.

Each project and each team can and will adapt

these methods to their organizations and projects.

Our Process

Lean UX: The OutSystems way

28

Bus

ines

s A

naly

sis

Use

r Res

earc

h

Wire

fram

es

Vis

ual D

esig

n

Live

Sty

le G

uide

Go

Live

Lean UX: The OutSystems wayB

usin

ess

Ana

lysi

s

29

Define clear goals

Understand the business

Interview main stakeholders

Review current application(s)

Get application analytics

Figure out the different user profiles

Identify what to ask the users

Lean UX: The Outsystems way

30

CONTEXT IS KING

Don’t learn the business with the usersCreate a context rich environment

Identify goals and constraints

Lean UX: The OutSystems way

31

Bus

ines

s A

naly

sis

Use

r Res

earc

hLet us Meet the Users

Lean UX: The OutSystems way

32

Use

r Res

earc

hPlanningIdentify the different user profiles

Talk to, at least, 2 users for each profile

Dress appropriately – blend in

Don’t take a committee – 2 people, max 3

Bring someone they already trust

Lean UX: The OutSystems way

33

Use

r Res

earc

hWhat To DoCreate rapport

Compliments and Complaints

Where do they spend their time

Known Unknowns vs. Unknown Unknowns

3 things we must fix

3 things we cannot break

Gather, organize, prioritize

NOTHING LIKE WATCHING CURRENT USAGE AND

UNDERSTAND WHAT DRIVES ITWhen we watch the users in their natural environment we get real data on

how they use the system and what for.

That way we discover the natural journey and can identify gaps within the intended usage of the system(s).

Shadow IT can be discovered at this stage.

NEVER ASK THE USER WHAT HE/SHE WANTS

The users will report different needs. The challenge is to get what is the root of those needs.

When you tap into that, you will solve a problem and make users lives easier.

TIMES CHANGE, PEOPLE CHANGE… NEW NEEDS ARISE!

Lean UX: The OutSystems way

37

Bus

ines

s A

naly

sis

Use

r Res

earc

h

Wire

fram

es

Fail fast or fail loudly

Lean UX: The OutSystems way

38

Wire

fram

esDon’t let ideas escape

Rich context makes it a ton easier

Information organization is key

Keep sketching

IA comes hand-in-hand with mockups

Challenge designs continuously

Lean UX: The OutSystems way

39

Wire

fram

es

Wireframes are quick to produce and a great tool to gather feedback, early on, from stakeholders and even users.

Feedback is focused on function, information architecture, user tasks, user interactions, and so on, rather than being lost in graphic details or implementation glitches.

Lean UX: The OutSystems way

40

Wire

fram

es

WIREFRAMES ARE A POWERFULCHANGE MANAGEMENT TOOL

Everyone can understand what the changes meanand where the company is headed

You can defeat the unknown… make change easier!

Lean UX: The OutSystems way

42

Bus

ines

s A

naly

sis

Use

r Res

earc

h

Wire

fram

es

Vis

ual D

esig

n

Make it Awesome

Lean UX: The OutSystems way

43

Vis

ual D

esig

n

The Visual Design is created over the wireframes to support and extend the developed concept.

It is custom built to implement your branding and make use of the OutSystems platform’s patterns and widgets.

VISUAL DESIGN IS KEYFOR INITIAL ADOPTION

Usability benefits only kick in after the initial impression

Lean UX: The Outsystems way

45

Live

Sty

le G

uide

Webinar: Building a Live Style Guide

Lean UX: The Outsystems way

46

Go

Live

Keep it RealKeep testing with real users

Identify user difficulties

Prepare users for what’s coming

Understand ramp up needed for users

Teasers and Presentation Videos

Controlled rollout with a BETA version

IT AIN’T OVER UNTIL THE FAT USER SINGS

It’s easy to get it wrongStay close to the users and react, fast

How to avoid UX traps

Extras

49

Developer’s UX Checklist: Full Article

Checklist PDF version

Extras

50

Download UX for IT

Extras

51

Stay sharp, more goodies on the way:

● Forms that work;● Design Principles;● Balsamiq Stencils;● Dribbble Account (Sketch Files available);

Food for Thought

52

Thank you