Any successful system improves its users’ work practice. The improvement means increase in efficiency and accuracy. One should be able to deliver in less amount of time without any errors. Technology in software really does not matter. People decide to use jazzy user interfaces because they look good during demo and they look “cool” to your developers. But, if that extra graphics is killing the performance and not adding any convenience to end users then it’s incorrect technology to use. If particular software is going to improve the system then it will get revealed during design phase itself. If we are not sure about it after completing high level design then do not start coding. It’s time to revisit your design.
Contextual design as described by Hugh Beyer and Karen Holtzblatt promises successful software. The process of contextual design drives work redesign if required. Work redesign brings the designers together to discuss the consolidated data and how technology can improve the work. This focuses the conversation on how technology helps people to get their jobs done, rather than on what could be done with technology without considering the impact on people’s real lives.
For more details on contextual design, I would recommend you to go through book called “Contextual design – Beyer/ Holtzblatt”.
This book is available on Amazon.com
http://www.amazon.com/gp/product/1558604111/qid=1148032519/sr=2-1/ref=pd_bbs_b_2_1/102-4335525-3001724?s=books&v=glance&n=283155
