Welcome to MSDN Blogs Sign in | Join | Help

Thinking aloud

Windows Vista Speech ToolbarSpeech recognition in Vista works well for me. Dictation accuracy is very high - especially since I flicked the switch to train it on my emails and documents - and the correction experience is smooth and efficient. But I hardly use it. I find it very difficult to dictate to my computer.

WTF? Typing is easier than speaking?

Yes. I can't speak the way I write. If I'm typing, I'll begin a sentence without knowing how it's going to end, future phrases will form as I finish typing previous ones. I'll pause, go back, select text, delete it, write again. It feels almost as if hitting the keys is a direct extension of the thought process. 

If I'm dictating, there's no such flow. I'll begin a sentence (having got over the minor panic triggered by the Listening microphone UI over a blank document) and the phrase will appear - correctly - on my page, but saying it out loud has corrupted the thoughts that would have helped complete it. I have to step back and think hard about what should come next. Every phrase forces a little mental reboot.

I think what's going on - in addition to my inability to think in complete sentences - is that my thought processes while typing have habituated themselves to the gated speeds of my motor operations. The extra time is valuable and they use it to do the work of sounding out the current phrase in context, thinking up the next phrase, and so on. So typing actually greases the wheels of forming the right words and sentences. That's missing when I dictate, and I find it quite paralyzing.

Surely many keyboard users, even very slow typists, will be reluctant to move to speech recognition systems - even high accuracy systems - because of the advantages of the thinking on-the-side that we seem to do while hitting keys. The standard words-per-minute (wpm) metric for text input is usually measured over copying pre-existing texts. The text creation part is assumed to be equal to each. But my wpm drops dramatically when I dictate, because the creation processes that work with typing are unavailable to me. But what does the wpm look like when you do have them available?

Many users of speech recognition (and of transcription-taking secretaries) have obviously overcome this. Most visibly, Richard Powers, a novelist who wrote the 2006 National Book Award winner using speech recognition on his TabletPC, trained himself after years of typing:

I needed weeks to get over the oddness of auditioning myself in an empty room, to trust to the flow of speech, to learn to hear myself think all over again. 

He broke through - and argues now that typing is the obstacle to the thought process:

What could be less conducive to thought’s cadences than stopping every time your short-term memory fills to pass those large-scale musical phrases through your fingers, one tedious letter at a time? You’d be hard-pressed to invent a greater barrier to cognitive flow.

Is the grass really greener over there? I'd love to know. If anyone has done it, please send a comment. I'm also going to try it out for myself. Over the next few weeks, I'll be training myself to think aloud.

Published Wednesday, August 01, 2007 6:50 PM by Stephen Potter
Filed under:

Comments

Wednesday, August 15, 2007 10:08 PM by jeremiah

# re: Thinking aloud

As far as I know, that a think aloud is a great strategy to test/use to slow down the reading process and let students get a good look at how skilled readers construct meaning from a text.  Many of us developed our skills as readers implicitly, by simply doing a lot of reading of all sorts of texts and <a href="http://www.aftermarketperformanceparts.com/index.html">index</a>; after all, reading is a passion for us.  Therefore, when we teach reading at the secondary level, we need to keep in mind that we must take what we know and do implicitly and make it explicit for our students, especially for our struggling readers.  Below is a beginning list of what skilled readers do implicitly; we need to help our students learn and apply these skills/strategies on a regular basis to improve their interactions with text.

Here are my tips:

*  Formulate questions prior to reading and in response to the text.

*  Make, confirm or revise predictions based on information presented in the text.

These are that things that a skilled readers do while they're reading: Activate prior knowledge, Set a purpose/reason/goal for reading, Decode text into words and meanings, Make personal connections, Make predictions, Visualize, Ask questionsMonitor understanding and summarize, Apply what has been learned.

Hope these things would help.

Friday, September 28, 2007 3:02 PM by Tanya (aka NetChick)

# re: Thinking aloud

Hi -- This is the same reason why I continue to write a conventional blog, rather than provide podcasts.  I know video podcasts would be much more interesting to my visitors, but I write far better than I dictate out loud.

:)

Friday, September 28, 2007 4:21 PM by Stephen Potter

# re: Thinking aloud

Hi Tanya, yes it's much easier to hide behind text isn't it (and maybe speaking the text removes the veil a little)? I wonder whether professional actors treat speech dictation systems any differently.

BTW, I got a lot of mileage out of your sister-in-law's run-in with your system at work (http://blogs.msdn.com/spokenword/archive/2006/05/22/the-shouting-match.aspx) I'd love to know if you have any other interesting audio files.

Stephen

New Comments to this post are disabled
 
Page view tracker