There is no 'i' in UX.

73
There is no ‘i’ in UX, but maybe there should be.

Transcript of There is no 'i' in UX.

Page 1: There is no 'i' in UX.

There is no ‘i’ in UX, but maybe there should be.

Page 2: There is no 'i' in UX.

I don’t know who you are…

Page 3: There is no 'i' in UX.

Quadrant Chart

An Iceberg

A Colourful Diagram

Badly taken Phone Images

Boring References to UX in Everyday Life

A Unicorn

Screen Shots

Page 4: There is no 'i' in UX.

UX in Everyday Life.

Page 5: There is no 'i' in UX.

The biometric scanner is always glitchy… or not.

Page 6: There is no 'i' in UX.
Page 7: There is no 'i' in UX.
Page 8: There is no 'i' in UX.

Shucks, which entrance does this scanner activate!?

Page 9: There is no 'i' in UX.

Those damn self-service kiosks…

Page 10: There is no 'i' in UX.
Page 11: There is no 'i' in UX.
Page 12: There is no 'i' in UX.
Page 13: There is no 'i' in UX.
Page 14: There is no 'i' in UX.
Page 15: There is no 'i' in UX.
Page 16: There is no 'i' in UX.

Bad UX means having to

pay this lady

Page 17: There is no 'i' in UX.
Page 18: There is no 'i' in UX.

The Kano Model.How to measure the investment of improving customer satisfaction.

Frustraters.

Delighters.

Investment.Us

er Sa

tisfac

tion.

Page 19: There is no 'i' in UX.

The Kano Model.How to measure the investment of improving customer satisfaction.

Frustraters.

Delighters.

Investment.

Basic Expectations.

User

Satis

factio

n.

Page 20: There is no 'i' in UX.

The Kano Model.How to measure the investment of improving customer satisfaction.

Frustraters.

Delighters.

Investment.

Basic Expectations.

User

Satis

factio

n.

If the goal is satisfaction we can never delight.

We can however mess this up.

Page 21: There is no 'i' in UX.

We Have Basic Expectations.Don’t fix what’s broken, just add another feature.

Let’s talk about my stay at Holiday Express.

• Couldn’t pay with my card to by snacks.• Lift didn’t work.• Wifi was fickle.

Lady asks me: “Did you enjoy your stay sir?”

I replied: “It was ok.”

Ok, is the problem. Ok isn’t bringing anyone back anytime soon.

Page 22: There is no 'i' in UX.

We Have Basic Expectations.

?

