Claude Cowork — Win Back 15 Hours a Week — 8. Presentations & Materials That Convince

18 min read min de lecture
Chapter 08

Presentations & Materials That Convince

Chapter 8 of 10 · 80%

Chapter objectives

  • Structure the message before the slides: one idea per slide, a title that asserts
  • Turn an existing document into a presentation without rewriting everything
  • Prepare speaker notes and answers to the likely questions
  • Adapt the same deck to different audiences without the substance drifting

The deck is not the message

The typical failed presentation doesn't lack work, it lacks hierarchy: everything is in it, so nothing stands out. Thirty-four dense slides is a document being projected, not a presentation — and the audience, ordered to read and listen at the same time, does neither properly. The founding rule of this chapter fits in one sentence: you design the message, then the talk, then only the slides. The visual deck is the last step, never the first.

That's excellent news for you: message design is exactly the type of work that delegates well. Clarifying the objective ("what should the audience do on the way out?"), finding the angle, ordering the arguments, calibrating for twenty minutes — all structuring tasks where your digital coworker excels, provided it receives a good brief. And you'll see that an existing document — a note, a business proposal, a chapter 3 report — already supplies 80% of the material.

Start from the end: the objective and the outline

Before any slide, answer three questions: what should the audience remember (a single sentence), what should it feel (confidence? urgency?), and what should it do next (book an appointment, sign, approve a budget). These three answers form your presentation's contract; anything that doesn't contribute to it is a candidate for cutting. Put this contract in your brief along with the audience, the duration and the context, and ask for the outline — not the slides, the outline.

PROMPT
I must present my accounting firm's advisory offer to a group of 12 building tradespeople. Duration: 20 minutes + 10 of questions.
The presentation's contract:
- To remember: "a supported tradesperson saves time and sleeps soundly"
- To feel: confidence, zero intimidating jargon
- To do: book an individual discovery appointment
Context: they know little about accounting firms, some have had bad experiences (opaque billing). Here is our existing offer note: <paste>.
Propose a presentation outline in 8-10 slides maximum: for each slide, the title phrased as a complete message and the single idea it carries. No detailed content yet. End with what you would cut from the offer note and why.
The title of each slide must be a complete assertion, not a label. "Our fees" teaches nothing; "A fixed monthly package, no year-end surprises" already carries the message — even a distracted viewer who reads only the titles receives the essence of your presentation.

One idea per slide

Once the outline is approved, have the content produced slide by slide with a strict constraint: one idea per slide, twenty-five words maximum on screen, the rest goes into the speaker notes. This constraint feels brutal to slide-document veterans, but it changes everything: the audience listens to you instead of reading the screen, and each slide becomes again what it should be — a visual support, not a teleprompter. If an idea doesn't fit on an airy slide, there are two ideas: split.

For numbers, same discipline: one strong figure per slide, staged, rather than a full table. "15 hours won back per week" in large type strikes home; the calculation table that justifies it goes in the appendix, ready to be shown if someone asks. You can also ask, for each numerical result, which representation would suit it — trend, breakdown, comparison — exactly like the analysis report-back in chapter 4. The deck gains in force what it loses in exhaustiveness.

PROMPT
Here is the approved outline of my presentation: <paste the 9 title-messages>.
Now write the content of each slide:
- On screen: 25 words maximum, a single idea, possibly one strong figure highlighted
- In speaker notes: what I say during the slide, 60-80 words, oral and natural tone, with a transition to the next slide
- Flag the slides where a simple visual would help and describe it in one sentence
Constraint: no accounting jargon without its plain-language explanation. Audience: tradespeople, some wary of accounting firms.

Speaker notes: your safety net

The speaker notes generated with the slides deserve a personalization pass: read them out loud and rewrite whatever doesn't sound like you. A brilliant phrase in writing can be unpronounceable out loud; a simple turn of phrase you use every day will always land better than an elegant borrowed sentence. Then ask for a "backup plan" version: for each slide, the key sentence in one line — that's what you'll glance at if you lose the thread, not the full paragraph.

Marc discovered an extra use: assisted rehearsal. He pastes his notes and asks for an estimated timing section by section, then the questions a nitpicky listener would ask at each step. Twenty minutes of rehearsal with that feedback are worth a real dress rehearsal — and on the day, almost nothing truly surprises him.

Anticipating questions: the mock session

The ten minutes of questions do more for the audience's decision than the twenty minutes of presentation: that's where your solidity is judged. Prepare them like a mock exam: ask for the twelve most likely questions from your specific audience — including the three most uncomfortable — each with a thirty-second answer and the posture to adopt. For the wary group of tradespeople, the question "why do your colleagues bill surprise extras?" will come; better to have rehearsed it than to discover it in public.

Personally verify every figure and every factual claim in the deck before the big day — rates, deadlines, regulatory references. A single factual error spotted by the audience contaminates the credibility of everything else. It's the chapter 4 discipline: the tool produces, you validate what commits you.

Adapting without drifting

