what ever happened to object > action?
I’ve noticed a trend in user interfaces i’ve reviewed recently that designers are moving away from the use of object > action towards using action > object.
For instance, someone told me that the new St George online banking asks you to choose what you want to do first then choose the bank account you want to do it to. I’m not convinced that this is the best way to organise sites. A case in point I was recently asked to integrate an action > object “knowledge management framework” into an information based site.
This request was difficult to cater for because what the framework asked for was that users come to the site with a problem in mind, but after choosing thier problem category they then had to define what process the problem belonged to. This seems sensible from a high level perspective, but what if you want to explore multiple problem categories across the same process? Well then you have to go back to the top of the tree and navigate from the new problem down through the process again.
The same with the new St George banking system, evidently if you want to make more than one payment from an account (e.g. paying your monthly bills) you choose pay bill and have to navigate which account to pay from again and again.
Damian suggests that this sort of logic is due to the use of user scenarios and not a lot of thinking on behalf of designers, I’m wondering if it is the emergence of a new interaction tradition.