(

. .

(. .

Delightful Experiences.

Frustrating Experiences.

–. .

Page 23: There is no 'i' in UX.

We Have Basic Expectations.(

. .

(. .

Delightful Experiences.

Frustrating Experiences.

–. . Usable Experiences.

Page 24: There is no 'i' in UX.

Not creating an experience that is sucky, is still not

creating an experience that is delightful.

Page 25: There is no 'i' in UX.

Why does the average user sometimes seem to

be dumb or drunk?

Page 26: There is no 'i' in UX.

The strange thing is most people use interfaces like they’re drunk, but they’re not.

Most people engage with something like they’re dumb, but they’re not.

So what the heck is going on!?

Unlike you, they’re not in love with the interface they’re busy doing other things as well as checking out your interface for the 1st time.

User’s Aren’t Drunk Or Dumb.

Page 27: There is no 'i' in UX.

Do we really know what an MVP is?

Page 28: There is no 'i' in UX.

Delighters vs. Frustraters.

Feature 1.

Don’t fix what’s broken, just add another feature.

Checkout sucks.

Feature 3.

Feature 2.

Feature 4.

vs.

Page 29: There is no 'i' in UX.

You can’t move on until your MVP is delightful, not just

satisfactory.

Page 30: There is no 'i' in UX.

“Start the product process by saying no.”

– Jason Fried, 37 Signals

Page 31: There is no 'i' in UX.

Release 1.0

Feature 1. Feature 2. Feature 3.

Page 32: There is no 'i' in UX.

Release 5.0

Feature 5. Feature 6. Feature 7.

Feature 1. Feature 2. Feature 3.

Feature 9. Feature 10. Feature 11.

Feature 8.

Feature 4.

Feature 12.

Page 33: There is no 'i' in UX.

Release 5.0

Feature 5. Feature 6. Feature 7.

Feature 1. Feature 2. Feature 3.

Feature 9. Feature 10. Feature 11.

Feature 8.

Feature 4.

Feature 12.

Experience Rot.

Page 34: There is no 'i' in UX.

Release 5.0

Feature 5. Feature 6. Feature 7.

Feature 1. Feature 2. Feature 3.

Feature 9. Feature 10. Feature 11.

Feature 8.

Feature 4.

Feature 12.

So what do we do!?

Page 35: There is no 'i' in UX.

Release 5.0

Feature 5. Feature 6. Feature 7.

Feature 1. Feature 2. Feature 3.

Feature 9. Feature 10. Feature 11.

Feature 8.

Feature 4.

Feature 12.

Page 36: There is no 'i' in UX.

Release 5.0

Feature 5.

Feature 10.

Feature 4.

Feature 7.

Page 37: There is no 'i' in UX.

Release 6.0

Feature 5. Feature 10. Feature 4.Feature 7.

Page 38: There is no 'i' in UX.

Basic Expectations.I met with Discovery. And they’re a little freaked out by the bad press from their new Drive Challenge App.

Page 39: There is no 'i' in UX.

Basic Expectations.Problems with accuracy of maps & calculations, bugs and battery life drainer.

Page 40: There is no 'i' in UX.

UX Strategy Basic Expectations.

• Beware the death of a thousand cuts.

• Don’t ignore consistent bad feedback.• Missing a basic expectation causes extreme frustration.

• More you don’t deliver, the more it opens the door to competitors.

Page 41: There is no 'i' in UX.

The Kano Model.How to measure the investment of improving customer satisfaction.

Frustraters.

Delighters.

Investment.

Basic Expectations.

User

Satis

factio

n.

Page 42: There is no 'i' in UX.

The Kano Model.How to measure the investment of improving customer satisfaction.

Frustraters.

Delighters.

Investment.

Excitement Generators

User

Satis

factio

n.

Basic Expectations.

Page 43: There is no 'i' in UX.

Excitement Generators.

Pleasure.

Flow.

Meaning.

Dana Chisnell’s 3 Approaches to Delight.

Excitement Generators

Page 44: There is no 'i' in UX.

Designing for Pleasure.Great copy and content strategy is often key here, but sometimes you can even add pleasure with a How-To screen.

vs

Page 45: There is no 'i' in UX.

Designing for Pleasure.

Page 46: There is no 'i' in UX.

Designing for Pleasure.

Page 47: There is no 'i' in UX.

Designing for Pleasure.

Page 48: There is no 'i' in UX.

Designing for Pleasure.

Page 49: There is no 'i' in UX.

Designing for Pleasure.

Page 50: There is no 'i' in UX.

Designing for Pleasure.

Page 51: There is no 'i' in UX.

Designing for Pleasure.

Page 52: There is no 'i' in UX.

Designing for Pleasure.Apple’s built in video clip editor.

Page 53: There is no 'i' in UX.

Designing for Pleasure.Spark’s app.

Page 54: There is no 'i' in UX.

Designing for Flow.Providing clarity and reducing steps where possible. That’s right forms and check-out processes is where it hurts the most.

Page 55: There is no 'i' in UX.

Designing for Flow.

Page 56: There is no 'i' in UX.

Designing for Flow.

Page 57: There is no 'i' in UX.

Designing for Flow.

Page 58: There is no 'i' in UX.

Designing for Flow.

Page 59: There is no 'i' in UX.

Designing for Flow.

Eeeek!

Page 60: There is no 'i' in UX.

Meaning.Hands down the best, most effective and meaningful user experiences are the ones that feel invisible.

Page 61: There is no 'i' in UX.

The Kano Model.Excitement generators tend to move towards basic expectations.

Frustraters.

Delighters.

Investment.

Basic Expectations.

User

Satis

factio

n.

Excitement Generators

Page 62: There is no 'i' in UX.

A Stellar Kano Model UX Strategy.

You haven’t achieved anything by meeting a users basic expectations, however if you don’t they’re gone.

Be reluctant to just add features and keep pruning those features back to prevent feature rot.

Get to creating delightful experiences through pleasure, flow & meaning.

Remember delighters now, become basic expectations in the future.

Page 63: There is no 'i' in UX.

Cool, that doesn’t seem like rocket science, why then is UX such a contentious topic?

Page 64: There is no 'i' in UX.

The UX Iceberg.

Page 65: There is no 'i' in UX.

The UX Iceberg.

What is known.

What is assumed.

What is unkown.

Page 66: There is no 'i' in UX.

The Spectrum of UX, Chart.

Page 67: There is no 'i' in UX.

Sorry, but UX is not one person’s job.

It’s the coming together of many disciplines to solve a common problem.

Page 68: There is no 'i' in UX.

The mythological creature that is the UX Designer.

Page 69: There is no 'i' in UX.

Most of us who practice it agree on the goals of UX Design (happy users)

and even the methods we use to get there (contextual inquiries, user journey maps, wireframes, usability studies, etc).

But defining “the thing itself” continues to baffle us.

Page 70: There is no 'i' in UX.

The UX Designer Power Cards.What a UX Designer should be able to do.

Page 71: There is no 'i' in UX.

The UX Disciplines.

UI Designer

How can we expect one person to where all these hats?

Information Architect Content Strategist Developer Product Manager

Page 72: There is no 'i' in UX.

Small tight teams that have the authority to turn ideas around are by far the most successful in this iterative age.

We believe UX is still in it’s infancy and look forward to what the future holds.

Page 73: There is no 'i' in UX.

Thanks ; )