Iterative Design

In this presentation I went through how engineers can better utilize their designers in an iterative process.

Transcript

1. Iterative Design Garth Braithwaite Wednesday, July 11, 12
2. • Designing as a product progresses • Designing in sprints • Changing design as needs change Iterative Design Wednesday, July 11, 12
3. What it isn't Wednesday, July 11, 12
4. What it isn't • Going dark Wednesday, July 11, 12
5. What it isn't • Going dark • Design perfectionism Wednesday, July 11, 12
6. What it isn't • Going dark • Design perfectionism • Icing on the poo cake Wednesday, July 11, 12
7. What it isn't • Going dark • Design perfectionism • Icing on the poo cake • Weasley House Wednesday, July 11, 12
8. Causes Wednesday, July 11, 12
9. Causes • Designers failing to understand technical ramifications Wednesday, July 11, 12
10. Causes • Designers failing to understand technical ramifications • Developers failing to understand design Wednesday, July 11, 12
11. Causes • Designers failing to understand technical ramifications • Developers failing to understand design • Too many assumptions, not enough passion Wednesday, July 11, 12
12. 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
13. 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
14. Cause • Individual contributors and mangers fail to be decent people. Wednesday, July 11, 12
15. Cause • We’re all jerks and we suck. Wednesday, July 11, 12
16. Interview Story Wednesday, July 11, 12
17. What's wrong with us? Wednesday, July 11, 12
18. How to care for your designer Wednesday, July 11, 12
19. How to care for your designer and other useless generalizations Wednesday, July 11, 12
20. How to care for your designer Wednesday, July 11, 12
21. How to care for your designer Table of Contents Wednesday, July 11, 12
22. How to care for your designer Table of Contents 1.Picking your designer Wednesday, July 11, 12
23. How to care for your designer Table of Contents 1.Picking your designer 2.Understanding design Wednesday, July 11, 12
24. How to care for your designer Table of Contents 1.Picking your designer 2.Understanding design 3.Communication Wednesday, July 11, 12
25. 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
26. Picking your designer Wednesday, July 11, 12
27. Picking your designer this one uses gradients Wednesday, July 11, 12
28. Picking your designer Wednesday, July 11, 12
29. Picking your designer • Engineers need to be in the interviewing process Wednesday, July 11, 12
30. Picking your designer • Engineers need to be in the interviewing process • Designers need to be able to code Wednesday, July 11, 12
31. 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
32. 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
33. Understanding your designer Wednesday, July 11, 12
34. Understanding your designer Inconceivable! Wednesday, July 11, 12
35. Understanding design Wednesday, July 11, 12
36. Understanding design • Design != pretty pictures Wednesday, July 11, 12
37. Understanding design • Design != pretty pictures • Design is a process Wednesday, July 11, 12
38. Understanding design • Design != pretty pictures • Design is a process • Design is objective Wednesday, July 11, 12
39. Understanding design • Design != pretty pictures • Design is a process • Design is objective • Design pushes limits Wednesday, July 11, 12
40. Understanding your designer Wednesday, July 11, 12
41. Understanding your designer • Their job does not look like your job. Wednesday, July 11, 12
42. Developer Wednesday, July 11, 12
43. Designer Wednesday, July 11, 12
44. Understanding your designer Wednesday, July 11, 12
45. Understanding your designer • Not all designers are equal. Wednesday, July 11, 12
46. Understanding your designer • Not all designers are equal. • Different skill sets, strengths, weaknesses Wednesday, July 11, 12
47. Understanding your designer • Not all designers are equal. • Different skill sets, strengths, weaknesses • Design school is a complex learning process Wednesday, July 11, 12
48. 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
49. 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
50. 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
51. Wednesday, July 11, 12
52. Wednesday, July 11, 12
53. Communication blah blah blah Wednesday, July 11, 12
54. Communication • Learn basic design concepts and terminology. Wednesday, July 11, 12
55. Communication • A good designer has a logical basis design decisions. Wednesday, July 11, 12
56. Communication • Designers need clear feedback Wednesday, July 11, 12
57. Communication Wednesday, July 11, 12
58. Communication • Examples of non-feedback Wednesday, July 11, 12
59. Communication • Examples of non-feedback • make it pop Wednesday, July 11, 12
60. Communication • Examples of non-feedback • make it pop • it doesn’t seem finished Wednesday, July 11, 12
61. Communication • Examples of non-feedback • make it pop • it doesn’t seem finished • make it look more like x Wednesday, July 11, 12
62. Communication • Explain technical/resource limitations Wednesday, July 11, 12
63. Communication Wednesday, July 11, 12
64. Communication • Designers capable of compromise Wednesday, July 11, 12
65. Communication • Designers capable of compromise • Don't confuse debate with contention Wednesday, July 11, 12
66. 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
67. Communication Wednesday, July 11, 12
68. Communication • Make the designer a part of standups Wednesday, July 11, 12
69. Communication • Make the designer a part of standups • Have them give status updates Wednesday, July 11, 12
70. Communication • Make the designer a part of standups • Have them give status updates • Use Dropbox - Creative Cloud Wednesday, July 11, 12
71. Forging a Relationship hug it out Wednesday, July 11, 12
72. Forging a relationship Wednesday, July 11, 12
73. Forging a relationship Wednesday, July 11, 12
74. • Higher Brain • Imagining • Self Understanding • Thinking • Control Over Emotions • Planning Forging a relationship Wednesday, July 11, 12
75. Forging a relationship Wednesday, July 11, 12
76. • Lower Brain • Basic needs • Breathing • Blinking • Anger • Fear Forging a relationship Wednesday, July 11, 12
77. Forging a relationship Wednesday, July 11, 12
78. • Amygdala • Bridge Forging a relationship Wednesday, July 11, 12
79. Forging a relationship A priority is observed, not manufactured or assigned. Otherwise, it's necessarily not a priority. Wednesday, July 11, 12
80. 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
81. 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
82. Forging a relationship • One of the guys Wednesday, July 11, 12
83. Best Team Ever Wednesday, July 11, 12
84. Conclusion Wednesday, July 11, 12
85. Conclusion 1.Be decent Wednesday, July 11, 12
86. Conclusion 1.Be decent 2.Be friend your designer Wednesday, July 11, 12
87. Conclusion 1.Be decent 2.Be friend your designer Iterative design will come Wednesday, July 11, 12