Comments on: Software Designer != Interface Designer http://www.dansketcher.com/2006/06/18/software-designer-interface-designer/ Dan Sketcher on Rails, computers, and other junk Wed, 30 Jul 2008 20:15:31 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: dansketcher http://www.dansketcher.com/2006/06/18/software-designer-interface-designer/comment-page-1/#comment-6 dansketcher Mon, 19 Jun 2006 12:14:06 +0000 http://www.dansketcher.com/2006/06/18/software-designer-interface-designer/#comment-6 I think you might be onto something there MacD. One of the thing my business parter does is use the systems i write and then bug me because it does something stupid that I didn't even think about. I guess that's why they say you should eat your own dog food... I think you might be onto something there MacD. One of the thing my business parter does is use the systems i write and then bug me because it does something stupid that I didn’t even think about.

I guess that’s why they say you should eat your own dog food…

]]> By: Mac Daddy http://www.dansketcher.com/2006/06/18/software-designer-interface-designer/comment-page-1/#comment-5 Mac Daddy Mon, 19 Jun 2006 10:25:03 +0000 http://www.dansketcher.com/2006/06/18/software-designer-interface-designer/#comment-5 Design is a tough gig. It's that link between great code and a potentially stupid user. A great design gives the user a familiarity without having ever seen the system before. A good way to test your design is to write a list on functionality that your user will regulary perform and time yourself performing those activities. Count the number of clicks and screens you need before you complete the task and then aim to cut it in half. As programmers we sometimes get into the zone of step 1, step 2, execute this command, step 3. Simplifying the complex is what good design is all about and executing 2 steps in one screen can be very helpful to a user. Once you've cut down your clicks, time, etc. Give that list to someone who has never used the system and watch how they go through it to execute your instructions. I think this will be insightful for you. MacD Design is a tough gig. It’s that link between great code and a potentially stupid user. A great design gives the user a familiarity without having ever seen the system before. A good way to test your design is to write a list on functionality that your user will regulary perform and time yourself performing those activities. Count the number of clicks and screens you need before you complete the task and then aim to cut it in half.

As programmers we sometimes get into the zone of step 1, step 2, execute this command, step 3. Simplifying the complex is what good design is all about and executing 2 steps in one screen can be very helpful to a user.

Once you’ve cut down your clicks, time, etc. Give that list to someone who has never used the system and watch how they go through it to execute your instructions. I think this will be insightful for you.

MacD

]]>