Saturday, January 13, 2007

which requirements are worth supporting??

There are many features that would be nice to have. For example, how many people press the wrong button in elevators once in a while, and then have to wait while the elevator stops at the wrong floor? It would be nice if there were some kind of undo function. Maybe you could press the wrong button a second time to turn it off.

But here is the question. How important is this to the user experience? And are there consequences to adding it that could take away from its value? For example, would it add to the cost of the design? Would there be a learning curve during which other errors would occur (hitting the button twice on purpose to "make sure" we pressed it). Would there be other permanent errors that could be introduced (someone intentionally turning off other passengers' floors because they are in a rush).

It is this set of tradeoffs that are necessary to decide when a design feature really makes the system more effective.

No comments: