This case explicitly reveals and names for students the four communication problems that listeners have during a technical talk, and the four well-known, standard (sets of) techniques that good speakers use to anticipate and mitigate those problems. (Approaching talks in this problem-oriented way makes appropriate technique a matter of social responsibility, not merely public speaking skill.) Although general, this four-problem framework applies easily and directly to almost any classroom (or current-events) science topic. This means that examples for modeling or practicing the technical-talk techniques can be easily found in your on-going lessons.
SUGGESTIONS FOR EACH PROBLEM:
(A) Structure (Order).
The advice (in the right-hand column of the "Tips" table below) to clearly reveal each talk's structure and milestones (verbally, or with an introductory "table of contents" slide) appears in every book on how to give talks. But you will probably need to explain to students psychologist Donald Norman's related tip on "scope/depth tradeoffs." Shopping provides a familiar example:
When looking for wire at the hardware store, you face a "narrow and deep" situation--you can ignore all aisles except for the one marked "electrical" (narrow), but then you have to face many specific "deep" choices (copper or aluminum, coated or uncoated, braided or solid).
When shopping for ice cream, however, your situation is "broad and shallow"--31 flavors confront you, but then you only have to pick one scoop or two.
To succeed psychologically, a good technical talk must follow one of these same two scope/depth alternatives. Broad-ranging talks cannot get too detailed, while deeply detailed talks must stay narrowly focused.
Review (Rereading).
In a movie, viewers can easily tell when the action shifts from scene to scene. Likewise, the audience of a technical talk needs to easily tell when the speaker shifts from topic to topic. Student speakers therefore must learn to help their listeners topically by paying attention to their own "topic transitions" and signaling the audience about them. Using a personal story board, perhaps constructed of one sticky note per (sub)topic pasted on a large sheet of paper for easy rearrangement, is the standard, Disney-pioneered way of mapping out the "scene changes" (topic transitions) in a technical talk (so that the speaker can be sure to disclose them).
Understanding (Complexity).
As noted above, technical talks are much more dense with data than is ordinary speech. Most people can absorb dense information more easily by seeing it than by hearing it only. So most good technical speakers supplement their spoken words with things that their audience can also see: exhibits, handouts, pictures, summaries, or slides.For very discussable, visually clever, gender-neutral examples of data-dense handouts or charts, visit http://www.cookingforengineers.com. This site diagrams dozens of kitchen recipes to concisely reveal which tasks to perform on which ingredients in which order.
For help planning good slides, the "Simple Tips" page (below, and for students) summarizes rules of thumb found in dozens of book-length treatments of slide design. If you wish to tap just one of those many published slide-advice discussions with high relevance to science class, consult Edward R. Tufte, Visual Explanation (Cheshire, CT: Graphics Press, 1997), pp. 38-53, where Tufte elegantly shows and evaluates the actual slide used to justify the launch of space shuttle Challenger, which exploded on January 28, 1986.
Delivery (Presentation).
No matter how thoughtfully a speaker plans the structure, topic transitions, and data density for their technical talk, they still must actually deliver it aloud to their audience. The tips on the student chart for this delivery problem are rather more specific than for the other three problems, and of course students must physically try them out through personal practice to benefit from them. You can helpfully model these tips by presenting from a few sample slides, since slide/speech coordination often defeats beginners. Sticky-note prompts placed on the slides themselves can help nervous speakers manage the rough spots. "Casing the room" is another helpful behavior that you can model here--checking the lights, projector alignment and focus, and sight lines from the corners and rear--before launching into the prepared talk.
| Technical Talk Tips | ||
|---|---|---|
| Problem | Technical writing, where the audience can... | Technical speaking, where the audience must... |
| STRUCTURE | Read in any order. | Listen in the speaker's order of presentation. |
|
||
| REVIEW | Reread any passage. | Rely on the speaker to repeat if appropriate. |
|
||
| UNDERSTANDING | Study and gradually understand. | Understand on the first hearing. |
|
||
| DELIVERY | Read at any pace. | Listen and absorb at the speaker's pace. |
|
Begin each slide with a headline sentence, not just a topic phrase.
Examples:
Drosophila [bad; too vague]
Drosophila Hmx gene [bad; so what?]
Drosophila Hmx gene directs mouse
inner-ear development. [good; asserts an interesting claim]
Use large fonts and simple layout for easy reading.
Rules of thumb:
Use no more than 8 words/line, 8 lines/slide maximum.
Can you read it easily if you stand over it on the floor?
Choose images carefully not to decorate but to reveal
Consider progressive disclosure when sequence is important
(sticky notes can help here).