When I started my professional programming position at Upjohn’s, my first task was cleaning data within ‘soon to be decommissioned systems’. I soon observed that adding additional, unnecessary fields was a common practice. I remember the countless hours I spent scrubbing data so that we could offload old Fortran records into our new Oracle Intranet'. It amazed me how many duplicates I found, but the biggest surprise was the number of obsolete records and fields that were not used. So, I disregarded them during the join process when I uploaded the old data sets into new systems. 

​

How Does This Relate to UX?

In our new ‘Intranet’ we used MS Visual Basic as our front end (GUI). This was great and for the first time, the hidden records from within in the dBase were now more transparent, including the functionality and purpose of the system. We made user interfaces that were intuitive and purposeful and helpful not only for the users, but were also more efficient to cross-train new programmers as well.

However, I saw that here too we somehow thought that the more we added, the more impressive it looks? 

For me, more is never better, 'best' is better. 

​

UX in My Own Words
UX, in my experience, starts with the consumer/user. It has to be simple, intuitive, capable, and functional and it has to be an invaluable asset to completing one's objectives.