Alan Alda’s If I Understood You: Summary and Practice

Key Ideas

1. Relating means allowing the listener to affect the explanation

Alda’s communication inquiry places relating at the center. In a direct interview about the book, he connects improvisation with observing another person and moving out of lecture mode. For a practical speaker, the question is whether the listener’s contribution can change what happens next.

Ana has prepared a detailed tour of her library tool. When a volunteer asks about a missing book, she could say that availability comes later and continue through the screens. That would protect the presentation’s order but lose the volunteer’s actual question. Instead, she can ask what they tell a visitor when the catalog lists a title that is not on the shelf. Their answer supplies a concrete starting point for the distinction she needs to explain.

This response does not require discarding preparation. Ana still needs accurate facts, a workable demonstration and time boundaries. Preparation gives her options; relating helps her select the useful option now. If the question concerns a feature she cannot verify, she can say so and arrange a follow-up rather than improvising a technical claim.

Before your next explanation, identify one point where you will invite a real question. Listen for something that could change your next example or the order of a passage. If every possible response leads you to exactly the same speech, the invitation may be ceremonial. A responsive conversation leaves room for new information while keeping a clear purpose and an honest boundary around what the speaker knows.

2. The mirror exercise makes pace a shared responsibility

In his own demonstration of the mirror exercise, Alda explains that the person leading must help the partner follow. The point for an explanation is practical: if the audience falls behind, repeating the same performance at the same pace may miss the part the speaker can change.

For an optional rehearsal, Ana and a willing colleague can try a brief version of the movement exercise, staying within comfortable movement and taking turns leading. Notice when a sudden change makes following difficult. Then apply the observation to a software demonstration. A rapid sequence of clicks can be as hard to follow as an abrupt movement, even when each individual step is simple to the expert.

Ana can pause after a search and ask a volunteer to describe what the result tells them. If they infer that every listed copy is available, the next move is to clarify the distinction before opening another screen. Slowing down helps only if it creates room to notice and repair misunderstanding; a slow lecture can still be disconnected.

The rehearsal is a way to notice coordination, not a test of a colleague’s empathy or a proven intervention for every audience. Participants can also skip movement and practice a verbal demonstration with pauses. The useful question is what the presenter can adjust to make the next step followable. Responsibility is shared, but the expert should inspect their own pace and assumptions before blaming the listener for failing to keep up.

3. Build on a contribution without pretending every claim is true

Alda also describes the improvisational principle of accepting and adding to a partner’s contribution. Its communication value lies in keeping a shared exchange possible. In a factual explanation, the principle needs judgment: acknowledging a person’s concern is different from endorsing an incorrect statement about how a system works.

A volunteer says that the new catalog is useless because a result does not guarantee a book is on the shelf. Ana could defend the software and begin listing its features. That might answer a claim while missing the concern underneath it: volunteers do not want to disappoint visitors. She can acknowledge that concern and build from it by explaining which screen checks a copy’s current status.

An original response might recognize the need to give a visitor a dependable answer, then demonstrate how to distinguish the title record from the copy record. Ana has accepted the practical goal without agreeing that the entire tool is useless. If the displayed status can lag behind an update, she should explain that limitation too. Maintaining connection should not require making the product sound more reliable than it is.

Try separating three things when a listener challenges you: the person’s goal, their experience and their factual claim. You may understand the first two while needing to correct the third. Ask a question if you are unsure which part matters most. This keeps the exchange open for learning while preserving the responsibility to explain the subject accurately and to acknowledge a genuine fault when one appears.

4. Translate jargon by finding the experience it names

In Alda’s own discussion of jargon, he distinguishes its efficiency among specialists from the distance it can create with other audiences. The practical question is what concept a listener needs, and how to make that concept accessible before relying on the specialist label.

Ana begins with synchronization between the local catalog and the circulation database. Volunteers may understand the words individually but not know what the phrase implies for a visitor waiting at the desk. She can explain that a returned copy’s status must update before every screen shows the same information. Then she can name synchronization as the process that keeps those records aligned. The term now points to something the volunteers can discuss.

Keep a precise word when it helps. Avoiding all technical language can leave people unable to ask a useful follow-up or find the right setting later. Ana can display the actual screen label and connect it to the plain explanation. The aim is shared understanding of the term, rather than either displaying expertise or hiding it behind a loose analogy.

Before a demonstration, choose three expressions your audience may not know. For each, write the relevant real-world event, the term and one consequence for the listener’s task. Ask a colleague outside your field to explain the relationship back in their own words. If they reproduce the label without understanding its effect, provide a concrete instance. The test is usable meaning, not whether the audience can pronounce your preferred vocabulary.

5. A concrete story should open a question, not close it prematurely

The publisher identifies storytelling among the approaches Alda explores. For a practical explanation, a story can give unfamiliar information a situation and a purpose. Its usefulness depends on how well the situation connects to the actual concept. A compelling account can still leave a mistaken impression if the speaker never checks where the listener has taken it.

Ana can begin with an invented visitor looking for a particular gardening book. The title appears in the catalog, but one copy is already borrowed and another belongs to a different branch. The story creates a reason to distinguish a title from a physical copy. Ana can then show the relevant records and ask which information the volunteer would need before promising to fetch the book.

The example should remain small enough to inspect. Adding a dramatic visitor, an emotional conflict and an elaborate rescue could distract from the two-record distinction. It might also imply that the system handles every exceptional case shown. Ana should label a made-up scenario as practice and use real verified behavior when demonstrating the software itself.

After the story, ask a transfer question: what would change if the visitor wanted a different edition or a copy from another branch? Their response shows whether they understood the distinction or merely remembered the ending. This original check prevents a smooth narrative from becoming the only evidence of understanding. Use a story to make participation easier, then let the listener’s response reveal where the explanation needs further work.