Transientstudent

In my readings on Human-Computer Interaction, the emphasis is usually placed on promoting time-to-accomplish efficiency measurements. This is not surprising, as these sorts of metrics are useful for cross-comparison of systems, and whether or not one system is better than another.

What I do find surprising is the segregation of these metrics from user satisfaction. It could be that they’re directly related: a user that is able to perform their tasks more efficiently (read: in less time) is also likely more satisfied with the system.

What if, however, a system is quantitatively less efficient, but qualitatively more satisfying? If a user does less in the same amount of time, but enjoys it more? My guess would be that they would perceive time passing quicker, leading to a better overall experience with the system, even though the numbers tell us that they are actually slower.

What then? Where is the emphasis on usability placed after that? If we’re looking to make things for people, shouldn’t the emphasis be on making a system that they enjoy using, rather than on one that allows them to accomplish tasks faster? And are efficiency and satisfaction directly linked?

Just some thoughts for a sunny Saturday morning.