L3Lesson 22Free

Rehearse the talk track

Timing, transitions, and likely questions

After this, you'll be able to create a rehearsal notes pass and use it to move a deck from rough material toward a presentable file.

Before you start

Complete Export and share the right file first.

The idea

Rehearsal is where the deck proves whether the story can be spoken in the available time. This lesson asks you to make a rehearsal notes pass, not a prettier version of scattered notes. The output should be specific enough that someone could open the deck file and see what changed.

The talk track wanders beside the deck instead of following slide intent. — The first move: turn the lesson input into a rehearsal notes pass.

Here is the before and after: Before, the presenter finds pacing problems in the meeting. After, timing, weak transitions, and likely questions are visible before the room sees the deck. For example, if you are preparing a sales presentation, the artifact should name the audience, slide job, proof, speaker note, or export check where that detail matters. A reviewer should be able to tell whether the deck is closer to being presented, sent, or handed off.

Now try it: Run the deck through a timed rehearsal and have Claude produce revision notes. Make one choice before asking Claude to write: which audience, which decision, which proof, which slide job, or which delivery mode matters most right now. That choice keeps the deck from becoming a generic presentation outline.

Rehearse the talk track runtime mapThe deck works when a rehearsal notes pass connects the input, the check, and the next step.

Messy inputThe raw pitch deck material before the lesson shapes it.
a rehearsal notes passThe thing you can inspect, edit, and reuse.
Review checkThe delivery check that catches a weak assumption.
Next stepThe output moves into the next lesson instead of sitting alone.

The lesson is done when the artifact moves the deck toward a real room, reader, or file handoff.

Try it (16 min)

Watch out for

Practicing only the first five slides.
Timing slides one by one without checking section flow.
Skipping the final ask in rehearsal.

Paste this into Claude

Act as my rehearsal coach. Use this deck outline and notes: [paste]. Create a timed rehearsal plan with target time per section, transition lines, likely questions, cuts if time runs short, and slides that need clearer notes.

If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic Deck Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Present Or Send This Without Fixing It. Keep the answer practical enough that I can paste it into my deck working doc.

What a good response looks like

Finished Artifact:
- a rehearsal notes pass
- Why it matters: it gives the deck a concrete thing to inspect instead of a vague intention.
- Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything.

Reality Check:
- The artifact names the user, input, decision, owner, or proof it depends on.
- The weakest assumption is visible.
- The next step can be completed in one sitting.

What good looks like

Timing is assigned by section.
Transition lines are written.
Cuts are named if time is short.
Likely questions are captured.

Go deeper (8 min)

Paste this into Claude

Without rereading the lesson, explain why a rehearsal notes pass matters in three bullets. Then apply it to a second deck example: [describe a different audience, room, or topic]. Return What Changed, What Stayed The Same, What To Check Before Presenting Or Sending, and the exact next action.

What a good response looks like

Transfer Check:
- What changed: the second example has a different audience, input, or delivery context.
- What stayed the same: a rehearsal notes pass still needs a source, a review check, and a next step.
- Before trusting it: inspect the delivery check that would catch a wrong assumption.
- Next action: run the check once, then carry the revised artifact into the next lesson.

What good looks like

You explained the lesson idea from memory before applying it again.
The second example changes the artifact instead of copying the first answer.
The delivery check names a real risk.
The next action can be done in one sitting.

When this breaks

Breaks when timing is guessed because the final ask gets rushed.
Fails when transitions are weak because the deck feels like separate fragments.

AI can help with this

Paste the exercise prompt into Claude with your real deck context. Ask Claude to interview you one question at a time, produce a rehearsal notes pass, challenge the weakest assumption, and rewrite the artifact once so it is ready for the next deck step.

Rehearsal notes attach to each slide job and keep the speaker path clear.

You can now

You can explain a rehearsal notes pass in one sentence.

You can name the source material or decision it depends on.
You can name the assumption that still needs checking.
You can point to the check that proves it is ready for the next deck step.

Key takeaways

Rehearsal turns a deck file into a meeting plan.

Timing belongs at section level.
Transitions can be written before the room.
Cuts protect the final ask.
Likely questions improve readiness.

Was this helpful?

Up nextBuild the Q&A appendix

Export and share the right file Build the Q&A appendix

← Back to Slides & Pitch Decks

Act as my rehearsal coach. Use this deck outline and notes: [paste]. Create a timed rehearsal plan with target time per section, transition lines, likely questions, cuts if time runs short, and slides that need clearer notes. If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic Deck Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Present Or Send This Without Fixing It. Keep the answer practical enough that I can paste it into my deck working doc.

Finished Artifact: - a rehearsal notes pass - Why it matters: it gives the deck a concrete thing to inspect instead of a vague intention. - Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything. Reality Check: - The artifact names the user, input, decision, owner, or proof it depends on. - The weakest assumption is visible. - The next step can be completed in one sitting.

Without rereading the lesson, explain why a rehearsal notes pass matters in three bullets. Then apply it to a second deck example: [describe a different audience, room, or topic]. Return What Changed, What Stayed The Same, What To Check Before Presenting Or Sending, and the exact next action.

Transfer Check: - What changed: the second example has a different audience, input, or delivery context. - What stayed the same: a rehearsal notes pass still needs a source, a review check, and a next step. - Before trusting it: inspect the delivery check that would catch a wrong assumption. - Next action: run the check once, then carry the revised artifact into the next lesson.