Working with Developers for Fun and Profit

I gave this talk for IxDA Grand Rapids on 5/22/14.

Transcript

1. Working with Developers For Fun & Profit Jack Moffett | @jackmoffett Senior Interaction Designer Inmedius, a Boeing Company designaday.tumblr.com
3. “The way we work at Apple is that the complexity of these products really makes it critical to work collaboratively, with different areas of expertise. I think that’s one of the things about my job I enjoy the most. I work with silicon designers, electronic and mechanical engineers, and I think you would struggle to determine who does what when we get together. We’re located together, we share the same goal, have exactly the same preoccupation with making great products.” ! Sir Jonathan Ive
4. Tight Integration the board is misleading by snickclunk http://www.flickr.com/photos/snickclunk/4119284398/in/photostream/
5. Bridges to Development
6. Bridges to Development Relationships (the soft skills)
7. Bridges to Development Relationships (the soft skills) Supporting Development
8. Bridges to Development Relationships (the soft skills) Supporting Development Documentation
9. Bridges to Development Relationships (the soft skills) Supporting Development Documentation Comprehensive Participation
10. Bridges to Development Relationships (the soft skills) Supporting Development Documentation Comprehensive Participation Shared Tools
11. Bridges to Development Relationships (the soft skills) Supporting Development Documentation Comprehensive Participation Shared Tools Implementing the UI
12. Relationships
13. Who We Work With
15. DO Not Tug Of War by Tom Blackwell https://flic.kr/p/6pjYgc
16. DO Not Critique engineering prototypes on aesthetics or usability. Tug Of War by Tom Blackwell https://flic.kr/p/6pjYgc
17. DO Not Critique engineering prototypes on aesthetics or usability. Expect developers to have the same design sensibilities you have. Tug Of War by Tom Blackwell https://flic.kr/p/6pjYgc
18. DO Not Critique engineering prototypes on aesthetics or usability. Expect developers to have the same design sensibilities you have. Force your process on the developers. Tug Of War by Tom Blackwell https://flic.kr/p/6pjYgc
19. DO Not Critique engineering prototypes on aesthetics or usability. Expect developers to have the same design sensibilities you have. Force your process on the developers. Expect developers to make last-minute changes just because you haven’t been involved until late in the process. Tug Of War by Tom Blackwell https://flic.kr/p/6pjYgc
20. Yes Please Green Ants by Kasi Metcalfe https://www.flickr.com/photos/kasimetcalfe/339113868
21. Yes Please Position your involvement as something that makes your developers’ jobs easier. Green Ants by Kasi Metcalfe https://www.flickr.com/photos/kasimetcalfe/339113868
22. Yes Please Position your involvement as something that makes your developers’ jobs easier. Be inclusive. It’s not our responsibility to make decisions so much as to offer options. Green Ants by Kasi Metcalfe https://www.flickr.com/photos/kasimetcalfe/339113868
23. Yes Please Position your involvement as something that makes your developers’ jobs easier. Be inclusive. It’s not our responsibility to make decisions so much as to offer options. Dare to compromise. Green Ants by Kasi Metcalfe https://www.flickr.com/photos/kasimetcalfe/339113868
24. Yes Please Position your involvement as something that makes your developers’ jobs easier. Be inclusive. It’s not our responsibility to make decisions so much as to offer options. Dare to compromise. Find opportunities to educate. Green Ants by Kasi Metcalfe https://www.flickr.com/photos/kasimetcalfe/339113868
25. Yes Please Position your involvement as something that makes your developers’ jobs easier. Be inclusive. It’s not our responsibility to make decisions so much as to offer options. Dare to compromise. Find opportunities to educate. Be social. Green Ants by Kasi Metcalfe https://www.flickr.com/photos/kasimetcalfe/339113868
26. Relationships
27. “Have a beer with your engineer. You can accelerate trust and communication if someone feels you care about them as a person—and not just a set of skills that you rely on to realize a design vision.” Jenna Bilotta – How Designers and Engineers Can Play Nice (and Still Run with Scissors)
28. Collaboration life cycle 65: Wellbeck College Mens Novice 8+ by Steve Selwood https://www.flickr.com/photos/8507625@N02/11122136456
29. Collaboration life cycle Requirements Analysis Design Implementation Functional Testing Usability Testing 65: Wellbeck College Mens Novice 8+ by Steve Selwood https://www.flickr.com/photos/8507625@N02/11122136456
30. Collaboration life cycle Requirements Analysis Design Implementation Functional Testing Usability Testing 65: Wellbeck College Mens Novice 8+ by Steve Selwood https://www.flickr.com/photos/8507625@N02/11122136456
31. Requirements
32. Develop a shared understanding of the requirements Pre-game huddle by -just-jen- http://www.flickr.com/photos/whetzel/55214389/
33. Develop a shared understanding of the requirements Pre-game huddle by -just-jen- http://www.flickr.com/photos/whetzel/55214389/
34. “We’ve got to find a way to make this... fit into the hole for this... using nothing but that.” Identify technical challenges
35. Identify technologies The cup that can only be half-full. by vrogy http://www.flickr.com/photos/vrogy/511644410/
36. Identify technologies The cup that can only be half-full. by vrogy http://www.flickr.com/photos/vrogy/511644410/
37. Estimate Time & Effort “Ideally, the developers and I are to work closely together during the design phase... but it typically works out that they gloss over the document or attend a few meetings and get a basic understanding of what we are planning on doing, but never pay attention to the full details. Then they tend to come to me with questions or ‘are you crazy? I can’t do that!’ when it’s time for them to put together a timeline for their development assessment. After a few times of close calls, they are beginning to pay more attention to the pencil sketches and overall workflows we put together for them.” By eflon http://www.flickr.com/photos/eflon/5079163335/
38. Estimate Time & Effort
39. Estimate Time & Effort
40. Estimate Time & Effort
41. software bill of materials Estimate Time & Effort
42. How can we best prioritize our work to support the developers’ schedule? Estimate Time & Effort
43. A successful tool is one that was used to do something undreamed of by its author. by katerha http://www.flickr.com/photos/katerha/5746905652/ Use their tools
44. Issue Tracking
45. Issue Tracking Create items for each of your design tasks. Developers can subscribe to the ones that relate to their own tasks. Your estimates can be calculated in the burndown chart, or not.
46. Issue Tracking
47. Design
48. Design Documentation One size fits all…. By The Candid Street http://www.flickr.com/photos/haddadi/5971508861/
49. Design Documentation One size fits all…. By The Candid Street http://www.flickr.com/photos/haddadi/5971508861/
50. Design Documentation One size fits all…. By The Candid Street http://www.flickr.com/photos/haddadi/5971508861/
51. Design Documentation
52. Design Documentation Design the documentation for those that will wear it.
53. Design Documentation
54. Design Documentation Design documentation to be a reference tool. Always reference the requirements. Be concise and explicit in your explanation. Label screens effectively. Be thorough. Be consistent.
55. For the Client
56. For the Developers
57. For the Developers
59. Bill Scott “The developers really appreciated it, because they could just look at it, and they didn’t have to wonder if the designer had forgotten something.”
60. Documentation is part of the design process.
61. Documentation is part of the design process. You learn a lot by describing your design.
62. Questions? Roberto Clemente Bridge in Pittsburgh by Brook Ward https://flic.kr/p/dAWcYQ Jack Moffett | @jackmoffett Senior Interaction Designer Inmedius, a Boeing Company jackmoffett@mac.com designaday.tumblr.com
63. 1. State of the Industry 2. Looking for Group 3. Collaboration Life Cycle 4. Why HTML and CSS? 5. Tooling Up 6. Formatting Standards 7. OOCSS 8. Owning Behavior 9. Looking Toward the Horizon Chapter
64. Available for pre-order: ! store.elsevier.com amazon.com barnesandnoble.com ! In stores mid-August.
65. Thank You! Jack Moffett | @jackmoffett Senior Interaction Designer Inmedius, a Boeing Company jackmoffett@mac.com designaday.tumblr.com