developer.* Blogs - I'm an Idiot Who Doesn't Know How to Use a Telephone - Comments

I don't think we have that

Guest — Tue, 13 Mar 2007 12:12:22 -0700

I don't think we have that in Europe. I didn't know you could do so many things in a voice mail, I thought the point was to simply leave a message.
So, here, you only have to listen to the silly "you have called to number 123455..." (as if you didn't know which number you were calling to, or if, otherwise, you were going to realise that one of the numbers was wrong) "...please leave your message after the beep". And that's all. No callback stuff (it's always easier and faster to just mention your phone number in the message) and no beepers options (who has a beeper, anyway?) (I think pager and beeper are the same thing)

Totally agree

Guest — Tue, 25 Jul 2006 08:46:37 -0700

The endless litany of voicemail options usually makes me just hang up in disgust instead of leaving a message. Is there a button I can press to end this nonsense and just LEAVE MY MESSAGE? I'm still searching the internet for a solution.

ATMs, too. Amen.

Andy Tegethoff — Tue, 13 Jun 2006 11:31:03 -0700

First of all, ditto to the entire post. Almost all cell carriers' VM systems were clearly programmed for use by the unfathomably stupid.

As far as ATMs, I've recently noticed that my megabank's machines now have a dedicated "Fast Cash" button, such that once you enter your PIN, you can shoot directly to the "Choose an amount" page. What's more, you can store a default value, so that in the future you can just push one button and get your dollars.
And it only took them 20-odd years to come up with that!

The inmates SHOULD run the asylum!

Edward G Nilges — Fri, 09 Jun 2006 20:23:36 -0700

See my blog post with this title.

Usability Trade-Offs and Bean Counting

Daniel Read — Fri, 09 Jun 2006 08:46:53 -0700

Mistake one is to let the novice user drive design to the extent that it imposes on sophisticated users. ... The second mistake is allowing seldom-used features to impose on everyday users.

These are pet peeves of mine as a user also, but these are real issues in software design, and well worth bringing up for discussion.

I have been in the situation a few times in which the client or subject matter expert whom I'm working with suggested a certain design or feature that is oriented towards making things easier or more clear to the novice or new user, but as Rob points out, so often these kinds of well intentioned features are the very things users will come to hate (and which will limit their productivity) after they've worked with the software for a few weeks. This situation has come up for me in the context of both shrinkwrap/turnkey software and back-office internal-only corporate software.

In my limited experience, there is typically an existing user group that is being migrated away from either a manual process, or more likely, from an old keyboard-centric DOS/green-screen UI. Either way, the underlying assumption is "A lot of the users are not savvy with Windows/Web user interfaces." (Incidentally, I think this sort of concern is dwindling rapidly as we forge into the 21st century--I saw this more often in the late 90's.)

On some occassions I have made attempts to explain that the particular design/feature might have unintended consquences. I try hard to not send the message "This is a bad idea," but rather "This is a good idea, but it might have some unintended consequences that you might regret later."

I have had success framing the issue as one where we need to calculate the trade-offs in a strategic way. For example, if there are indeed a large number new, unfamiliar users that will be confused by a "power user" interface, then we can add niceties to the UI to make it less daunting for these users. However, we have to keep in mind that these users are only going to be new users for a short time, and after that they will be "power users" for perhaps years in the future. Is the risk of loss of user productivity/satisfaction for years to come worth the soothing balm you are seeking to apply to the user's transition period to the new software?

If both are important, do you have the time and budget to develop *both* the new-user interface and the power-user interface? Similarly, do we have time to figure out ways we can design a power user interface that can have some new user adornments? If there is no time to do both, my advice would be to accept the painful transition for the new users, try to prepare them for it with training, and invest instead in the long term productivity and satisfaction of the entire user base.

I suspect that the real problem behind the valid pet peeves Rob describes with voice mail interfaces (and which I've experienced similarly with things like ATMs, fax machines, cameras, and other consumer electronics) is "bean counting," much the same way that automobile manufacturs will calculate the cost of lawsuits vs. the cost of adding a safety feature.

Some software person may have indeed explained to a management person the very point of view I present in the preceding paragraphs, but the management person(s) follow thought processes like "Is it better to annoy a bunch of people who will never call my support line to complain, or confuse a smaller number of people who *will* call my support line because they *are* too stupid to use the phone. ;-)

Dan

P.S. A must read for this topic area: Alan Cooper's The Inmates are Running the Asylum.

Soooo true

Guest — Fri, 09 Jun 2006 07:04:33 -0700

Soooo true

I'm an Idiot Who Doesn't Know How to Use a Telephone

Rob MacGrogan — Thu, 08 Jun 2006 17:37:42 -0700

"You may leave your message after the tone. When you are finished, you may hang up, or press pound for more options. To leave a callback number, press six. To page this person, press star star."