As a UX professional, it is inevitable that you will work closely with software developers in your career. You might also have coding skills, but this is about how you relate with developers while in a UX role. A talented developer I have worked with before called me up some days ago and told me how he was applying UX skills and practices that he had learnt from me at his new job and role as a development manager. Highlight of my week.
I have come across three main types of developers in my experience and the way I’ve learnt to relate/work with them differs.
The ‘code-alone’ type of developer is one who just wants to get on with their work. Sometimes they say things like “I am not sketching anything, it’s not my job” or “Just tell me what to do” At first when I encountered this, I was taken aback, all they wanted to see was wireframes and didn’t care about the ideas or concepts behind the wireframes.
I learnt that it is best to leave them be, respect the work they do. It is likely that by the work you do, they will come on their own to ask questions. Don’t count on it though, supply them with as much information as possible (Annotate wireframes properly and in detail!) and let them get on with their work.
These ones never forget to tell you how great they are at what they do, and what they can do. Usually, they can back up their claims, but it can be grating where a person attempts to tell you what your job should be. I appreciate them, because they add to the collaborative effort, however it gets to a point where you have to put your foot down. They might understand UX principles, but they tend to see it only from one point of view, theirs. This is where a UX professional shines because you should be able to bring together multiple viewpoints, ‘connecting the dots’
A good rule is to, Listen to what they have to say, but always do what is right. It is easy to be driven by technology where two or more of these are gathered, but being the UX professional you are, never forget that your users come first.
Some of the best developers fall into this category and it is not because they write the best code. They are open and curious about what UX is and how it benefits their own process. They contribute constructively and spark ideas in others around them. They genuinely want to solve problems creatively.
Never forget to tell them how much their efforts are appreciated, teach them more about UX and how best you can work together.
Work well anyway
Now, none of these categories are rigid, I have had a good friend switch from a Code-It-All to Code-Open recently. Neither do they cover every single type of developer out there. In my experience these are the ones I’ve come across and how I have learnt to work with them.
It’s always rewarding when people attempt to understand each other, how else are we going to work productively and delightfully together?