A successful presentation has a second life: the version sent afterwards to those who want to reread, the short version for another appointment, the internal version to train the team on the pitch. It's the single-source principle from chapter 3, applied to decks: you start from the same substance, you adapt the angle and the level of detail, and the figures stay rigorously identical everywhere — a prospect comparing two versions must never find two different stories.

Projection deckOne idea per slide, 25 words on screen, staged figures, the talk carries the content. Unusable without the speaker — by design.
Document sent afterwardsThe same substance, but self-supporting: complete sentences, context restored, numerical appendix included. Reads without you, in five minutes, losing nothing of the message.

Everyday materials: beyond the big appointment

The method isn't just for big occasions. Every month the firm produces more modest materials that benefit from the same principles: the three slides presenting an annual statement to a client, the deck for the internal training on the new software, the visual summary page that accompanies a business proposal. Each time, the same reflex: presentation contract first, title-messages next, one idea per page — the short version of the method takes fifteen minutes for three slides.

Marc even applied the logic to the firm's most-read document: the annual accounts presentation. Before, it was a stack of tables the client leafed through politely; now, three visual pages open the document — the year in three figures, the trend, the recommendation — and the tables follow in the appendix for whoever wants to dig. The year-end meeting went from an endured lecture to a conversation: the client arrives having understood the essentials, and asks better questions. Presenting better also means listening better.

The pitfalls of the assisted deck

First pitfall: generating the slides before the message. You'll get a generic deck, pretty and hollow — the order design → talk → slides is non-negotiable. Second pitfall: the deck that knows everything. Wanting to show everything means making nothing stand out; your best weapon is the cut, and explicitly asking "what would you cut?" is often the most useful part of the brief. Third pitfall: reciting. Speaker notes are a net, not a script; if you read them word for word, you might as well send the document. Rehearse until you can speak from the one-line key sentences — that's where you become convincing.

One last reflex: after each presentation, note while it's fresh what worked and the unexpected questions received, and feed those lessons back into your standard presentation brief, filed in the library. The firm's tenth presentation will be prepared in an hour, not a day — and it will be better than the first.

🛠️ Your turn

Context

The appointment with the tradespeople's group is in ten days. Marc starts from the firm's offer note (3 pages) and must produce: a deck of 9 slides maximum, his speaker notes, the question prep, and the document version to send afterwards. Choose your own upcoming presentation — client pitch, management update, internal training — and run the full method.

Instructions

  1. Write your presentation's contract: to remember (one sentence), to feel, to do — then have the outline generated as title-messages (8-10 slides max) from your existing document.
  2. Challenge the outline: ask "what would you cut and why?" and make the final cuts yourself.
  3. Have the content produced slide by slide: 25 words max on screen, speaker notes of 60-80 words, visual suggestions.
  4. Read the notes out loud, rewrite what doesn't sound like you, and ask for the backup plan in one-line key sentences.
  5. Prepare the mock session: the 12 likely questions from YOUR audience (including 3 uncomfortable ones) with 30-second answers — then personally verify every figure in the deck.
  6. Generate the self-supporting document version to send afterwards and check that the figures are identical to those in the projected deck.
Hint — If a slide exceeds 25 words, don't shorten the sentences: look for the hidden second idea and make it a separate slide — or move the surplus into the speaker notes. And the ultimate test of the outline: someone reading only the titles must already understand your message.

In summary

  • The order is non-negotiable: message first, talk next, slides last.
  • The presentation contract — to remember, to feel, to do — guides every cut.
  • Every slide title is a complete assertion: the titles alone already tell the story.
  • One idea per slide, 25 words on screen maximum: the rest lives in the speaker notes.
  • Prepare the questions like a mock exam, especially the three most uncomfortable for your audience.
  • Personally verify every figure: one spotted factual error contaminates the whole deck.
  • Adapt from a single source (projection, sent document, internal version) without ever letting the figures drift.

Quiz — check your understanding

1. In what order do you build an effective presentation?

The visual deck is the last step: generating the slides first produces a generic, hollow deck, because the message hierarchy doesn't exist yet.

2. What makes a good slide title?

The title-message means a viewer who reads only the titles still receives the essence — it's the ultimate test of the structure.

3. What do you do with a slide that exceeds 25 words?

An overloaded slide almost always hides two ideas: splitting preserves the one-idea-per-slide principle, and the speaker notes hold what you'll say without displaying it.

4. Why specifically prepare the 3 most uncomfortable questions?

Your solidity is judged on the questions: an uncomfortable question rehearsed in advance becomes a chance to score points instead of a moment of panic.

5. What is the difference between the projected deck and the document sent afterwards?

The projection deck is deliberately unusable without you; the sent version reads on its own. The substance and the figures stay strictly identical: that's the single-source principle.

Auteur(s)

R

REHOUMA Haythem

Haythem Rehouma est un ingénieur et architecte IA et cloud, formateur et enseignant technique, avec un profil orienté IA médicale, AWS, MLOps, LLM/RAG et vision par ordinateur.