When designing a new web application, I wrongfully turn my brain into data collection mode. I determine what data entities I need to collect (people, orders, products, etc…), what fields I need to collect (name, sku, weight, etc…) and how to most logically group everything together into a usable interface. This process is all wrong.
Often I ignore, or worse… neglect, to account for the business procedure that is in place to actually collect and account for that data.
When we think about the development of websites, we think of the back-end development, graphic design and semantic markup that are coded and combined into the finished website.
The user experience design is often overlooked. It is intangible, naturally vague and difficult to understand. However, making this user experience comprehendible is crucial to the design process.
It is very tempting to skip over the experience design and straight to designing in Photoshop. Perhaps our ego gets in the way, or we are scared of spending hours that, in the end, don’t return a tangible product.
In the end our user experience notes and research are transformed into wireframes, design comps and ultimately the finished website.