Making Things Simple

Over the last three weeks, I’ve been doing a lot of work on a new site. The basic premise is that it needs to be very user-friendly, easy to use, quick, smooth, and useable. I’ve got my own ideas about a lot of this, and on the initial development work, I’ve been applying quite a few of them to what I’m doing.

One particular thing that drives me crackers when I’m using a website is – to use the example of on-line banking – when I have to go through a seperate page to ‘select an account’ when I’ve only got one account. To me, if that’s the case, I’d far rather that the system had some logic, and effectively figured out for itself (OK, was programmed to ‘realise’) that if I’ve only got one account, I don’t need to select that account, it’s fine to go straight through to the account details page.

Anyway, I’ve been working to a similar kind of idea on the site, and while in theory it’s simple, it actually turned out to be (in some ways) a real pain. Yes, the logic is also simple, it’s just that it does take a couple of extra steps in order to get it to work.

But when it does work, it’s really nice, and makes life a lot easier.

Why is it, though, that making things simple to use can be incredibly complex in the back-end, whereas making things really complex and obstructive is actually dead easy?