By Eric W., Lead Product Designer
I was recently invited to speak at DevFest MN 2018, [https://devfest.mn/] a Google Developer Group’s local conference intended to bring members of the engineering community together to learn and share. As a Product Designer speaking to Engineers, I was excited to represent my discipline and share some advice on how to improve the ways we work together.
Great Product Design requires great relationships, and few relationships are as important to the success of a product as the one between design and development. Both parties need to understand each other, challenge each other and compromise effectively to build the right things, at the right time with right level of quality.
Most of us however, have never been meaningfully introduced to the other’s world nor felt what it is like to walk in their shoes. So the relationship between Designers and Developers can often strain under the weight of assumptions and abstractions.
My journey toward empathy began with a simple goal of wanting to better understand the Developers I worked with every day. I wanted to be a better partner to them and communicate more effectively. So I learned to code. I didn’t do this with any intention of submitting pull requests, but simply to increase my awareness.
I watched Stanford lectures on Computer Science, listened to coding podcasts and did tutorials and coding puzzle games. As I became more immersed, something surprised me. I was struck by the sheer variety of ways I could solve any problem. Often times the goal was clear, but there were so many ways to get there.
This experience reminded me of something familiar…and then it hit me. I was using the design process. Coding was a form of creative problem solving. I was pushing code rather than pixels but just like Product Design, coding was a craft. It could even be an art form. I had far more in common with my Developers than I ever realized and I wanted to tell the world. DevFest was a great start.
Speaking at DevFest was about highlighting what we have in common and leveling up the audience’s understanding of the world of User Experience. If you peel away the jargon and tools, Designers and Developers want to make great things, and make things that matter. In a high-level but comprehensive way I built up their context by defining UX, demystifying titles like “Information Architect” and “User-Interface Designer,” describing the tools Product Designers use and the challenges we face.
I left them with a challenge:
“On Monday, when you get back to work. I want you to ask the Product Designer you work with to coffee. Ask them ‘Why did you become a Product Designer? Why do you do what you do?’ and then listen graciously to what they have to say. I think you will find you have much in common and let that be the beginning of empathy for one another. The beginning of a stronger working relationship. A relationship that leads to better products and more enjoyment in our work.”
I give you the same challenge.