Tweet
Tweet

Slide 1

Slide 1 text

Iterative Design Garth Braithwaite Wednesday, July 11, 12

Slide 2

Slide 2 text

• Designing as a product progresses • Designing in sprints • Changing design as needs change Iterative Design Wednesday, July 11, 12

Slide 3

Slide 3 text

What it isn't Wednesday, July 11, 12

Slide 4

Slide 4 text

What it isn't • Going dark Wednesday, July 11, 12

Slide 5

Slide 5 text

What it isn't • Going dark • Design perfectionism Wednesday, July 11, 12

Slide 6

Slide 6 text

What it isn't • Going dark • Design perfectionism • Icing on the poo cake Wednesday, July 11, 12

Slide 7

Slide 7 text

What it isn't • Going dark • Design perfectionism • Icing on the poo cake • Weasley House Wednesday, July 11, 12

Slide 8

Slide 8 text

Causes Wednesday, July 11, 12

Slide 9

Slide 9 text

Causes • Designers failing to understand technical ramifications Wednesday, July 11, 12

Slide 10

Slide 10 text

Causes • Designers failing to understand technical ramifications • Developers failing to understand design Wednesday, July 11, 12

Slide 11

Slide 11 text

Causes • Designers failing to understand technical ramifications • Developers failing to understand design • Too many assumptions, not enough passion Wednesday, July 11, 12

Slide 12

Slide 12 text

Causes • Designers failing to understand technical ramifications • Developers failing to understand design • Too many assumptions, not enough passion • Lack of communication Wednesday, July 11, 12

Slide 13

Slide 13 text

Causes • Designers failing to understand technical ramifications • Developers failing to understand design • Too many assumptions, not enough passion • Lack of communication Wednesday, July 11, 12

Slide 14

Slide 14 text

Cause • Individual contributors and mangers fail to be decent people. Wednesday, July 11, 12

Slide 15

Slide 15 text

Cause • We’re all jerks and we suck. Wednesday, July 11, 12

Slide 16

Slide 16 text

Interview Story Wednesday, July 11, 12

Slide 17

Slide 17 text

What's wrong with us? Wednesday, July 11, 12

Slide 18

Slide 18 text

How to care for your designer Wednesday, July 11, 12

Slide 19

Slide 19 text

How to care for your designer and other useless generalizations Wednesday, July 11, 12

Slide 20

Slide 20 text

How to care for your designer Wednesday, July 11, 12

Slide 21

Slide 21 text

How to care for your designer Table of Contents Wednesday, July 11, 12

Slide 22

Slide 22 text

How to care for your designer Table of Contents 1.Picking your designer Wednesday, July 11, 12

Slide 23

Slide 23 text

How to care for your designer Table of Contents 1.Picking your designer 2.Understanding design Wednesday, July 11, 12

Slide 24

Slide 24 text

How to care for your designer Table of Contents 1.Picking your designer 2.Understanding design 3.Communication Wednesday, July 11, 12

Slide 25

Slide 25 text

How to care for your designer Table of Contents 1.Picking your designer 2.Understanding design 3.Communication 4.Forging a relationship Wednesday, July 11, 12

Slide 26

Slide 26 text

Picking your designer Wednesday, July 11, 12

Slide 27

Slide 27 text

Picking your designer this one uses gradients Wednesday, July 11, 12

Slide 28

Slide 28 text

Picking your designer Wednesday, July 11, 12

Slide 29

Slide 29 text

Picking your designer • Engineers need to be in the interviewing process Wednesday, July 11, 12

Slide 30

Slide 30 text

Picking your designer • Engineers need to be in the interviewing process • Designers need to be able to code Wednesday, July 11, 12

Slide 31

Slide 31 text

Picking your designer • Engineers need to be in the interviewing process • Designers need to be able to code • Pick a designer you can respect Wednesday, July 11, 12

Slide 32

Slide 32 text

Picking your designer • Engineers need to be in the interviewing process • Designers need to be able to code • Pick a designer you can respect • Don't be a dick Wednesday, July 11, 12

Slide 33

Slide 33 text

Understanding your designer Wednesday, July 11, 12

Slide 34

Slide 34 text

Understanding your designer Inconceivable! Wednesday, July 11, 12

Slide 35

Slide 35 text

Understanding design Wednesday, July 11, 12

Slide 36

Slide 36 text

Understanding design • Design != pretty pictures Wednesday, July 11, 12

Slide 37

Slide 37 text

Understanding design • Design != pretty pictures • Design is a process Wednesday, July 11, 12

Slide 38

Slide 38 text

Understanding design • Design != pretty pictures • Design is a process • Design is objective Wednesday, July 11, 12

Slide 39

Slide 39 text

Understanding design • Design != pretty pictures • Design is a process • Design is objective • Design pushes limits Wednesday, July 11, 12

Slide 40

Slide 40 text

Understanding your designer Wednesday, July 11, 12

Slide 41

Slide 41 text

Understanding your designer • Their job does not look like your job. Wednesday, July 11, 12

Slide 42

Slide 42 text

Developer Wednesday, July 11, 12

Slide 43

Slide 43 text

Designer Wednesday, July 11, 12

Slide 44

Slide 44 text

Understanding your designer Wednesday, July 11, 12

Slide 45

Slide 45 text

Understanding your designer • Not all designers are equal. Wednesday, July 11, 12

Slide 46

