I never been to any Book Club meetings before, it was my first time there. I attended UX Book Club San Francisco on the evening of May 26th 2010, it was about a book name Thoughts on Interaction Design by Jon Kolko. Very intriguing book. Part theory, part practical and stories of the experts.

The topics that discussed were from the book context as I remember few were Data and Process.

Data as in web analytics data are mere representation of the usage but not the usability counter. It don’t capture the User Behavior, there likes or dislikes. Although the Usability Tests are there where you can observe the user and capture the accurate interaction conundrum or satisfaction.

Processes is like defining the path how a User will go from point a to point b. However these days applying something similar to Six Sigma is a big NO. Fast paced era needs fast paced process. As one of the participant pointed to the Agile Development Method. Where releases are in small chunk. Approvals are small chunks too. However it is not quite easy to get all the thing involved in an development to be catered in an agile context. As one of the member said and I kind of agree with her that You need to define the complete framework. For instance if we are taking from features perspective then do not try to implement them all at once, and ask the business owners to approve it at once. We should have release cycle for two weeks for let say only two to three feature. This will keep the standards of end-products very high. And as I personally saw where I work that our product that was developed from agile perspective has 0.001% support issue.

While discussing about the Interaction Designer role and why most of the time Project Manager, Business Owner and most of the Development Team does not put them on priority. At that point I felt that there is a need of a bridge. Double-Decker Bridge like Bay Bridge but not weak one.

I at that point did have my say. Developers and Interaction Designer are doing the something except there perspective is different. They both are fluent in there Design Pattern language. Coding is art. So does crafting product behavior. Coding a piece of module is an art too, developers do need to code in a way that it don’t hurdle the future enhancement which lead them to carefully pick the Design Patterns in such a harmonic way that I am dead sure people from the other side will be amazed. Same thing goes for Interaction Designers, there mindset is totally toward the usefulness with ease. Their observation of the user behavior is really intriguing and artistic then putting there research in to a desirable form and combing with the developers effort for sure it will create a very useful, desirable and emotional product. Why we love Gmail rather than Hotmail? Why some who are not in favor of Dancing Bear are lean toward iPhone than Google Android? Why we want elegancy? Even at Target Store people love to get there prescription? Why Boxee Media Center is much more usable then the Windows Media Center? It is the work of Interaction Designer and Developers. Not just one entity but two working together.

I told the group a story of a two construction worker, it goes like this:

a curious person was looking at a construction site, there he saw couple of construction workers building something. he went to “constructor worker a” and asked him, “what are you doing?” the worker replied “oh, I am constructing a building where I need to put the cabling modules, sewerage system, heater and ac and ventilation etc”. then that curious person went to another worker “construction worker b” and asked him the same question ” what are you doing?” he replied… I am building a church.

Now you see both groups are doing there job and they are doing perfectly. One group is really focused in to the inner and other is working on the outer side, that group is also trying his best to get the perfect aura of the end result. However they can’t live without each other they need each other.

How to make Developer to see the goal of Interaction Designer? Very simple Interaction Designers should pull them take them 30,000 feet and show it to them that’s what we are building. Same thing developer do with UX peeps, take them in to a wonderful world of coding and show them the MVVC pattern, how it is really benefiting the designer, and developers.

See one group trying to build a robust engine for Ferrari another group creating an exterior and the behavior. There path is  parallel, it is a two lane street they have to make sure they are sync and holding each other hand. If any of them fail. Blame will be on both of these groups, on a team. Instead of Developers or Interaction Designers.

For that purpose go play with android and iPhone. iPhone works superbly well because Hardware, Software and Interaction is extremely taken care of. On the other hand Android software is awesome. However hardware and interaction around it is poor. So overall Google Android is complex. Where as iPhone is superior. Simple. Here blame goes to Everyone who worked on Android not on one group only.

Hope we in coming days will lead to a path where we understand each other.

May the ease be in our life and in those who we work with.

Get inspired be inspired.