Daily using/supporting

Get Firefox browser!
Get Thunderbird!
Get Opera browser!
Get The Gimp!
Get Inkscape!
Get LibreOffice!
Get Videolan!
Get Linux!
Get Mandriva!
Get Joomla!
Hacker Emblem

Archives

Which topics would you like us to cover more?

Latest comments

Latest tweets

about 1 day ago Using REDIPS.drag to add drag and drop to your .Net webapplication #li #dib0 http://t.co/n8zY3s7d
about 7 days ago http://t.co/cknQcDbo #Kindle
about 15 days ago Freedom isn't the ability to choose what to do or say, but the ability to choose what not to do or say #freedom
about 29 days ago http://t.co/61KTQknI #Kindle
12 Apr 2012 Force the use of a networking adapter using C# #li #dib0 http://t.co/ZTJOPzOz
9 Apr 2012 Mandriva 2010.2 and USB devices in Virtualbox http://t.co/fwq9gbHB
9 Apr 2012 Execute a http request to you own site with PHP http://t.co/DIvWPrpd
Home Architecture, security and coding Listen to your user... Or not?
Listen to your user... Or not?
Written by Division by Zero   
Wednesday, 02 June 2010 10:23

Did you read 'Why Software Sucks ... And What You Can Do About It' by D. Platt? If your answer is "No", you should!

The rule that summarizes Platt's book is 'Know thy user for he is not thee'. You are not your user, therefore you can't think the way your user does and you can't make decision for your user. Listen to what your user has to tell you and create software (tools) that make the life of your user easier. Not harder.

So... if I want to create usable software I have to listen to my user. That's at least what I thought. That is, until I came across this article 'First Rule of Usability? Don't Listen to Users' by J. Nielsen. Nielsen tells us that we shouldn't listen to our users, but just watch what our users do. There's an interesting take. According to Nielsen users don't rationally know the best way they perform their work, at least they can't explain it. There is a difference in what a user thinks and does.

I want to create software that is usable... Should I or shouldn't I listen? The truth, as always, is more subtle. Platt and Nielsen are both right. The difference between the two is that Platt is mostly talking about functionality and Nielsen about user-interface design. TO create usable software we have to listen (not just listen but discuss!) to our users and study the way they work. Does the software fit the work-process? Does it fit the way a user uses the computer or the network-infrastructure? I think it is impossible to get this one right at the first attempt. It is important to keep discussing the software with the ones that will eventually use it. Keep in mind that it is often difficult for users to talk about functionality. At first, discuss the way they work. Base your first design or prototype on this and then discuss software functionality. This way it is easier for you and your user to talk on the same level.

 

Add comment


Security code
Refresh

Prayer does not change God, but it changes him who prays. - Soren Kierkegaard


© 2009 - 2012, Division by Zero

Template based on the empire template by joomlashack 

Valid XHTML 1.0 Strict  Valid CSS!  Creative Commons License
This work by Division by Zero is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Netherlands License.