Slide 46 text

Understanding your designer • Not all designers are equal. • Different skill sets, strengths, weaknesses Wednesday, July 11, 12

Slide 47

Slide 47 text

Understanding your designer • Not all designers are equal. • Different skill sets, strengths, weaknesses • Design school is a complex learning process Wednesday, July 11, 12

Slide 48

Slide 48 text

Understanding your designer • Not all designers are equal. • Different skill sets, strengths, weaknesses • Design school is a complex learning process • Designers are damaged goods Wednesday, July 11, 12

Slide 49

Slide 49 text

Understanding your designer • Not all designers are equal. • Different skill sets, strengths, weaknesses • Design school is a complex learning process • Designers are damaged goods • Designers != PS monkeys Wednesday, July 11, 12

Slide 50

Slide 50 text

Understanding your designer • Not all designers are equal. • Different skill sets, strengths, weaknesses • Design school is a complex learning process • Designers are damaged goods • Designers != PS monkeys • Designer != the guy who can't code Wednesday, July 11, 12

Slide 51

Slide 51 text

Wednesday, July 11, 12

Slide 52

Slide 52 text

Wednesday, July 11, 12

Slide 53

Slide 53 text

Communication blah blah blah Wednesday, July 11, 12

Slide 54

Slide 54 text

Communication • Learn basic design concepts and terminology. Wednesday, July 11, 12

Slide 55

Slide 55 text

Communication • A good designer has a logical basis design decisions. Wednesday, July 11, 12

Slide 56

Slide 56 text

Communication • Designers need clear feedback Wednesday, July 11, 12

Slide 57

Slide 57 text

Communication Wednesday, July 11, 12

Slide 58

Slide 58 text

Communication • Examples of non-feedback Wednesday, July 11, 12

Slide 59

Slide 59 text

Communication • Examples of non-feedback • make it pop Wednesday, July 11, 12

Slide 60

Slide 60 text

Communication • Examples of non-feedback • make it pop • it doesn’t seem finished Wednesday, July 11, 12

Slide 61

Slide 61 text

Communication • Examples of non-feedback • make it pop • it doesn’t seem finished • make it look more like x Wednesday, July 11, 12

Slide 62

Slide 62 text

Communication • Explain technical/resource limitations Wednesday, July 11, 12

Slide 63

Slide 63 text

Communication Wednesday, July 11, 12

Slide 64

Slide 64 text

Communication • Designers capable of compromise Wednesday, July 11, 12

Slide 65

Slide 65 text

Communication • Designers capable of compromise • Don't confuse debate with contention Wednesday, July 11, 12

Slide 66

Slide 66 text

Communication • Designers capable of compromise • Don't confuse debate with contention • Designers are trained to be criticized and to defend their decisions Wednesday, July 11, 12

Slide 67

Slide 67 text

Communication Wednesday, July 11, 12

Slide 68

Slide 68 text

Communication • Make the designer a part of standups Wednesday, July 11, 12

Slide 69

Slide 69 text

Communication • Make the designer a part of standups • Have them give status updates Wednesday, July 11, 12

Slide 70

Slide 70 text

Communication • Make the designer a part of standups • Have them give status updates • Use Dropbox - Creative Cloud Wednesday, July 11, 12

Slide 71

Slide 71 text

Forging a Relationship hug it out Wednesday, July 11, 12

Slide 72

Slide 72 text

Forging a relationship Wednesday, July 11, 12

Slide 73

Slide 73 text

Forging a relationship Wednesday, July 11, 12

Slide 74

Slide 74 text

• Higher Brain • Imagining • Self Understanding • Thinking • Control Over Emotions • Planning Forging a relationship Wednesday, July 11, 12

Slide 75

Slide 75 text

Forging a relationship Wednesday, July 11, 12

Slide 76

Slide 76 text

• Lower Brain • Basic needs • Breathing • Blinking • Anger • Fear Forging a relationship Wednesday, July 11, 12

Slide 77

Slide 77 text

Forging a relationship Wednesday, July 11, 12

Slide 78

Slide 78 text

• Amygdala • Bridge Forging a relationship Wednesday, July 11, 12

Slide 79

Slide 79 text

Forging a relationship A priority is observed, not manufactured or assigned. Otherwise, it's necessarily not a priority. Wednesday, July 11, 12

Slide 80

Slide 80 text

Forging a relationship Making something a BIG RED TOP TOP BIG HIGHEST #1 PRIORITY changes nothing but text styling. If it were really important, it'd already be done. Period. Think about it. Merlin Mann Wednesday, July 11, 12

Slide 81

Slide 81 text

Forging a relationship • Bring them in early and often • Define roles • Who is the ultimate decision maker? • What is the end goal of the designer? • Explain roadmap Wednesday, July 11, 12

Slide 82

Slide 82 text

Forging a relationship • One of the guys Wednesday, July 11, 12

Slide 83

Slide 83 text

Best Team Ever Wednesday, July 11, 12

Slide 84

Slide 84 text

Conclusion Wednesday, July 11, 12

Slide 85

Slide 85 text

Conclusion 1.Be decent Wednesday, July 11, 12

Slide 86

Slide 86 text

Conclusion 1.Be decent 2.Be friend your designer Wednesday, July 11, 12

Slide 87

Slide 87 text

Conclusion 1.Be decent 2.Be friend your designer Iterative design will come Wednesday, July 11, 12