Welcome to MSDN Blogs Sign in | Join | Help

Anandi’s Thoughts

Random stuff (mostly) about working as a Program Manager at Microsoft
Some tips for your VUI design

Hey!  It's my first post actually related to Microsoft Speech Server.  Actually, that's not true - one of my earlier posts was about a slew of MSS KB articles we published in July.

Last week, Kevin, one of the awesome Product Managers on our team, presented some tips for designing a voice user interface (VUI).  I liked the simplicity of these tips, so I'm sharing them with you, my loyal readers.

Tip #1: Don't replicate the touch-tone-based menu system

It's a better user experience if you let users choose an option by name rather than having to remember which number goes with which option ("Press or say 1, etc.")

Tip #2: Restrict options on the main (opening) menu to 4 or fewer

Studies have shown (unfortunately I don't remember which ones) that people are only good at remembering lists of up to 3-4 items.

Tip #3: Make sure your opening greeting is short

Frequent users (and really, any users) don't want to listen to a long greeting before they can get down to business.

Tip #4: Don't design the app solely for the new user

Again, you don't want to frustrate frequent users with extensive info.  You can reveal additional help progressively, if your users seem "stuck".

Tip #5: Focus on task completion above all

Your users are there to perform a particular task or get certain information.  Focus on that above making your application "fun", "exciting", or "personal".

This isn't rocket science, but I think these simple tips will go a long way towards building an application that at the very least, doesn't annoy its users.

What tips do you have for VUI design?

Posted: Wednesday, February 08, 2006 3:53 PM by anandi

Comments

Brandon Tyler [Intervoice] said:

Thanks Anandi!  I was trying to write these down but didn't get a chance.
# February 10, 2006 2:46 PM

Marshall Harrison [Landstar] said:

Thanks Anandi.

One of the things I like to do is try out the VUI with users that are new. I prefer not to give them any instruction on how to use it and get their feedback. This way there is no coaching from me and you get the real experience of a completely new user of the system instead of tainting their experience with my knowledge of the system.
# February 14, 2006 7:56 AM

anandi said:

Marshall - that's a great idea - thanks for the tip.  How many of these new users do you try to get feedback from?
# February 14, 2006 7:11 PM

Marshall Harrison [Landstar] said:

That depends on the scope of the project and its intended audience.

If you will be getting lots of first time users then the key is to not coach your test audience. You want their impressions as a first time user. As they use it more you can then get their observations from the standpoint of an experienced user. You want them to discover on their own the shortcuts. If you have to tell them how to navigate then you have blown it with your VUI.

As developers we obviously know how to use the systems to their fullest. We have to be careful not to influence or taint the pilot users.

# February 15, 2006 6:54 AM

Sara Rea said:

Late last year, I wrote an article for DevX.com titled, "Top Ten Tips for designing Telephony Apps". Iy is very similar to your list. Thought you might be interested in seeing it.

http://www.devx.com/dotnet/Article/29623/0

Thanks,
Sara
# February 25, 2006 11:57 PM

balunkl said:

tips are very useful. thanks
# March 21, 2006 6:46 PM

Speech Served Here said:

The show:
Introductions (brandontyler and csharprox)
History and vision of GotSpeech.Net
Katrina Safe...
# April 10, 2006 4:01 PM

Speech Served Here said:

The show: Introductions ( brandontyler and csharprox ) History and vision of GotSpeech.Net Katrina Safe

# March 22, 2007 9:34 AM
New Comments to this post are disabled
Page view tracker