Why I became a UX designer

I enjoy coding because it allows me to make digital things with both hardware and software. I studied computer engineering at the University of Waterloo then I was a developer for 8 years. I worked on software which dealt with automotive manufacturing to investment banking. However coding wasn’t the favourite part of my job. The part of the job that I enjoyed the most was gathering information on the business problem and working on what the solution should be.

In an enterprise environment the role of gathering of business information was designated to the business analyst. I did that for a while and produced documents which listed the functional and non functional requirements. Although I learnt a lot about the business, I was missing out on the other side of the applications — the users.

What inspired me?

Most designers I worked with, I never saw. I gave them the requirements and they gave me a design back. The designs missed out the real purpose and was just putting the lipstick on my Visio diagrams. I didn’t like this process but was there a better way?

This all changed when I worked closely with one designer who did interviews and workshops with users before he even touched Illustrator. He gathered information about the business and produced documents in a visual manner with sketches and wireframes. The business were more responsive in reviewing the requirements of the project and provided more insight on what their needs were. I wanted to create the same collaborative process.

My colleague recommended that I read Undercover UX by Cennydd Bowles and James Box. This book was helpful by showing me where and how I can incorporate user experience design processes into a process which did not have it initially.

What did I have to do?

Over the next two years I refined my process as a developer to include some of these practices of sketching, wireframing, interviews and workshops in my day to day role. I knew I was doing something right when traders who are strapped for time were asking for wireframes so that they can discuss concepts for new features. Working in this environment also meant that I didn’t create huge amounts of documents but just the necessary ones.

The next step was making the jump from developer to designer. All I had at the moment were financial trading applications, how could I relate this to other types of apps? I needed a wider breadth of experience. I invested personal time into a few personal projects and helped out a start up designing a mobile payment experience. I managed to get a job at an UX agency which focused on financial services.

Once in my new role, I knew there was still much I had to learn. Using different tools like Omnigraffle and Axure were easy to learn but the major ones was handling design critiques, design principles and presentations. Thanks to the feedback from people I have worked with, it has helped me improve along this evolving journey.

How do I feel now?

Moving from being a developer to a designer allowed me to keep solving problems. Instead of the how, I am now approaching problem solving by focusing on the why.

There are a lot of similarities and parallels between the worlds between business analysis and UX designer. User stories and system diagrams versus personas and experience maps. Data flows versus user flows. For a while we have treated these activities as being separate worlds. But the software we build have those two sides — the business and the user. One can’t be without the other. It is one product.

The biggest lesson to date for me is that UX design cannot be done alone. It requires business, technology and user research to come up with the right user experience. This makes me wonder how this industry will evolve in the future as we become more collaborative.


For more stories of other UX designers who came from a development background, here is an excellent write up from Boon Chew about his journey.

It’s not my problem

Going through some of my draft posts, I noticed that this was not posted yet. This was a thought I had two years ago which I think it is still true.

You limit yourself when you say it’s not my problem

In my career, I noticed that some people do their job but only their job. It is fair to say that you shouldn’t take on more than you can do then you are just asking for trouble. However if the work you are doing is related and it is not much more effort to help someone else out by doing a bit extra, what is stopping you?

Managers have told me this that these individuals are selfish or not team players. I guess it boils down to whether is that the person can’t or won’t go the extra mile. “No, this is not part of my remit” is a weak excuse (I cringe every time I hear that line). If you can’t do it then at least try to help the person find the path towards the solution.