The Spelling Check is Complete

Yesterday, I mentioned the new contextual spelling feature that is part of Office 2007. Writing the post reminded me of a story from years past...

One of the things we've tried to do from time to time is reduce the number of modal alerts that pop up as part of working with Office. Most people don't spend the time to read the text of message boxes--as a result, unless there's an action that needs to be taken, most people just click OK.

Long before we had the Customer Experience Improvement Program in Office 2003, we relied on data from something called the "instrumented version." This was a special build of Office we gave to a few hundred test subjects to collect a small amount of objective information on how people used the software. It was not nearly as complete or as representative as the CEIP data, but it was better than nothing.

So, when a team was tasked with reducing the number of alerts, they developed a magic formula for deciding which alerts to target: look for the most frequently-appearing alerts (based on the data) which contained only an OK button. Because we know that any alert with just an OK button is simply informative, and we know that most people don't read the text of alerts, knocking just the first 10 or 20 off the list held the promise of reducing the number of dumb alerts seen by Office users by billions and billions.

Dutifully, the team removed these seemingly useless alerts. The very top one on the list seemed like an absolute slam-dunk to remove: "The spelling check is complete." It's a totally unactionable alert--just an extra click people have to do every time they check their spelling. A perfect example of a useless, intrusive dialog box, interrupting your work and getting in your way. Bad design. Right?

Within hours, the complaints started to roll in. Within days, the complaints became deafening from all corners. It wasn't long before the alert was put right back in the product.

Why? People who were spell checking their document manually had no idea when the process was complete. If you've grown up expecting a dialog box to come up once all of the spelling errors are corrected, and now the software just sits there silently--well, it’s no wonder people thought the program was just broken. Or very, very slow.

Spell check is one of those great features that have a beginning, a middle, and an end. The beginning is you clicking the spell check button. The middle is the computer conversing with you about potential misspelled words and giving you an opportunity to fix them. And the end is the computer telling you that the process is complete.

It’s a truly collaborative, uncomplicated interaction between user and computer. The "spelling check is complete" alert is a form of exactly what dialog boxes are named for: dialogue. The computer telling you that it’s finished rounds out and completes the process. It's no different from a checker at a grocery store saying "Here's your receipt, thank you for shopping at Thriftway." It’s a very human way of ending a transaction.

I guess the meta point here is that it's hard to do interaction design by formula. Not many great works of art are achieved through Paint By Numbers.

Comments

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  These dialog boxes are also problematic from a usability perspective. Even though they are modal, sometimes the focus still gets shifted to another part of the application. This strands keyboard users, as there is no clear way to transfer focus back to the dialog without clicking.
  
  Why not have OK dialogs that disappear when the user clicks anywhere or presses a key in the application?
  
  Or you could even use the status bar for what it was designed: communicating the status!
  
  Another possible solution would be to have dialogs that expire--they count down or fade away if the user takes no action.

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  Yeah, I think a non-modal notification would work well. I agree the user needs to know when the process is done, but I shouldn't have to click OK, just to dismiss a dialog. That doesn't make any sense!

• Anonymous
  June 14, 2006
  Roland: I don't think a non-modal balloon would make sense here, because spell-checking is a modal task. It's not a background task that needs to unobtrusively notify you of its status - it's a direct continuation of the spell-check process itself.
  
  That said, perhaps a spell-check scan that finds no spelling errors should exit quietly - there was no modal interaction in the first place.
  
  Ben R.: I think Office 2003's help windows showed why panes are often a bad idea. I would hate for a simple reviewing operation like spell-checking to cause my document to resize, repage and reformat itself.

• Anonymous
  June 14, 2006
  Avner: I agree that Task Panes have been a pain. However, just because they were poorly implemented does not mean that the idea has no merit.
  
  The latest version of Acrobat has a delightful, Task Pane-like Find feature: instead of forcing the user to click "Find Next" repeatedly, it finds ALL occurences of the search term and shows them in context, much like a super-index. This has saved me innumerable hours looking through 1,000+ page PDFs.
  
  The same could be done in Word for Find/Replace, and maybe even for spelling/grammar check.

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  I would be curious to hear which ones you did get rid of, and which no-one complained about.

• Anonymous
  June 14, 2006
  Show a "Spell check complete." message, then fade it away.
  
  Like the toast notification, but not locked to the bottom right corner since that's where I expect to see system-wide notifications and IM pop-ups.

