This book is licensed under a Creative Commons by-nc-sa 3.0 license. See the license for more details, but that basically means you can share this book as long as you credit the author (but see below), don't make money from it, and do make it available to everyone else under the same terms.
This content was accessible as of December 29, 2012, and it was downloaded then by Andy Schmitz in an effort to preserve the availability of this book.
Normally, the author and publisher would be credited here. However, the publisher has asked for the customary Creative Commons attribution to the original publisher, authors, title, and book URI to be removed. Additionally, per the publisher's request, their name has been removed in some passages. More information is available on this project's attribution page.
For more information on the source of this book, or why it is available for free, please see the project's home page. You can browse or download additional books there. To download a .zip file containing this book to use offline, simply click here.
Barlow was the head of our IT group and he was also the head scorekeeper for the plant’s golf league. Every Monday morning Barlow would take the golf scores from the past week of play and compute the league standings as well as calculate the handicaps. Barlow had been doing this for years. Someone in human resources thought that he was spending too much time on the league and they also thought it was a burden to Barlow. So HR commissioned a golf handicapping and league scoring system. A complete cost–benefit analysis was actually implemented and the payback was deemed acceptable, so the green light was given to the project. A team of analysts and programmers were assigned to gather requirements and implement the system. Tens of thousands of dollars were spent developing and programming the system. The system was used just a couple of times. It was a pain to use, the results were incorrect, and most importantly, Barlow could finish his calculations faster than it would take to key-in the data and generate the reports. Barlow actually liked his manual system and took pride in his ability to produce weekly updates in a few hours. He said as such, in quiet tones, but he was not listened to.
In the current market context, functionally designed products and services are sometimes at risk, unless the meaning of the design is to convey simplicity and functionality. There are numerous examples of successful products and services that simply do what they are supposed to do, because they are functional. Functionally designed products can be even more successful when they are accompanied by user-centered design and meaning-centered design.