In my previous post on Object Oriented UX, I discussed defining objects from your requirements to create a modular system. Now lets look at how you can take those objects in conjunction with actions to create an interaction model that maps out the overall UX architecture. Thus creating a plan to achieve the goal of a better process to deliver exceptional products and services.
When you hear someone talk about object-oriented design, you may jump to the conclusion that they are speaking about coding. Object-oriented thinking has been around for a long time on the development side of the house, but it’s time that user experience picked up the practice too. Let’s start with a definition of what object-oriented means, and then we’ll look at how this can be applied to user experience, design, and development.
Topics: User Experience
Developing an experience strategy can seem daunting, but if you look at it as a set of coordinated, planned actions/tactics, which will take you along a journey to reach a desired future state over an established period of time, then it seems a bit more manageable. Breaking that down into bite-sized chunks, let’s start with the set of coordinated, planned actions.
I recently spoke at a global hotel conference about connecting physical and digital experiences for users. My colleague, Justin Reilly, started off our presentation with great information on how storytelling affects the human brain. To tie into this great introduction, I asked my audience to imagine their website as a virtual hotel. I then began to paint a picture of the parallels between the two.