• Anonymous
  June 14, 2006
  One of the new user interface elements I have really liked in the past year is the information bar that was introduced in Internet Explorer with Windows XP Service Pack 2.
  
  The information bar is able to convey information to the user in a highly visible fashion without disrupting the workflow of the user.
  
  Key to the visibility of the information bar is the location and color of the bar, which naturally draws the user to the information that is presented on it. The status bar, in comparison, due to it's location and color, I believe is not as effective in conveying important information to the user.
  
  I would recommend against dialogs that time out because if the user is distracted from the display for some period of time (for example, a telephone call), the dialog could expiry before the user had even seen it.
  
  I believe it is important for the user to know that a spell check is complete and I feel that that the information bar would be a natural UI element to convey that information.

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  I agree with Ben and others, a find in the spirit of the Firefox deisgn would be a great improvement. To me it would almost be worth the price of admission for that alone.
  
  Any comment Mr. Harris?
  

• Anonymous
  June 14, 2006
  This doesn't need to be all or nothing.  
  
  These two things are true:
  
  1) The "The spelling check is complete" dialog is rediculously annoying.
  
  2) I want to know when the spelling check is compete.
  
  Who went and decided that these two things are mutually exclusive and the only option is to choose the one that annoys the user the least?  
  There are plenty of examples where information can be displayed to a user without messing up his mental flow and/or making him click a button.  
  
  This version of Office is breaking new ground in user interfaces.  I don't understand how you can come up with a great UI concept like the ribbon to replace menus (which is no small feat) and can't find a way around purely informational modal dialog boxes.  I don't get it.

• Anonymous
  June 14, 2006
  The incremental find feature in Visual Studio is a nice variation on the Firefox text-search feature.
  
  in VS2005 type CTRL+I to active the incremental-search mode (the cursor changes to indicate the new mode). Then type what you are looking for. The selection jumps to the next occurrence automatically. ESC backs out.
  
  Adding a small search-pane à la Firefox would probably make more sense than the invisible text-field that visual studio uses. (heck, even Emacs shows you what you are typing while doing an incremental search)
  

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  Status bar anyone? Like, you know, for status notification.

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  I agree that Office's Find-Replace UI should be redone.  I like the text search pane method that Acrobat Reader uses.  
  
  (Firefox's Find bar is nice, but Word's Find-Replace functionality does more stuff, too much to squeeze into such a bar.)

• Anonymous
  June 14, 2006
  Escamillo, your workflow is not necessarily the same as the next guy's.  That's whay they interview more than one person when researching feedback mechanisms.  For instance, I'd prefer to only be notified if there are spelling errors.  I know I started the process, but forcing me to click OK when it's done is annoying.
  
  I think having extraneous dialog boxes only reinforces the average user's behavior of not actually reading the text before clicking.
  
  

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  Charlie Williams, you say, "I think having extraneous dialog boxes only reinforces the average user's behavior of not actually reading the text before clicking", but does this dialog really qualify as "extraneous"?  I'd say that the usability feedback showed otherwise.  Microsoft did remove the truly "extraneous" dialogs, but had to put this one back because it wasn't as "extraneous" as they had thought. ;-)
  

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  The comment has been removed

• Anonymous
  June 14, 2006
  Very interesting post Jason. After significant usability obstacle like that is removed from the application and you get so many requests to put it back - that usually means something is wrong with the original design. I think that’s exactly what happened in this case. Even more, as pointed out by Ben and others, Spell Check and Find and Replace are currently the biggest usability annoyances in beta2.
  
  I would hate to see the current implementation stick around for next 3-4 years until the next major Office release, so please do something :-)

• Anonymous
  June 14, 2006
  Escamillo >
  
  "I'd say that the usability feedback showed otherwise.  Microsoft did remove the truly "extraneous" dialogs, but had to put this one back because it wasn't as "extraneous" as they had thought. ;-) "
  
  They put it back because it's better than having no feedback whatsoever.  I'm simply saying that the best solution is somewhere in between no feedback and a modal dialog.

• Anonymous
  June 14, 2006
  Adobe Reader actually has 2 find interfaces. The most excellent Search task pane mentioned above (Shift+Ctrl+F), and the Find modeless dialog (Ctrl+F). I use both.
  
  As for spellcheck progress, why not use a Progress Bar. Put a % next to it, and when complete print "Spell Check Complete". The bar could be placed in the status bar or elsewhere in the interface (if you have the status bar hidden, how would you know the status?).
  
  The more I use Office 2007 the more I'm looking forward to Office 13, where the new interface will have matured nicely.
  
  

