L2Lesson 19Free

Make the image and diagram plan

Original, sourced, or generated visuals

After this, you'll be able to create an image and diagram production list and use it to move a deck from rough material toward a presentable file.

Before you start

Complete Build visual hierarchy first.

The idea

Images and diagrams need a production plan. The plan says which visuals are original, sourced, generated, recreated, or unnecessary. This lesson asks you to make an image and diagram production list, not a prettier version of scattered notes. The output should be specific enough that someone could open the deck file and see what changed.

Images and diagrams sit as decorative placeholders with no source plan. — The first move: turn the lesson input into an image and diagram production list.

Here is the before and after: Before, the deck uses placeholder images or decorative AI art. After, every visual has a job, source, rights note, and owner. 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: Turn the visual plan into a production list with source, rights, prompt, and owner. 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.

Make the image and diagram plan runtime mapThe deck works when an image and diagram production list connects the input, the check, and the next step.

Messy inputThe raw pitch deck material before the lesson shapes it.
an image and diagram production listThe 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 (17 min)

Watch out for

Asking a deck tool to invent proof the source material does not contain.
Mixing brand systems inside one deck.
Exporting before checking mobile, projector, and send-ahead readability.

Paste this into Claude

Create an image and diagram production list for this deck. For each visual, include Slide, Visual Job, Source Type, Asset Needed, Rights or Permission Note, Generation Prompt If Needed, Owner, and Deadline. Visual plan: [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:
- an image and diagram production list
- 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

Every visual has a job.
Source type is named.
Rights or permission is considered.
Owner and deadline are included.

Go deeper (8 min)

Paste this into Claude

Without rereading the lesson, explain why an image and diagram production list 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: an image and diagram production list 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

Fails when visuals are decorative because they add polish without helping the argument.
Breaks when rights are ignored because a good-looking deck becomes unsafe to send.

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 an image and diagram production list, challenge the weakest assumption, and rewrite the artifact once so it is ready for the next deck step.

Each visual receives a distinct job block, source lane, accountable block, and rights boundary.

You can now

You can explain an image and diagram production list 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

A visual plan turns images and diagrams into production work, not last-minute decoration.

Every visual needs a job.
Rights and source notes matter.
Generated images still need review.
Owners and deadlines prevent missing assets.

Was this helpful?

Up nextCheck readability and accessibility

Build visual hierarchy Check readability and accessibility Start Here: Build Your Portfolio Brief

← Back to Slides & Pitch Decks

Create an image and diagram production list for this deck. For each visual, include Slide, Visual Job, Source Type, Asset Needed, Rights or Permission Note, Generation Prompt If Needed, Owner, and Deadline. Visual plan: [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: - an image and diagram production list - 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 an image and diagram production list 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: an image and diagram production list 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.