User Experience design has always been, and continues to be, a field riddled with ambiguous labeling and nomenclature. We hear all sorts of conjecture and debate as to what terms have what specific meaning. Are profiles and personas the same thing? When exactly do wireframes become mock-ups? Is “mock-up” supposed to hyphenated? These are issues of semantics, and when it comes to the actual meat of the work we do, we could call a wireframe a “whosamawhatsit” and it wouldn’t change it’s purpose. From the perspective of standardizing our professional space, common labeling is important. This is not in doubt. Client, asset, and project management aside, there is something vital to the decisions that we make as designers that is not addressed as often as it should be: Science.
On Tuesday, November 9th, Krish Mandal, Eric Fitchett, Paul Hurlock and I attended an event in New York called HTML5 Live. My intentions going into this were to get a better understanding of HTML5, where it is now, and where it’s going.
I actually got more out of the conference than I had anticipated. I was pleasantly surprised with some of the tools that were demonstrated, and some of the HTML5 features that were shown, particularly native validation and the enhancements to Adobe’s Creative Suite. As I expected, the general sentiment was that HTML5 is going to be big, but it is only practical to develop it right now in a controlled browsing environment. Progressive enhancement is certainly possible, but with all the uncertainty around video and audio codecs, and how other native features will be handled in a standardized way…
Integrating Agile methodology and User Experience Design has long been a challenge. This diagram shows how the two can work in harmony with each other to produce profitable products that meet the demands of stakeholders.
This diagram shows the stages and deliverables of the User Experience Design process.