Transcript
Page 1: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

1

The Trouble With All Those BoxesDesigning for ecosystems and people instead of screens and pages

@shoobe01 #mLearnCon

Page 2: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

2

Page 3: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

3

Page 4: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

4

Page 5: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

55

Page 6: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

66

Page 7: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

7

Page 8: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

8

“I'm as interested in "channels" as a thing when designing ecosystems as I am in pages when reading a book.”

– Andrea Resmini

@resmini

Page 9: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

99

Page 10: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

10

Page 11: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

11

Page 12: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

12

Page 13: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

13

“What we’re doing is trying to translocate information, and all the machine does is impair that process. Possibly infinitely. You have a choice over where it goes, and that’s it.”

– Martin Geddes

@hypervoice

Page 14: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

1414

Page 15: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

1515

Page 16: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

16

Page 17: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

1717

Page 18: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

1818

Page 19: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

19

• Design for Every Screen

• Mobile is More

• Design for Failure

Page 20: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

20

• Design for Every Screen

• Mobile is More

• Design for Failure

Page 21: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

21

Mobile First?

Page 22: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

22

Page 23: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

23

Page 24: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

2424

Page 25: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

25

Page 26: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

26

Page 27: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

27

Page 28: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

28

Page 29: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

29

Page 30: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

30

Design for Every Screen

Blueprint

• Goals, objectives of the business • Legacy systems, business constraints• Put users on the paper• Task flow/Storyboard/ID/IA/…

Concept• Platform agonstic < - > Every

platform

Page 31: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

31

• Design for Every Screen

• Mobile is More

• Design for Failure

Page 32: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

3232

Page 33: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

33

Wrong

Page 34: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

3434

Page 35: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

35

“…inequality is where the opportunities/challenges for design really are.”

– Andrea Resmini

@resmini

Page 36: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

36

Every platform is a unique and special snowflake.

Page 37: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

37

Page 38: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

3838

Page 39: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

3939

Page 40: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

40

Page 41: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

41

Mobile is More

Branch Design to Platforms

• Pick your platforms • Mark/strike interactions for each

platform• Design by widget/module• Embrace polymorphism• Design for re-use

Page 42: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

42

• Design for Every Screen

• Mobile is More

• Design for Failure

Page 43: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

4343

Page 44: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

44

Page 45: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

45

“when these subsystems are combined into larger systems, we enter the world of non-linear dynamics, complex interactions, chaotic behavior — and often, disastrous non-resilience...”

– Michael Mehaffy

tectics.com

Page 46: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

46

Page 47: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

47

Page 48: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

4848

Page 49: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

49

Page 50: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

50

Page 51: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

5151

Page 52: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

52

Resilience Design Method:

1. Evaluate by widget

2. Determine user tolerance

3. Rate by severity

Page 53: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

53

Design for Failure

Evaluate, avoid, fix

• Evaluate each component for pitfalls• Detrmine user tolerance• Rate severity, risk• Can you avoid the issue? • Can you mitigate the issue?

Page 54: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

54

Philosophy, Not Process

Page 55: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

55

Contact me for consulting, design, to

follow up on this deck, or just to talk:

Steven Hoober

[email protected]

+1 816 210 045

@shoobe01

shoobe01 on:

www.4ourth.com

Page 56: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

56

Page 57: The Trouble with All Those Boxes: Designing for Ecosystems Instead of Screens

57

Every platform is fragmented


Recommended