Seems like I’ve expounded on this topic ever since my first encounter with software and software development. Keep it Simple (Stupid) – aka the KISS approach is, I believe, always appropriate when looking at development of a business application. It has always been my goal that users of applications which I’ve developed not need any “training” in the use of the application, but rather (assuming they know the job which they are expected to do) they just get into the application and start using it.
I’ve written before about how simplicity at the interface and user level does not necessarily mean simplicity behind the scenes at program core, but that in fact many times it adds to the complexity behind the scenes, putting more responsibility on the developer. Certainly consideration must be given to the complexity behind the scene as well that it not become a tangled, unmanageable mess of what has been dubbed “spaghetti code”.
Todays emphasis on simplicity has really been brought to the forefront as the result of checking out a book recommended by Avery in a previous post reply. The book, Getting Real by 37 Signals triggered my mind into over-drive thinking about how strongly I believe in simplicity of design. You might want to check out the link for yourself.
Actually, it seems that I made reference to Getting Real in my post a year ago entitled “Getting Real” is UnReal!. (I knew I had remembered something about less being more!).