Insights from a book on why software s**ks

For those of you who wonder why software is so difficult to use,

may I suggest the book Why Software Sucks, by David S. Platt (note: I normally avoid such words, and give the title in its entirety here only out of a desire to be accurate). In

fact, I was reminded of this book by a Tech Republic link, even

though I had heard about it before. I mention this book

because it offers insights into and can help improve your

relationships with your customers.

In an early chapter of the book, Professor Platt discusses a

theory that explains bad software. He concludes, not

surprisingly, that developers focus on their own view of how

software should work, rather than considering how users believe it

should work. As an example, he cites the floating toolbar feature

of Microsoft Office. How often, he asks, do people who use Word,

Excel or PowerPoint really use that feature? Or, put another way,

when they DO use that feature, how often does it happen by design

rather than by accident?

Curious about and intrigued by this theory, I decided to check for

myself. At a customer service training program I conducted last

week for IT professionals at an East Coast university, I polled the attendees, asking them this same question. I found, not surprisingly, that only a small percentage of them floated the toolbar because they really wanted or needed to. More commonly, they did so by accident.

I then asked if what they said, when they accidentally floated the toolbar, was printable, and everyone laughed.

Think about this "floating toolbar" matter yourself, and ask if you also do so mostly only accidentally. Now think more about whether, instead of putting in that feature, the developers should have spent time and budget to put in things you REALLY would find useful.

Avoid giving your own customers the same grounds to be annoyed at you. The more you show customers that you understand their point of view, the greater (generally) will be their satisfaction. When dealing with a customer, remember that the technical problem will cause an emotional reaction. Depending on the circumstances of the problem, and the work affected, that reaction could range from mere annoyance to outright panic and anger. For that reason, if you want a satisfied customer, you probably need to do more than solve the technical problem. You may need to be the counselor/psychologist as well, and let the customer know your awareness of the customer's emotional reactions. When you do so, even if you don't solve the problem right away or get it completely right, the customer is more likely to "cut you some slack." On the other hand, if all you do is solve the technical problem, you may leave behind a customer who STILL is upset at IT.

I hope this insight helps you. Now go and float some toolbars.


Calvin Sun is an attorney who writes about technology and legal issues for TechRepublic.

Editor's Picks