I tend to agree with Will here; a couple of years ago I was working for a company in the UK. The software gave users access to different functions or features depending on their permissions, but the developers opted to make all functions show while those that were unavailable were greyed out.
While this made sense to the developers (not sure why though), the users couldn't understand why they were not able use a particular function, even though it was shown. The helpdesk received numerous calls regarding these greyed out functions from users who thought that there were problems with the software as functions were greyed out. I think that it is also perhaps worth considering the kinds of users who will be using the software; Will white-collar users understand differently than blue-collar workers? Will you need different design considerations based on the socio-economic group of your [potential] users? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=36261 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
