8 Responses

  1. response to why devs hate designers
    response to why devs hate designers at |

    […] response to this post on a friend/colleague’s blog got really long-winded, so I’m using it as an opportunity […]

  2. Reason why your develop hates you #7 | Elisabeth Hubert

    […] your developer hates you: 1. Your requirements are unclear and incomplete and yet you expect a concrete answer to your question. 2. You bring us to the playing field after the game is over. 3. You don’t really know what I do […]

  3. Reason why your developer hates you #5 | Elisabeth Hubert

    […] » A few weeks ago I started a series on Reasons Why Your Developer Hates You. Check out the first post and others to get some ideas on the reasons I’ve brought up. Today is reason #5 why your […]

  4. Reasons why your developer hates you: #3 | Elisabeth Hubert

    […] UX Designers see where the tension begins between them and their development team. You can read the first and second posts here, and remember if you have suggestions, ideas, other reasons why you think […]

  5. Reasons why your developer hates you: #2 | Elisabeth Hubert

    […] and user experience designers (Note: sometimes these roles overlap). Here, you can read my first post and also a great response from Lee Fastenau an amazing designer/developer/genius over at Frog […]

  6. Lee
    Lee at |
  7. Gabi Moore
    Gabi Moore at |

    I find that sometimes just saying you’re available for questions is not enough. You have to actually be a little pushy, and write or call every few days or weeks to see how things are going. That’s very tricky because you may come across as really annoying. But if you can manage to keep in touch and see their work as it progresses I think it’s the best way to try to avoid the gap between design and implementation.

  8. Adam Lerner
    Adam Lerner at |

    I couldn’t agree with you more about the communications thing. Not only should we, as UX designers, be available for questions, we should do our best to ensure that our relationships are not unintentionally adversarial. The best environments I’ve worked in are ones in which UX design and development are a team — if not officially on the org chart — than in the day-to-day cycle of work. In those environments I’m not sending requirements off — I’m drafting them and responding to feedback about the technical feasibility of the user interactions I’m proposing. Lather-rinse-repeat.

    Strange how frequently teamwork is sabotaged in ways both mundane and subtle in most workplaces.


Leave a Reply

fifteen + 18 =