I asked this question to my network -
How to bring simplicity in to the design of products – take complexity out and not the capabilities?
Here are a couple of interesting answers I got -
David Marshall wrote back -
It should all be driven by a proper elicitation process to define system requirements. This should result in an immediate protoyping session with the users without ever telling them what is technically possible. Find out what they need to be able to do their work effectively. Then build that and only that. Too often, designers build what they want to work on and with. The latest technological gizmos are cool. It is boring to keep reusing the tried and tested code. Except that users want only what makes their work easy. Anything that slows down the system’s performance or clutters up the GUI with redundant options is annoying and demotivating. It is hard enough to manage the transition to a new system. Giving the users the chance to take ownership of the design gives managers the best chance of a smooth transition. Thus, taking the designers out of the design is the best way to achieve simplicity.
Shantanu Sengupta says -
1st step – Forget you’re designing!!! Think you’re solving a problem!
2nd step – Once a solution is found, don’t stop… look for more solutions – at least 5 more!
3rd step – Apply logic and reason to see if these solutions are different and addresses the problem fully
4th step – If yes, see if they’re simple enough for applying in reality
One of the readers of 
I interviewed Bill George, author of best-seller books
Uncertain Future: Our brains have a number of issues that make it hard for us to predict “what would make us happy”. The most significant shortcoming is the lack of details in our imagination. When we think about a future event we tend to just imagine a few important aspects of it. Our brain misses on a number of details.


