Iterative Design (LV Startup Weekend)

A shortened version of my Iterative Design presentation aimed at the startup weekend type of design.

Transcript

1. Iterative Design Garth Braithwaite Tuesday, July 17, 12
2. Slides speakerdeck.com/u/garthdb/ Tuesday, July 17, 12
3. Brackets brackets.io Tuesday, July 17, 12
4. • Designing as a product progresses • Designing in sprints • Changing design as needs change Iterative Design Tuesday, July 17, 12
5. What it isn't Tuesday, July 17, 12
6. What it isn't • Going dark Tuesday, July 17, 12
7. What it isn't • Going dark • Design perfectionism Tuesday, July 17, 12
8. What it isn't • Going dark • Design perfectionism • Icing on the poo cake Tuesday, July 17, 12
9. What it isn't • Going dark • Design perfectionism • Icing on the poo cake • Weasley House Tuesday, July 17, 12
10. What it isn't Tuesday, July 17, 12
11. What it isn't • Eternal Status Reports Tuesday, July 17, 12
12. What it isn't • Eternal Status Reports • Changing the color (x) times Tuesday, July 17, 12
13. What it isn't • Eternal Status Reports • Changing the color (x) times • Using the designer as a PS monkey Tuesday, July 17, 12
14. Causes Tuesday, July 17, 12
15. Causes • Designers failing to understand technical ramifications Tuesday, July 17, 12
16. Causes • Designers failing to understand technical ramifications • Developers failing to understand design Tuesday, July 17, 12
17. Causes • Designers failing to understand technical ramifications • Developers failing to understand design • Too many assumptions, not enough passion Tuesday, July 17, 12
18. 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
19. 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
20. Cause • Individual contributors and mangers fail to be decent people. Tuesday, July 17, 12
21. Cause • We’re all jerks and we suck. Tuesday, July 17, 12
22. How to care for your designer Tuesday, July 17, 12
23. How to care for your designer and other useless generalizations Tuesday, July 17, 12
24. How to care for your designer Tuesday, July 17, 12
25. How to care for your designer Table of Contents Tuesday, July 17, 12
26. How to care for your designer Table of Contents 1.Picking your designer Tuesday, July 17, 12
27. How to care for your designer Table of Contents 1.Picking your designer 2.Understanding design Tuesday, July 17, 12
28. How to care for your designer Table of Contents 1.Picking your designer 2.Understanding design 3.Communication Tuesday, July 17, 12
29. 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
30. Communication blah blah blah Tuesday, July 17, 12
31. Communication • Learn basic design concepts and terminology. Tuesday, July 17, 12
32. Communication • A good designer has a logical basis design decisions. Tuesday, July 17, 12
33. Communication • Designers need clear feedback Tuesday, July 17, 12
34. Communication Tuesday, July 17, 12
35. Communication • Examples of non-feedback Tuesday, July 17, 12
36. Communication • Examples of non-feedback • make it pop Tuesday, July 17, 12
37. Communication • Examples of non-feedback • make it pop • it doesn’t seem finished Tuesday, July 17, 12
38. Communication • Examples of non-feedback • make it pop • it doesn’t seem finished • make it look more like x Tuesday, July 17, 12
39. Communication • Explain technical/resource limitations Tuesday, July 17, 12
40. Communication Tuesday, July 17, 12
41. Communication • Designers capable of compromise Tuesday, July 17, 12
42. Communication • Designers capable of compromise • Don't confuse debate with contention Tuesday, July 17, 12
43. 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
44. Communication Tuesday, July 17, 12
45. Communication • Make the designer a part of standups Tuesday, July 17, 12
46. Communication • Make the designer a part of standups • Have them give status updates Tuesday, July 17, 12
47. Communication • Make the designer a part of standups • Have them give status updates • Use Dropbox - Creative Cloud Tuesday, July 17, 12
48. Best Team Ever Tuesday, July 17, 12
49. Conclusion Tuesday, July 17, 12
50. Conclusion 1.Be decent Tuesday, July 17, 12
51. Conclusion 1.Be decent 2.Befriend your designer Tuesday, July 17, 12
52. Conclusion 1.Be decent 2.Befriend your designer Iterative design will come Tuesday, July 17, 12