Developers are from Mars, Designers are from Venus - D2WC

1,948 views

Published on

It’s a session focused on the integration points in a mixed team and the challenges facing them. This is a situation that many design and development houses find themselves in today for a number of reasons. As Flash development gives way to Flex development for larger applications, the makeup of the development staff is bringing in more traditional development techniques and technology that seems foreign to designers. Likewise, Developers now just coming to the Flash platform, lured by RIA sexiness and agile techniques find themselves awash in a sea of designer hoo-ha. Leading? Kerning? Whitespace? The attention given to aesthetic in a modern app is not something one used to battleship grey apps is used to. This combination of situations, when put under pressure to deliver on time and on budget can breed animosity and destroys the teamwork mentality needed to create a superior user experience. My session is light on code, heavy on collaboration.

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,948
On SlideShare
0
From Embeds
0
Number of Embeds
39
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Developers are from Mars, Designers are from Venus - D2WC

  1. 1. Developers are from Mars, Designers are from Venus. Chad Udell D2WC – Kansas City 2010
  2. 2. Homer Simpson: We’re so different! Its like you’re from Venus! Marge Simpson: And you’re from Mars. Homer Simpson: Oh, sure, give me the one with all the monsters!
  3. 3. Not a Flash/Flex Presentation No MXML. No AS. No Catalyst.
  4. 4. A little context I’m a Designer
  5. 5. A little context I’m a Developer
  6. 6. What’s the difference? Let’s start with some generalizations.
  7. 7. What’s the difference? Developers are killjoys, squashing creativity to make a deadline or taking the easy way out to build functionality in to the application.
  8. 8. What’s the difference? Designers are fun but reckless, they create great work but aren’t concerned with the bottom line.
  9. 9. What’s the difference? A little reality, please.
  10. 10. What’s the difference? A little reality, please. While each may contain a grain of truth, both are way off.
  11. 11. We Need Both We are on a team, right?
  12. 12. We Need Both We are on a team, right? Work habits and communication styles need to be standardized to succeed.
  13. 13. Change Needed
  14. 14. Change Needed Designers need to be practical and able to move on when the goals are achieved.
  15. 15. Change Needed Designers need to be practical and able to move on when the goals are achieved. You must remember the scope of the project!
  16. 16. Change Needed
  17. 17. Change Needed Developers need to realize that design does matter.
  18. 18. Change Needed Developers need to realize that design does matter. Ideas need to be able to mature.
  19. 19. Integration Points
  20. 20. Integration Points Process, Process, Process
  21. 21. Integration Points Process, Process, Process “4D’s”
  22. 22. Integration Points Process, Process, Process “4D’s” What works for you and your company?
  23. 23. Integration Points
  24. 24. Integration Points Workflow?
  25. 25. Integration Points Workflow? Who is in on that first meeting?
  26. 26. Integration Points Workflow? Who is in on that first meeting? Which team is serving which on this project?
  27. 27. Integration Points
  28. 28. Integration Points File Organization
  29. 29. Integration Points File Organization Directory Structure is Not a Battlefield!
  30. 30. Integration Points
  31. 31. Integration Points Naming
  32. 32. Integration Points Naming “blue mockup 8 14 08.psd” or “mock_v1.psd” what will mean more when the project is complete? visualrinse.com/2007/06/12/deep-thoughts-on-file- naming-conventions/
  33. 33. Integration Points SVN=OMG!
  34. 34. Integration Points Versioning SVN=OMG!
  35. 35. Integration Points Versioning SVN? With Designers? SRSLY? SVN=OMG!
  36. 36. Integration Points Versioning SVN? With Designers? SRSLY? Version Cue is now defunkt SVN=OMG!
  37. 37. Integration Points Versioning SVN? With Designers? SRSLY? Version Cue is now defunkt SVN=OMG! GridIron Software’s “Flow” is a move in the right direction.
  38. 38. Integration Points Versioning SVN? With Designers? SRSLY? Version Cue is now defunkt SVN=OMG! GridIron Software’s “Flow” is a move in the right direction. Maybe check out “Versions” with a collaboration provider?
  39. 39. Integration Points
  40. 40. Integration Points Tickets and Issues
  41. 41. Integration Points Tickets and Issues A spreadsheet? For real?
  42. 42. Integration Points Tickets and Issues A spreadsheet? For real? At least try moving to a Google Doc
  43. 43. Integration Points Tickets and Issues A spreadsheet? For real? At least try moving to a Google Doc Even better? Basecamp or similiar
  44. 44. Integration Points Tickets and Issues A spreadsheet? For real? At least try moving to a Google Doc Even better? Basecamp or similiar Even Better-er? Assembla or similar
  45. 45. Integration Points
  46. 46. Integration Points Taxonomy
  47. 47. Integration Points Taxonomy Standardize the way you talk about things! http://edweb.sdsu.edu/courses/et650_online/
  48. 48. Integration Points Taxonomy Standardize the way you talk about things! http://edweb.sdsu.edu/courses/et650_online/ Are they wireframes or block diagrams? Mockups or Comps?
  49. 49. Integration Points Taxonomy Standardize the way you talk about things! http://edweb.sdsu.edu/courses/et650_online/ Are they wireframes or block diagrams? Mockups or Comps? Don’t get overly jargon-y or use it as a weapon. TLA dueling and art history barbs just lead to animosity.
  50. 50. Moving Forward
  51. 51. Moving Forward Development 101
  52. 52. Moving Forward Development 101 Designers, realize that pure Graphic Design will not save you!
  53. 53. Moving Forward Development 101 Designers, realize that pure Graphic Design will not save you! Change the toolset to meet development specs.
  54. 54. Moving Forward Development 101 Designers, realize that pure Graphic Design will not save you! Change the toolset to meet development specs. When things are slow, opt to take on some typically “developer” tasks.
  55. 55. Moving Forward
  56. 56. Moving Forward Design 101
  57. 57. Moving Forward Design 101 Developers, no one likes programmer art!
  58. 58. Moving Forward Design 101 Developers, no one likes programmer art! Use palettes from sites like Kuler or ColourLovers to avoid eyesores.
  59. 59. Moving Forward Design 101 Developers, no one likes programmer art! Use palettes from sites like Kuler or ColourLovers to avoid eyesores. Skins & themes for your apps are out there. Check out Scalenine.com for Flex themes. Use UI frameworks for your HTML apps.
  60. 60. Moving Forward Design 101 Developers, no one likes programmer art! Use palettes from sites like Kuler or ColourLovers to avoid eyesores. Skins & themes for your apps are out there. Check out Scalenine.com for Flex themes. Use UI frameworks for your HTML apps. Use great stencils for your wireframes, Graffletopia, Balsamiq, etc.
  61. 61. Changing Process
  62. 62. Changing Process Teamwork FTW!
  63. 63. Changing Process Teamwork FTW! Parallel Design and Development Tracks
  64. 64. Changing Process Teamwork FTW! Parallel Design and Development Tracks Rapid App Development (Blend, Catalyst)
  65. 65. Changing Process Teamwork FTW! Parallel Design and Development Tracks Rapid App Development (Blend, Catalyst) Proximity matters: Down the Hall vs Over the Wall.
  66. 66. Changing Process
  67. 67. Changing Process Tech to try
  68. 68. Changing Process Tech to try Let your designers help with XML (yes, even designing schema)
  69. 69. Changing Process Tech to try Let your designers help with XML (yes, even designing schema) Have your Devs prep some graphics and maybe even do some skin design from time to time
  70. 70. Changing Process Tech to try Let your designers help with XML (yes, even designing schema) Have your Devs prep some graphics and maybe even do some skin design from time to time Does your toolset allow for component creation? Teach your designers how they work!
  71. 71. Changing Process Tech to try Let your designers help with XML (yes, even designing schema) Have your Devs prep some graphics and maybe even do some skin design from time to time Does your toolset allow for component creation? Teach your designers how they work! Create APIs for the designers to use!
  72. 72. Changing Process
  73. 73. Changing Process Presentation and Pitching
  74. 74. Changing Process Presentation and Pitching Unified front!
  75. 75. Changing Process Presentation and Pitching Unified front! Who leads? Who follows?
  76. 76. Growing Forward
  77. 77. Growing Forward How do you keep the afterglow?
  78. 78. Growing Forward How do you keep the afterglow? Lunch and Learns
  79. 79. Growing Forward How do you keep the afterglow? Lunch and Learns Sharing “AHA”s via a team blog
  80. 80. Growing Forward
  81. 81. Growing Forward Realizing the benefits
  82. 82. Growing Forward Realizing the benefits Measuring
  83. 83. Growing Forward Realizing the benefits Measuring End of Project recaps
  84. 84. Growing Forward Realizing the benefits Measuring End of Project recaps Keeping up with trends and tech
  85. 85. Following Up visualrinse.com
  86. 86. Following Up visualrinse.com This presentation for download
  87. 87. Following Up visualrinse.com This presentation for download Twitter: visualrinse
  88. 88. Following Up visualrinse.com This presentation for download Twitter: visualrinse More posts on this topic - category: “ria”

×