Message clarity and public speaking
Get to the Point! Summary: Joel Schwartzberg's Message Method
*Get to the Point!* teaches communicators to identify a meaningful position, support it, and deliver it clearly instead of merely presenting information about a topic.
One-Sentence Answer
Get to the Point! teaches communicators to identify a meaningful position, support it, and deliver it clearly instead of merely presenting information about a topic.
What The Book Is About
A project update can describe a great deal of activity without helping anyone decide. Schwartzberg's subject is the missing point: the statement that gives those details a purpose. The book applies that question to speeches, meetings, slides, emails, and other work communication.
This guide uses the expanded second edition, identified by the current Berrett-Koehler product record. The publisher's distributor lists the paperback's June 17, 2025 release in its 2025 business catalog. Earlier editions use the subtitle Sharpen Your Message and Make Your Words Matter. Do not confuse Schwartzberg's book with similarly titled works by other authors.
Who Should Read It
- An analyst whose thorough presentation ends with “What are you recommending?”
- A manager who wants an email to make a request unmistakable without sounding abrupt.
- A speaker who keeps adding examples because the main argument is not yet clear.
- A student or specialist learning to translate knowledge into a contribution for a particular audience.
Readers needing a complete system for structuring a long analytical document may prefer The Pyramid Principle. Readers facing a disagreement about values or trust will need more than a sharper sentence. Point-making can clarify a position; it cannot establish consent, prove unsupported claims, or replace listening when another person needs to shape the problem.
Main Summary
Schwartzberg distinguishes a topic from a point. A topic names the territory of a communication. A point takes a position within it, giving the audience something to consider, evaluate, or act on. Knowing the topic is therefore an insufficient basis for preparing a useful presentation. Speakers must decide what they want the information to mean for the people receiving it.
His approach begins before delivery. The communicator identifies the actual contention, improves its clarity and value, and chooses material that supports it. A confident manner cannot rescue a message that never becomes specific. A memorable story can also fail if listeners remember the incident but cannot connect it to the intended conclusion. The author explains the core distinction on his book page and offers practical tests in his Toastmasters article on making a point.
The second edition expands the treatment for contemporary workplace communication. Its publisher describes coverage across written and spoken channels, openings and closings, evidence and stories, public-speaking concerns, and the supportive use of AI. This guide concentrates on the central task of identifying and defending the message. It does not invent a new numbered model or present the author's later articles as chapters of the book.
Our original case follows a university technician requesting protected equipment-maintenance time. The first version reports faults, repair tickets, and staff effort. The improved version makes a proposal and explains its expected benefit, while retaining the uncertainty that a decision maker needs. The examples and exercises are editorial applications rather than incidents from Schwartzberg's text.
The book is most useful when your material is relevant but your audience cannot locate its purpose. Its limit is equally clear: an elegant point remains a claim that needs adequate grounds. Use clarity to expose the reasoning and invite a meaningful response, not to make an uncertain conclusion sound inevitable. A well-made point should make disagreement more precise as well as make agreement easier.
Key Ideas
1. Name a position rather than announce a subject
Schwartzberg defines a point as a contention that can be argued and supported, rather than a title, theme, or subject. His “I believe that” test asks whether the proposed message can follow those words as a complete thought. This is a preparation device for finding the claim; a final email does not need to begin with that phrase. Grammatical completeness is a useful starting test, not proof of truth.
Our technician initially labels a presentation “Laboratory maintenance.” That tells the committee what the slides concern. It does not reveal whether the technician wants more equipment, different staffing, revised access hours, or simply acknowledgment of recent problems. A working point might be: reserving a short weekly maintenance window should reduce avoidable interruptions during teaching sessions. The sentence gives listeners something to examine.
Try stating the point before opening the slide software. If you can produce only a noun phrase, ask what you want to propose about it. If you produce several competing recommendations, decide which one this communication must carry and which belong elsewhere. The decision may reveal that you need two conversations with different people.
Do not force a recommendation before you understand the issue. Sometimes your legitimate point is that a decision needs further evidence, with a specific proposal for obtaining it. The improvement is taking responsibility for what you are saying, including its limits. A clear point can be cautious; it simply should not leave the audience guessing what contribution you intend to make.
2. Make the point useful enough to deserve support
The author's point-making article distinguishes a real contention from a truism. A statement that nobody could reasonably question may sound agreeable while contributing almost nothing. The same article warns against crowding multiple ideas into one point. Together, those tests push a communicator toward a specific claim with a reason for the audience to care, rather than a polished statement of general virtue.
“Equipment should work reliably” is unobjectionable in our example. It does not help the committee choose a maintenance policy. The proposed protected window identifies a possible intervention. The technician can explain what it is expected to change, which classes would lose access, and what would count as an unacceptable disruption. Those details make the proposal both useful and challengeable.
Our editing exercise is to ask what a thoughtful opponent would say. Perhaps interruptions arise mainly from training gaps, so a maintenance window would not address them. Perhaps the timing would disadvantage a group with limited laboratory access. These objections reveal what the point must explain. They may also require revising the recommendation rather than merely improving its wording.
Avoid making a claim stronger by adding unsupported certainty or a string of favorable adjectives. “Our transformative plan will eliminate downtime” is less responsible than a bounded proposal with a reasoned expectation. Keep one main contention visible, describe its expected value in terms the audience can assess, and preserve the relevant tradeoff. That gives the listener a basis for a decision instead of a slogan to applaud.
3. Choose evidence and stories by the work they do
The second edition's publisher describes using stories, examples, and data to highlight the point. Schwartzberg makes the same distinction in his essay on purposeful storytelling, listed in his author-maintained article collection: an entertaining anecdote and an argument-serving story are different achievements. Our application is to ask what each piece of material helps listeners understand or evaluate.
The technician has a vivid account of a failed demonstration and a spreadsheet of service tickets. The account shows what an interruption feels like for an instructor and students. It cannot establish how frequently preventable faults occur. The ticket record may help answer that question, but only if it distinguishes recurring maintenance issues from unrelated equipment failures. Each kind of material has a different evidential job.
Build the presentation around the reasoning required for the proposed choice. Keep the relevant incident brief, show the pattern you can actually support, and explain the connection to the recommended maintenance window. If the data do not establish that connection, say so and propose a limited trial. Do not let a moving story stand in for missing evidence.
A useful editing pass labels each section: illustrates the problem, supports the expected benefit, explains the tradeoff, or answers an objection. Material with no clear purpose may belong in backup notes or a separate conversation. This is a suggested editing exercise, not a named book framework. The goal is a better supported point with less distraction, rather than a presentation stripped of necessary context.
4. Carry the same message through different channels
Schwartzberg applies point-making beyond speeches. The author and publisher explicitly include emails, meetings, slides, and work chats. That breadth matters because a clear spoken recommendation can disappear when translated into a vague subject line or a dense slide. The communication should retain its purpose even when its form and level of detail change for a different setting.
In our university example, the committee presentation may need a short explanation of the problem, the proposal, and the conditions of a trial. An email to the laboratory coordinator may need the proposed timetable and a request to identify access conflicts. A notice to students should explain when equipment is unavailable and where to report a problem. These messages concern the same project, but their readers need different actions.
Our exercise is to draft the main sentence for each audience before copying material between channels. A subject line can state the decision requested rather than simply “Maintenance update.” A slide heading can explain what the displayed evidence supports rather than repeat a category label. The body then supplies the detail needed to evaluate that specific message.
This does not justify repeating identical text everywhere. Public announcements, technical notes, and private requests have different obligations, including accessibility and confidentiality. Also check that a shorter version has not removed a condition that changes the meaning. Consistency concerns the underlying claim and its boundaries. The useful question is whether each recipient can tell what this communication asks of them without reconstructing the entire project history.
5. Rehearse for understanding rather than the appearance of fluency
The book's emphasis on having a point gives rehearsal a concrete purpose: discovering whether the audience can actually find and follow the message. Smooth delivery is helpful, but it is a poor substitute for a listener who understands the proposal. Schwartzberg's published speaking advice also treats a point as something to identify and champion, making clarity a practical preparation task.
Ask a colleague to hear the technician's short explanation without first telling them the intended conclusion. Then ask what decision they think the speaker wants and what reason supports it. If they remember only that laboratory staff are busy, the presentation has communicated effort rather than the proposal. That feedback identifies a message problem before anyone spends time polishing gestures or formatting slides.
Practice with an interruption too. The colleague can ask why the maintenance window should take priority over access. Answer the question directly, acknowledge the tradeoff, and return to the proposal only if it still fits. Rehearsal should expose missing reasoning, not train the speaker to overpower objections with a memorized line.
Use feedback proportionately. One listener may lack context or have misunderstood a term, so investigate the mismatch rather than treating any criticism as a command. Readers with speaking anxiety may also need gradual practice or dedicated support. The point-making method supplies a clearer task to practice; it is not a treatment claim. A successful rehearsal ends with a message that another person can accurately describe and meaningfully question.
Practical Takeaways
- Write the point as a complete sentence before preparing the medium that will carry it.
- Use the “I believe that” test privately to identify sentence fragments masquerading as messages.
- Replace a general virtue with a specific claim that explains what should change and why it matters.
- Name a reasonable objection and check whether your evidence actually addresses it.
- Give each example, chart, or story an explicit job in supporting or qualifying the point.
- Rewrite the message for the recipient's actual decision or task instead of forwarding every detail.
- Ask a practice listener to state your recommendation and its strongest reason in their own words.
- Preserve important limits when shortening the communication; clarity includes uncertainty and conditions.
How To Apply It
Rewriting a request for laboratory access time
Start with a fictional draft: the technician lists recent faults, explains how hard the team has worked, and attaches a long repair history. The recipient might sympathize yet still not know what is being requested. The first revision supplies the missing proposition: test a protected weekly maintenance window to address preventable interruptions.
The technician then checks the grounds. Which incidents were preventable through scheduled maintenance? Which had unrelated causes? If the existing record cannot answer, the proposal becomes a limited information-gathering trial rather than a claim of guaranteed savings. That change strengthens the honesty of the message while making the decision smaller and clearer.
The final request identifies the proposed window, the access tradeoff, the person who can approve it, and the information to review afterward. The technician attaches the relevant evidence and leaves the complete ticket history available for questions. A colleague reads the request and explains it back. If the colleague mistakes it for a request to purchase new equipment, revise the opening before sending.
These steps are this guide's original application, not a reproduced checklist from the book. A reader can use the same exercise on a project recommendation, an interview answer, or an event invitation. If the issue requires exploration before a position is possible, make the immediate request about that exploration instead of pretending the conclusion is settled.
Best Related Books
- The Pyramid Principle is useful when your point needs a larger logical structure of supporting arguments and evidence.
- The First Minute focuses on opening work conversations with enough context and a clear purpose. Pair it with the earlier task of deciding what your point actually is.
- Brief examines concise workplace communication more broadly. Schwartzberg provides a particularly direct entry through the distinction between a subject and a contention.