Designers and developers are so different that sometimes it's almost like we're speaking different languages. What can we as designers to to help bridge these communication gaps to allow for smoother web projects? Presented at WordCamp NYC 2012.

1. Alas, No Mind Meld:
Designer-Developer
Communication for a
Harmonious Future
@melchoyce choycedesign.com

2. Not a developer
Not you

3. Step One:
Become an easier
designer to work with.

4. Be Consistent.
Become an easier designer to work with

5. Be Consistent.
Use consistent typefaces
and font sizing.
Become an easier designer to work with

6. Be Consistent.
Use consistent colors.
Become an easier designer to work with

7. Be Consistent.
Use consistent spacing.
Become an easier designer to work with

8. Be Consistent.
Use consistent column
widths.
Become an easier designer to work with

9. Be Consistent.
Style elements consistently.
Become an easier designer to work with

10. Be Clean.
Become an easier designer to work with

11. Be Clean.
Logically organize your
source files.
Become an easier designer to work with

12. Be Clean.
Name your layers.
This is bad
This is good
Become an easier designer to work with

13. Be Clean.
Group related layers.
This is bad
This is good
Become an easier designer to work with

14. Be Clean.
Delete unused layers.
What is this?!
Become an easier designer to work with

15. Be Clean.
Use whole pixel values.
Bad
Become an easier designer to work with

16. Be Clean.
Name your source files
appropriately.
Become an easier designer to work with

17. Be Knowledgeable.
Become an easier designer to work with

18. Be Knowledgeable.
Learn how to code...
just a little.
Become an easier designer to work with

19. Be Knowledgeable.
Learn how to user
developer tools.
Become an easier designer to work with

20. Be Knowledgeable.
Learn about browser
compatibility.
http://browsehappy.com/
Become an easier designer to work with

21. Be Knowledgeable.
Learn the right buzzwords.
Become an easier designer to work with

22. Be Knowledgeable.
Get to know WordPress
(or whatever you’re using).
Protip: Have your developer insall the Theme
Unit Test on your dev site
(http://codex.wordpress.org/Theme_Unit_Test)
Become an easier designer to work with

23. Remember:
Even if you are
knowledgeable, your
developer is the expert on
development. Not you.
Become an easier designer to work with

24. Step Two:
Work on your
communication skills.

25. When should you
involve a developer in
your design process?
Work on your communication skills

26. Immediately.
Work on your communication skills

27. ...Or a least before you
show any designs to
your client.
Work on your communication skills

28. What’s their process?
Go over your developer’s
process and how you fit
into it.
Work on your communication skills

29. What’s your process?
Go over your process and
how you would like it to
work with your developer’s.
Work on your communication skills

30. What about giving
your developer
feedback?
Establish a protocol for
doing check-ins and reviews.
Work on your communication skills

31. Giving Handoffs.
Double-check your
source files.
Work on your communication skills

32. Giving Handoffs.
Try to give handoffs in
person, if possible. If not,
try video, then phone.
Work on your communication skills

33. Giving Handoffs.
Walk your developer
through your psds.
Work on your communication skills

34. Giving Handoffs.
Go over interactions.
Work on your communication skills

35. Giving Handoffs.
Include relevant assets.
Work on your communication skills

36. Watch this.
http://www.geekwire.com/
2011/comedydevelopers-
designers-communicate/
It’s funny.
Work on your communication skills

38. Thanks.
Any questions?
@melchoyce choycedesign.com