getting good ux into mobile

1

@shoobe01#mtc2014

Getting Good UX Into MobileA few tools & techniques we can all use@shoobe01#mtc2014

2

@shoobe01#mtc2014

Prototype for success!

3

@shoobe01#mtc2014

Photoshop!

4

@shoobe01#mtc2014

4

@shoobe01#mtc2014

5

@shoobe01#mtc2014

Okay, you go find me an ecosystem developer.

6

@shoobe01#mtc2014

Tools to design experiences:

7

@shoobe01#mtc2014

First: don’t draw.

8

@shoobe01#mtc2014

Define, then design.

9

@shoobe01#mtc2014

KJ (Post-It®) Process:

• Determine focus questions• Get everyone in a room• Answer questions• Put up answers• Group answers, label groups• Vote on most important groups

10

@shoobe01#mtc2014

10

@shoobe01#mtc2014

11

@shoobe01#mtc2014@shoobe01#mtc2014

12

@shoobe01#mtc2014@shoobe01#mtc2014

13

@shoobe01#mtc2014

Model your ecosystem.

14

@shoobe01#mtc2014

15

@shoobe01#mtc2014

15

@shoobe01#mtc2014

16

@shoobe01#mtc2014

17

@shoobe01#mtc2014

18

@shoobe01#mtc2014

Design and review at device scale.

19

@shoobe01#mtc2014

19

@shoobe01#mtc2014

20

@shoobe01#mtc2014

20

@shoobe01#mtc2014

21

@shoobe01#mtc2014

Thing

21

@shoobe01#mtc2014

22

@shoobe01#mtc2014

Don’t just draw, specify.

23

@shoobe01#mtc2014

23

@shoobe01#mtc2014

24

@shoobe01#mtc2014

Embrace failure and complexity.

25

@shoobe01#mtc2014

Resilient, not brittle.

26

@shoobe01#mtc2014

27

@shoobe01#mtc2014

28

@shoobe01#mtc2014

Systems are fault-intolerant.

29

@shoobe01#mtc2014

Users are fault-intolerant.

30

@shoobe01#mtc2014

“Error is viewed, therefore, not as an extraneous and misdirected or misdirecting accident, but as an essential part of the process under consideration.”

– John VonNeuman

31

@shoobe01#mtc2014

Accounting for tolerances.

32

@shoobe01#mtc2014

PHOTO. REG CODES ON CEREAL BOXES.

3232

@shoobe01#mtc2014

33

@shoobe01#mtc2014

Design for imperfection.

34

@shoobe01#mtc2014

• Define, then design.

• Design ecosystems, not websites or apps.

• Don’t just draw: specify.

• Design at device scale.

• Embrace failure and complexity.

35

@shoobe01#mtc2014

And, ask for help.

36

@shoobe01#mtc2014

Contact me for consulting, design, to

follow up on this deck, or just to talk:

Steven Hoober

steven@4ourth.com

+1 816 210 045

@shoobe01

shoobe01 on:

www.4ourth.com