Comments on: Good Interaction Design Often Not Up To Interaction Designers

By: Peter

Peter — Sun, 08 Jul 2007 06:45:02 +0000

Thanks for the comment, Scott.

By: Scott L

Scott L — Sun, 08 Jul 2007 01:07:26 +0000

I think what you are talking about is actually the complete interaction part itself, the programmers are there to code based upon the information they are given from interaction designers,and once coded they are by no means the last people to deal with the project in any sense.

The user testing and initial feedback from what the programmers then have done can be evaluated by the interaction designers, so that they can asses if this is to the users requirements

A final point “Good Interaction Design is always up to Interaction designers” thats the purpose, yes there may well be company politics etc that could give poor communication, but the goal as an interaction designer always should be to be able to communicate the design to the programmers so they can develop the correct system.

By: Joel Laumans

Joel Laumans — Tue, 03 Jul 2007 00:17:51 +0000

I understand where you are going with this, but I think its not really “up to the programmer to implement these improvements”
…it is his job!
And if he can’t/won’t they should hire a different programmer.

I think that if a company is willing to pay for an interaction designer, they are willing to listen to him.

By: Dennis Koks

Dennis Koks — Mon, 02 Jul 2007 21:09:44 +0000

This also depends on the internal structure of a company. Companies that work withing teams who contain a person of every disapline will have this problem way less. If you’re in a company with a seperate programming department and a seperate interaction design department the chance is much bigger that these problems would occur.

It’s also a matter of how serious people take the jobs of his/here colleagues, and the visions they have uppon the whole process.