Comments on: Apple, Steve Jobs, Innovation and Iphone

By: Francois Aubin

Francois Aubin — Sun, 22 Jul 2007 18:44:58 +0000

The interaction designer must try a much as possible to do his homework (user observation, task analysis, usability testing). When there is a client, it is even more important. When we have the chance to do some of our homework (usability testing with enough subjects, task analysis). It is easier to provide the right information for decision making. In this context, client understand our design rational.

The problem lie in making client understand we must do our home work as interaction designer. This is the biggest challenge of the profession. They usually will tell they lack time or budget. When we feel it will not be possible, I suggest trying do part of our homework on our own time. Example recently I was ask to evaluate a mobile device and there was no budget for testing. So I dis test informally with colleague around me.

Interaction designer should avoid basing recomedation on heuristic and experience only. The risk to provide the wrong advice is too high. The consequence could be a lost of credibility

By: Adriana

Adriana — Sun, 22 Jul 2007 17:23:46 +0000

“…. In my view, the most important aspect is the Apple culture. It is not an engineering driven company but a design driven company. Decisions are not based on technical constraint. Of course, designers listen to engineers but they will sometimes ask them to go back to the drawing board and think again and be creative to achieve the design goal. For example Bill Atckison wanted the screen of the original Apple Lisa to be white instead of the traditional black in order to imitate the paper. Engineers at the time were strongly opposed saying it would consume more memory etc…but Bill stuck to his point and the engineers found innovative ways to achieve Bill’s design goal……”

Interesting point… This talks also a lot about a major respect culture from both teams (developers & designers)… Often in small companies the design of a new product is not only constrained by discussions between these two teams… it is also constrained by the client, the time and the budget… What is your recommendation on these cases…