Product built-trap and mind the gap between business and user objective
Once upon a time when I was doing product tech development, I thought that with all the product technical capabilities and features that we built, it will solved users problem and our product will enjoy the big success and generating revenue for company, unfortunately it was not! We were representing business and have bias in our decision-making process that we pretend that we representing our end-users. We were doing FGD and research but we came up with bias conclusion. So we thought this product must be built and solve users pain points. Once we had around 160 products to be delivered in a month, despite we were able to delivered them but only two achieved its revenue objective, the rest silently waste our development resource. This is the product built trap!
I use below old picture on TIER Swing vs TIRE Swing but I think its still relevant to illustrate product development process and how the gap arise from capturing user definition, “scope-creep” and project management aspects, quality and documentation, operations and support.
When we tried the user journey, UI/UX sometimes we torture them by offering not needed features, text and buttons that should not appeared in right user journey or requirements. We forgot that user need only need to see what is relevant and needed at that particular user-journey. If we want utilize the feature in the application, one of the solution is to blend it into the journey. For example in the user registration, we use hint on user-name and address rather that put a label User Name, email or phone. This is how we combine features, user-experience or ergonomics.
What do you think about this customer journey, ergonomics, UI, space efficiency?
What about below approach?
We need to keep on experimenting and learn from others right? So we identified the mind gap between what company needs to enable user to Log in, Register and Activate.
It’s not easy and sometime we are not aware that we are in the middle of built trap situation and even though we aware, we are able to reject and manage the condition. While mind the gap between user and company objective need to be balanced, product owner need to drive it.
