L2Lesson 10Free

Build proof slides

Evidence without clutter

After this, you'll be able to create proof-slide copy blocks and use it to move a deck from rough material toward a presentable file.

Before you start

Complete Write claim headers first.

The idea

A proof slide connects a claim to evidence and makes the important part easy to see. This lesson asks you to make proof-slide copy blocks, not a prettier version of scattered notes. The output should be specific enough that someone could open the deck file and see what changed.

Proof sits below the slide while the claim floats unsupported. — The first move: turn the lesson input into proof-slide copy blocks.

Here is the before and after: Before, proof is a dense screenshot, chart, quote, or table dropped onto the slide. After, the slide names the claim, highlights the evidence, and explains what the audience should notice. 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: Pick three proof-heavy slides and ask Claude to turn each into a claim, evidence, annotation, and note. 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.

Build proof slides runtime mapThe deck works when proof-slide copy blocks connects the input, the check, and the next step.

Messy inputThe raw pitch deck material before the lesson shapes it.
proof-slide copy blocksThe 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

Putting speaker notes on the slide instead of in the notes field.
Writing labels that describe the chart without making a claim.
Skipping the proof check because the deck looks persuasive.

Paste this into Claude

For each proof slide below, create slide copy with Claim Header, Evidence Shown, Annotation, Speaker Note, and What To Remove. Slides or source: [paste].

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:
- proof-slide copy blocks
- 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

The proof slide has one claim.
The evidence is named and visible.
The annotation tells the audience what to notice.
Unneeded detail is moved to notes or appendix.

Go deeper (8 min)

Paste this into Claude

Without rereading the lesson, explain why proof-slide copy blocks 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: proof-slide copy blocks 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 proof is present but unannotated because the audience sees data without meaning.
Fails when the slide has too much evidence because nothing feels important.

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 proof-slide copy blocks, challenge the weakest assumption, and rewrite the artifact once so it is ready for the next deck step.

Claim and proof lock together on each slide card.

You can now

You can explain proof-slide copy blocks 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

Proof slides should make evidence legible, not just present.

Evidence needs a claim.
Annotations guide attention.
Dense proof can move to the appendix.
Speaker notes can hold detail the slide should not.

Was this helpful?

Up nextPlan charts, tables, and diagrams

Write claim headers Plan charts, tables, and diagrams

← Back to Slides & Pitch Decks

For each proof slide below, create slide copy with Claim Header, Evidence Shown, Annotation, Speaker Note, and What To Remove. Slides or source: [paste]. 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: - proof-slide copy blocks - 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 proof-slide copy blocks 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: proof-slide copy blocks 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.