Shape the storyline
Opening, tension, proof, and ask
After this, you'll be able to create a storyline spine and use it to move a deck from rough material toward a presentable file.
Before you start
Complete Inventory source material and proof first.
The idea
A deck needs a path the audience can follow. The storyline spine sets the order before individual slides are written. This lesson asks you to make a storyline spine, not a prettier version of scattered notes. The output should be specific enough that someone could open the deck file and see what changed.
Here is the before and after: Before, the deck follows the order of the notes. After, the story starts with the audience's problem, builds the belief shift, proves the claim, and lands the ask. 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: Ask Claude to arrange your proof inventory into a five-part story spine. 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.
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
- Starting design before the audience, room, and decision are clear.
- Treating every note as slide content instead of source material.
- Using a clever title that hides the point the audience must remember.
Paste this into Claude
Use this deck argument and proof inventory: [paste]. Build a storyline spine with Opening, Current Tension, Proof Sequence, Recommendation or Offer, Final Ask. Include what the audience should believe after each part. 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 storyline spine - 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 opening names why the audience should listen now.
- The tension explains what is at stake.
- The proof sequence supports the argument.
- The final ask follows naturally from the proof.
Go deeper (8 min)
Paste this into Claude
Without rereading the lesson, explain why a storyline spine 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 storyline spine 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 the order follows source notes because the audience sees process instead of argument.
- Breaks when the ask appears without buildup because it feels abrupt or unsupported.
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 storyline spine, challenge the weakest assumption, and rewrite the artifact once so it is ready for the next deck step.
You can now
You can explain a storyline spine 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
Storyline is deck structure. It tells the audience why each slide arrives when it does.
- A storyline spine comes before slide count.
- Tension gives proof a reason to matter.
- Each section changes what the audience believes.
- The ask should feel earned.