Slide 1

Slide 1 text

Iterative Design Garth Braithwaite Tuesday, July 17, 12

Slide 2

Slide 2 text

Slides speakerdeck.com/u/garthdb/ Tuesday, July 17, 12

Slide 3

Slide 3 text

Brackets brackets.io Tuesday, July 17, 12

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

What it isn't Tuesday, July 17, 12

Slide 6

Slide 6 text

What it isn't • Going dark Tuesday, July 17, 12

Slide 7

Slide 7 text

What it isn't • Going dark • Design perfectionism Tuesday, July 17, 12

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

What it isn't Tuesday, July 17, 12

Slide 11

Slide 11 text

What it isn't • Eternal Status Reports Tuesday, July 17, 12

Slide 12

Slide 12 text

What it isn't • Eternal Status Reports • Changing the color (x) times Tuesday, July 17, 12

Slide 13

Slide 13 text

What it isn't • Eternal Status Reports • Changing the color (x) times • Using the designer as a PS monkey Tuesday, July 17, 12

Slide 14

Slide 14 text

Causes Tuesday, July 17, 12

Slide 15

Slide 15 text

Causes • Designers failing to understand technical ramifications Tuesday, July 17, 12

Slide 16

Slide 16 text

Causes • Designers failing to understand technical ramifications • Developers failing to understand design Tuesday, July 17, 12

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

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

Slide 20

Slide 20 text

Cause • Individual contributors and mangers fail to be decent people. Tuesday, July 17, 12

Slide 21

Slide 21 text

Cause • We’re all jerks and we suck. Tuesday, July 17, 12

Slide 22

Slide 22 text

How to care for your designer Tuesday, July 17, 12

Slide 23

Slide 23 text

How to care for your designer and other useless generalizations Tuesday, July 17, 12

Slide 24

Slide 24 text

How to care for your designer Tuesday, July 17, 12

Slide 25

Slide 25 text

How to care for your designer Table of Contents Tuesday, July 17, 12

Slide 26

Slide 26 text

How to care for your designer Table of Contents 1.Picking your designer Tuesday, July 17, 12

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

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

Slide 29

Slide 29 text

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

Slide 30

Slide 30 text

Communication blah blah blah Tuesday, July 17, 12

Slide 31

Slide 31 text

Communication • Learn basic design concepts and terminology. Tuesday, July 17, 12

Slide 32

Slide 32 text

Communication • A good designer has a logical basis design decisions. Tuesday, July 17, 12

Slide 33

Slide 33 text

Communication • Designers need clear feedback Tuesday, July 17, 12

Slide 34

Slide 34 text

Communication Tuesday, July 17, 12

Slide 35

Slide 35 text

Communication • Examples of non-feedback Tuesday, July 17, 12

Slide 36

Slide 36 text

Communication • Examples of non-feedback • make it pop Tuesday, July 17, 12

Slide 37

Slide 37 text

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

Slide 38

Slide 38 text

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

Slide 39

Slide 39 text

Communication • Explain technical/resource limitations Tuesday, July 17, 12

Slide 40

Slide 40 text

Communication Tuesday, July 17, 12

Slide 41

Slide 41 text

Communication • Designers capable of compromise Tuesday, July 17, 12

Slide 42

Slide 42 text

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

Slide 43

Slide 43 text

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

Slide 44

Slide 44 text

Communication Tuesday, July 17, 12

Slide 45

Slide 45 text

Communication • Make the designer a part of standups Tuesday, July 17, 12

Slide 46

Slide 46 text

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

Slide 47

Slide 47 text

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

Slide 48

Slide 48 text

Best Team Ever Tuesday, July 17, 12

Slide 49

Slide 49 text

Conclusion Tuesday, July 17, 12

Slide 50

Slide 50 text

Conclusion 1.Be decent Tuesday, July 17, 12

Slide 51

Slide 51 text

Conclusion 1.Be decent 2.Befriend your designer Tuesday, July 17, 12

Slide 52

Slide 52 text

Conclusion 1.Be decent 2.Befriend your designer Iterative design will come Tuesday, July 17, 12