Upgrade to Pro — share decks privately, control downloads, hide ads and more …

7 Successful Habits of Designers & Developers Who Actually Like Each Other

cassiemc
October 26, 2014

7 Successful Habits of Designers & Developers Who Actually Like Each Other

Delivered at HOW Interactive Design conference in Chicago / October 21, 2014
____

Designer and developer skill sets are complimentary, but often the personalities are not. In this highly practical session, you’ll discover opportunities for increased productivity, strategies for creating more harmonious teams, and collaborative habits that produce stellar work.

Whether you are a manager, team lead, developer or designer, getting two stubborn characters to play nice is an exercise in walking on eggshells. This session will take a look at the intricacies of these working relationships.

3 Main Takeaways:
• Learn the best workflows for designer / developer cooperation.
• Find out how to develop work habits that will allow you to get the job done, even if you can't stand your colleagues.
• Get tips for a happy “marriage” between a designer and a developer.

cassiemc

October 26, 2014
Tweet

More Decks by cassiemc

Other Decks in Design

Transcript

  1. @cassiemc cassiemcdaniel.com
    7
    Successful Habits
    of Designers & Developers
    Who Actually Like Each Other

    View Slide

  2. yamith head

    View Slide

  3. glenn jones

    View Slide

  4. webydo

    View Slide

  5. designer
    developer
    coders-survey.com, 2012
    what are you?
    11%
    38%
    50%
    both designer
    & developer

    View Slide

  6. Hybrids, who have one foot in each
    discipline, beg the question of whether
    we need to get along better or simply
    become more like each other.


    bit.ly/twocatsinasack

    View Slide

  7. tomek ducki

    View Slide

  8. design dev
    10
    1

    View Slide

  9. design dev
    10
    1
    4 6

    View Slide

  10. design dev
    professional
    amateur
    html / css
    javascript
    node.js
    ui
    typography
    ux

    View Slide

  11. teams
    skip hursh

    View Slide

  12. working
    hiring
    shipping

    View Slide

  13. ? ?
    ?
    ?
    ??
    ?

    View Slide

  14. 1. work transparently

    View Slide

  15. startup
    ad agency
    6 employees
    freelance
    just me
    tech company
    100s of employees
    boutique agency
    30 employees
    healthcare
    15-100 employees
    50 employees

    View Slide

  16. Transparency is a really good way to make
    people understand what kind and how much
    work a group is doing.


    – bobby richter

    View Slide

  17. View Slide

  18. bug tracker
    2 week sprints
    wiki
    irc
    vidyo
    etherpad
    email
    closed meetings

    View Slide

  19. View Slide

  20. View Slide

  21. View Slide

  22. air.mozilla.org/channels/webmaker

    View Slide

  23. View Slide

  24. 2. find the same page

    View Slide

  25. everyone accounted for

    View Slide

  26. audience problem success

    View Slide

  27. audience

    View Slide

  28. brief

    View Slide

  29. View Slide

  30. View Slide

  31. View Slide

  32. ask questions

    View Slide

  33. Groups of people that are naturally inclined to
    share & respect each other usually just have a
    common goal that's too looming and important
    to not use everybody's skill.


    – bobby richter

    View Slide

  34. 3. clear the way

    View Slide

  35. View Slide

  36. demolish roadblocks

    View Slide

  37. document the scope of work

    View Slide

  38. sprintr

    View Slide

  39. 4. share your screen

    View Slide

  40. pair-programming

    View Slide

  41. nearsoft inc

    View Slide

  42. I think the biggest key to good designer-
    developer relationships is that the people
    involved view each other as creative partners
    rather than resources to hand-off work to.


    – atul varma

    View Slide

  43. View Slide

  44. pair-designing
    pair-programming

    View Slide

  45. pair-creating

    View Slide

  46. View Slide

  47. 5. reviews

    View Slide

  48. it is impossible to ignore
    the reviewer when he or she
    is sitting right next to you.


    View Slide

  49. View Slide

  50. ILLUSTRATION: KEVIN CORNELL

    View Slide

  51. design review

    View Slide

  52. redpen.io

    View Slide

  53. View Slide

  54. View Slide

  55. 6. always be mentoring

    View Slide

  56. View Slide

  57. View Slide

  58. students don't know where to ask (irc, bug, email, ???)
    and if they try the one thing they know how to do and it
    fails, they can give up. Pay attention to new people on
    all your channels.
    do your reviews fast; prioritize contributor reviews.
    draw them out on irc, comment on their blogs, check
    in on bug comments. Quiet means you're losing them.
    reassure them that they're doing OK, tell them not to
    give up, be encouraging. make it okay for non-experts
    to be here. be [extra] friendly.
    file bugs with lots of details you're not filing a bug
    for colleagues. give more context.
    blog, tweet, or otherwise recognize their work/presence

    View Slide

  59. I feel the role of UX is
    always downplayed.


    – nadine lessio
    There's a common
    misperception that devs
    are not creative.
    – simon lindsay

    View Slide

  60. View Slide

  61. 7. perfect the handoff

    View Slide

  62. sean inman

    View Slide

  63. View Slide

  64. View Slide

  65. T H E D
    E N
    tomek ducki

    View Slide

  66. @cassiemc
    [email protected]
    thank you!

    View Slide