Back to HackerTubeYouTubeNovember 12, 2026Duration:1:03:42

How to Speak So Your Ideas Can Be Heard

How to Speak

MOMIT OpenCourseWare

Full transcript

English
Watch on YouTube
Contents

Speaking is a skill you can build

Source 00:19

Ideas need to reach other people before they can be valued. Professor Winston argues that speaking and writing can have an outsized effect on that journey, and that effective communication depends heavily on knowledge and practice. His story of being a better skier than an Olympic gymnast who was new to skiing illustrates the point: talent in one activity does not replace practice in another. It is an anecdote, not an experiment.

His aim is not to prescribe a single personality. Watch speakers you find effective, ask what they do, and gradually build a repertoire that fits your own style. He begins by asking the audience to close laptops and phones: reading competes with listening, he argues, and screens may distract neighbors and the speaker. His “one language processor” explanation and reference to studies are claims in the lecture, without a specific study identified.

Give listeners a promise and a route back in

Source 04:38

Winston advises against opening with a joke: people are still settling in and adjusting to the speaker's voice. Instead, make an empowerment promise: tell them what they will know or be able to do by the end. His own promise is that a technique from the hour might someday make a consequential difference, perhaps in a job interview. Watch the opening advice.

Four habits help listeners follow an argument:

  • Cycle through the idea. Return to it from different angles so someone whose attention wandered has another chance to understand it. Winston's estimate that 20% of a room may be momentarily lost is a rule of thumb, not a measurement established here.
  • Build a fence around it. Explain what the idea is and what similar things it is not. An arch and a near-arch make the distinction visible; in a technical talk, compare an algorithm's linear growth with another's exponential growth.
  • Use verbal punctuation. Number transitions and recap where the audience is: “That was the second idea; now for the third.” These landmarks let a listener rejoin the argument.
  • Ask a real question. Avoid one so obvious that answering feels embarrassing or so hard that no one can respond. Allow silence: Winston demonstrates a pause of roughly seven seconds.

Prepare the room for attention

Source 10:13

Winston favors 11 a.m. in his MIT context, when students are awake and it is not just after a meal. He also favors a brightly lit room, a visit beforehand to discover awkward sightlines or equipment, and an audience that fills more than half the space. These are practical, context-dependent judgments rather than universal rules. Watch the discussion of the room.

Use boards and physical objects to make reasoning visible

Source 13:37

For teaching, Winston likes a board because drawing slows the pace and leaves a persistent object to point to. A speaker can build a diagram with the audience rather than reveal a finished result too quickly. He also notes that pointing gives the hands a purpose, though gestures and posture carry different meanings across cultures.

A prop can make an abstract idea memorable. Winston spins a bicycle wheel and asks the audience to reason about its response to a torque. Instead of remembering a hand rule, isolate the taped piece of the wheel and think through how its motion changes. In another example, an instructor brings a heavy pendulum ball close to his face and releases it; the expected return illustrates conservation of energy while the audience watches in suspense. Winston warns viewers not to try that demonstration at home: an accidental push changes the conditions. Watch the wheel demonstration.

View full image

He speculates that watching physical action may engage “empathetic mirroring,” while acknowledging that the slower pace may explain the appeal. He labels the former a fringe view; it should not be treated as established by this lecture.

Design slides for listening, not reading aloud

Source 23:54

Slides can efficiently expose ideas in a conference or job talk, but Winston sees too many slides and too many words as recurring problems. He advises against reading a slide aloud, recommends keeping the speaker near the visual, and strips away decorative backgrounds, repeated logos, unnecessary titles and bullets. Large type—he suggests around 40–50 points—also forces a useful limit on density.

His explanation is that reading and listening compete for attention. He recounts a student's small experiment with fraternity freshmen in which slide text was remembered better than spoken material; that narrow anecdote is not proof of a general effect. When text is worth showing, pause and give the audience time to read it.

A laser pointer can pull the speaker away from the audience. An arrow and number embedded in the visual can identify the same location while preserving contact. Print the slides and lay them out to inspect their overall density and whitespace. Winston allows one deliberately complex slide when complexity itself is the point: his example depicts the tangled relationships involved in governing Afghanistan. The exception works only if the audience understands why it is there. Watch the slide examples.

View full image

Inspire learners and give them ways to think

Source 36:49

In an informal survey, Winston heard incoming students recall teachers who told them they could succeed; senior faculty recalled someone who helped them see a problem differently. Across groups he heard about passion. These recollections suggest ways to encourage learners, rather than a controlled test of teaching methods.

His map-coloring example combines a promise with curiosity. He shows a program assigning colors to neighboring states and says its initial approach would take longer than the solar system's lifetime. A small adjustment makes the calculation finish in seconds; the promise is that students will understand the change during the class. The example turns an abstract resource-allocation problem into a question worth answering. Watch the example.

View full image

Winston's own model of teaching thinking centers on stories: give learners relevant stories, questions to ask, methods of analysis, ways to combine stories, and ways to evaluate reliability. This is his framework for instruction, not a proven definition of thought.

In a job talk, connect a vision to evidence of work

Source 41:25

For oral examinations, Winston identifies two common failures: not situating the research—explaining its history, field and significance—and not practicing enough. Rehearse with people unfamiliar with the work. Close colleagues and supervisors may unconsciously fill gaps because they already know the answer.

For a faculty job talk, two colleagues told him they wanted to see both a vision and evidence that the candidate had accomplished something, within roughly five minutes. Winston's practical structure is:

  1. State a problem people care about and what is new about your approach.
  2. Map the steps needed to reach a solution, then identify which steps you have completed.
  3. End by enumerating your contributions, mirroring the roadmap at the start.

His own research example frames human intelligence through symbolic descriptions and stories. That is his research perspective, used here to demonstrate how a vision can be stated, not a settled comparison of species. The five-minute window is advice from his colleagues, not a universal hiring rule. Watch the job-talk framework.

Give the audience handles for remembering your work

Source 48:18

Winston's five-part “star” provides handles for an idea: a symbol, a slogan, a surprise, a salient idea and a story. His arch-learning work supplies an example: an arch is the symbol; “one-shot learning” the slogan; learning something definite from an example the surprise; a near miss—the almost-arch that exposes a missing condition—the salient idea; and the account of how and why the system works is the story. A memorable package helps people find the idea again; it does not substitute for the work itself. Watch the five handles.

Leave your contribution visible and end deliberately

Source 53:01

Winston recommends recognizing collaborators at the beginning and leaving a final slide labeled “contributions” on screen during questions. A generic “questions” or “thank you” slide gives up that space; a long list of names at the end can obscure what the speaker contributed. His advice is to make the final visual a reminder of what was done.

For final words, a joke may work better now that the audience knows the speaker. Winston personally dislikes ending with “thank you,” because he hears it as implying that people stayed only out of politeness. He shows political benedictions and other familiar ending conventions, then offers another option: sincerely salute the audience by saying what you valued about the occasion. This is a rhetorical preference, not a prohibition on gratitude. The broader lesson is to choose an ending that signals completion and reinforces the relationship with listeners. Watch the closing examples.