• Anonymous
  June 14, 2006
  I agree with the others that this should be a non-modal balloon tip. Yes, the spell checking is a modal task, but it doesn't mean every dialog it presents should be modal. Actually, I think none of the spell checking dialogs should be modal - they should all allow the user to make corrections in the text without closing the dialog, and the last dialog should definitly be a balloon - It's a notification.

• Anonymous
  June 15, 2006
  I agree a bit with Escamillo.
  
  It is simple. If the task the user is performing is modal, than there is no disturbtion with modal dialog.
  If the task runs in background, than modal dialog is not the right idea.
  
  I myself (as long as I think) do read the OK-only modal dialog boxes when the text is not long.
  The "spelling check is complete" can be read at a glance and therefore I don't think the dialog belongs to the unread ones.
  
  However, the fun is over when running on the server side. No modal dialog should be able to show up when the user is automated application.

• Anonymous
  June 15, 2006
  Charlie: Spell Check would tell you that "rediculously" is spelled wrong.  It's "ridiculously".

• Anonymous
  June 15, 2006
  I think it would be nice if the dialog was just a transparent overly that displayed for a second or two but which required no action to dismiss and which didn't bar users from immediately jumping to another task.  Just my $0.02.

• Anonymous
  June 15, 2006
  Non modal balloon tip please!! Or one of those do not show this agian check boxes. I really wouldn't miss it

• Anonymous
  June 15, 2006
  The comment has been removed

• Anonymous
  June 15, 2006
  PingBack from http://flyingsparks.wwwfiles.de/2006-06-16/bitte-ok-klicken/

• Anonymous
  June 15, 2006
  I dont agree with the "modal dialog leads to modal confirmation"-talk around here.
  
  Even if a task is modal it does not mean the confirmation-message has to be modal too. This would create another (second) modal dialog which is totally unnecessary.
  
  Pleace choose a way to tell people that the task is over without forcing them to focus, read, understand, move (the mouse) and klick once again...
  
  Thanks!

• Anonymous
  June 16, 2006
  > Charlie: Spell Check would tell you that "rediculously" is spelled wrong.  It's "ridiculously".
  
  Spelling correction much appreciated.  I feel you've contributed greatly to this conversation.  I'll think of your valuable input every time I spell "ridiculously" correctly.

• Anonymous
  June 16, 2006
  > Charlie: Spell Check would tell you that "rediculously" is spelled wrong.  It's "ridiculously".
  
  Spelling correction much appreciated.  I feel you've contributed greatly to this conversation.  I'll think of your valuable input every time I spell "ridiculously" correctly.

• Anonymous
  June 16, 2006
  Christian, in VS2003 (I haven't loaded 2005 yet), look for
  Incremental Search: mysearchtext
  on the status bar.  I hope they haven't removed that in 2005.
  

• Anonymous
  June 16, 2006
  The comment has been removed

• Anonymous
  June 18, 2006
  Mr Hunt, The SpellCheck is complete ... This message will self-destruct in 3 seconds.
  
  3
  2
  1
  
  Ka-boom
  
  (there goes your $1500 machine)

• Anonymous
  June 19, 2006
  My vote goes to a "Do not show this message again" checkbox.

• Anonymous
  June 27, 2006
  How many times do you see a dialog before you always click OK  ... how many people call for support saying ... "I got some kind of message ..." but they can't tell you what it said? Popups need to be informative in a way that lets you know that something other than standard behavior happened. A fade out balloon would be nice as an indicator that, well, everything worked just they way it should but we thought we should let you know. Don't start the fade until I do something else with the doc or if I click on the balloon make it wink out of existence. As for placement of the spellchecker dialog ... please scroll the document, don't move the dialog.
  
  Steve

• Anonymous
  March 23, 2007
  PingBack from http://learningtheworld.eu/2007/usability-analysis/

• Anonymous
  October 27, 2008
  PingBack from http://mstechnews.info/2008/10/the-office-2007-ui-bible/

• Anonymous
  June 01, 2009
  PingBack from http://uniformstores.info/story.php?id=17401

• Anonymous
  June 07, 2009
  PingBack from http://weakbladder.info/story.php?id=5790

• Anonymous
  June 13, 2009
  PingBack from http://thestoragebench.info/story.php?id=1460

• Anonymous
  June 17, 2009
  PingBack from http://thebasketballhoop.info/story.php?id=2209