It’s difficult to feel the tension between yourself and other team members when you have differing ideas about how products should be built. Standing up for user needs is sometimes seen as an inconvenience when battling against crushing development deadlines. It’s even more difficult to feel this way when user experience isn’t valued as highly as it should be.
The books I read in 2017 perfectly illustrate where my head was at last year. They're a sign of what my learning priorities were, and what inspired me. In this retrospective article I'm not going to give a review any of these books, but rather I'm going to talk about the effect they have had on my habits, skills, outlook and attitude.
In August 2017 I was asked by the CTO of Basis Technologies to lead a UX design project to create a web dashboard for Basis Technologies' newest product, Testimony. This is a story about how it went from an idea to a coded website in two weeks.
This article details the why, what, and how of my ongoing journey to create a product discovery process at an enterprise software company. I have structured it in five parts: situation, task, action, challenges and results in order to help you understand my thinking and approach to my work.
As a Product Manager who also wears the UX Designer hat within my organisation, it is my responsibility to ensure that we provide value for both the user through a good experience and our business by delivering bug-free software that is built in a cost-effective manner.