Carousel Frameworks

Five slide-by-slide narrative architectures for carousels — Instagram carousels and LinkedIn document posts. Each framework is a different reason to keep swiping; picking the right one for the content matters more than polishing individual slides.

A carousel is not a blog post chopped into squares. It's a swipe-through with two jobs per slide: deliver one idea, and make the next swipe irresistible. These frameworks encode structures that show up repeatedly in high-performing carousels; treat them as starting structures to adapt, not rigid formulas — and expect to validate against your own analytics.

Picking a Framework

Two cross-framework rules before the specifics:

• Slide 1 is the thumbnail. It competes in the feed alone, before anyone knows a carousel follows. Design and write it as a standalone scroll-stopper.
• One visual template per carousel. Same layout, type scale, and palette on every interior slide. Variety between slides reads as clutter; consistency lets the content change while the frame stays still.

Framework A: Value-Stack (4–14 slides)

The "everything you need" carousel. Works because the cover makes a completeness claim — an exact count and an exact deliverable — and every swipe pays it down.

Why the exact count matters: "27 free tools" outperforms "the best free tools" because a number is a checkable promise — the reader can verify you delivered. Rounding up with padding breaks the trust the count created.

SaaS example: "12 ChatGPT prompts for SaaS onboarding emails" → one prompt per slide with the use case → "Comment PROMPTS and I'll send the full doc."

Failure mode: filler slides to hit a bigger number. Cut to the real count; a tight 8 beats a padded 14.

Framework B: Problem-Proof (6–10 slides)

The "I did X, here's the system" carousel. The hook is a result stated as fact, not advice — and the final slide shows the receipt, closing the loop slide 1 opened.

The open loop is the engine: slide 1 makes a claim, the last slide proves it, and everything between explains how. Readers swipe to see whether the receipt is real.

SaaS example: "We cut churn 22% with one onboarding email." → the real problem (activation, not price) → the sequence structure → the literal email copy → the retention chart.

Failure mode: vague mechanism slides ("optimize your workflow") — if the middle slides don't name tools and steps, the proof slide reads as luck, not system.

Framework C: Hack List (6–10 slides)

The "numbered techniques" carousel. A contrarian cover creates status anxiety — most people are doing this wrong — and each numbered hack independently re-earns the swipe.

Name every technique. "The 3-second rule" is shareable and memorable; "keep it short" is neither. Named techniques travel — people repeat them and credit the source.

SaaS example: "90% of trial emails never get opened." → why (they read like receipts, not messages) → Hack #1: The founder-from line, Hack #2: The one-question subject, ... → "Trial emails are conversations, not confirmations. Save this for your next sequence."

Failure mode: hacks that are restatements of each other. Each slide must survive alone — if two hacks collapse into one idea, merge them and go shorter.

Framework D: Rant Callout (4–8 slides)

The "someone had to say it" carousel. Personality-led and polarizing by design — the structure exists to keep the heat fair so it reads as conviction, not bitterness.

The fairness pivot is what makes it work. Without it you're yelling; with it you're drawing a precise line, and precise lines get quoted. It also pre-empts the top hostile comment.

SaaS example: "Your AI-generated LinkedIn posts are costing you customers." → the specifics (same em-dash cadence, same 'game-changer' vocabulary, zero lived detail) → "Don't get me wrong. I use AI daily. My problem is publishing the first draft." → "Write like you talk. [Name]"

Failure modes: skipping the pivot (reads unhinged, invites pile-ons), or ranting about something your own product/content visibly does (the comments will find it).

Framework E: Demo Walkthrough (5–11 slides)

The "watch it work" carousel for product or workflow content. Show the finished result first, then the steps — the outcome earns attention for the process.

Overview-before-detail is the key move (same reason recipe sites list ingredients before instructions): a reader who's seen "4 steps, 10 minutes" on slide 3 will finish; a reader dropped straight into step 1 with no map bails at step 2.

SaaS example: "From CSV to live dashboard in 4 steps" → the pain (weekly manual reporting) → the 4-step overview → one screenshot per step → the finished dashboard + "Built for marketers, not analysts."

Failure mode: screenshots with too much UI. Crop to the action, zoom the relevant control, annotate with one arrow — each screenshot should make sense at thumbnail size.

Platform Notes

Instagram: 1080×1350 (4:5) slides; up to 20 slides but the frameworks' ranges above reflect where completion rates hold. The caption carries the searchable text — restate the hook and add context, don't just repeat slide 1. First slide doubles as the grid thumbnail.

LinkedIn (document posts): Upload as PDF. Square or 4:5. LinkedIn shows a "N pages" badge — Value-Stack's exact-count cover plays especially well here. B2B tolerates denser text per slide than Instagram, but the one-idea-per-slide rule still holds. The post text above the document is a second hook — write it as its own post, not a throwaway "see attached."

TikTok photo mode: Same frameworks work; pacing skews faster — trim each framework toward its minimum slide count.

Production Checklist

• [ ] Slide 1 works as a standalone feed post (test: would it stop the scroll with no carousel behind it?)
• [ ] One idea per slide — if a slide needs two sentences of setup, split it
• [ ] Same visual template on every interior slide
• [ ] Any count promised on the cover is exactly delivered (no filler, no rounding)
• [ ] Claims and numbers are real and yours — no invented stats or borrowed screenshots
• [ ] Text is legible at thumbnail size (minimum ~28pt at 1080px wide)
• [ ] Final slide has one CTA, not three
• [ ] Caption/post text written as its own hook, not a repeat of slide 1

Measuring What Worked

Judge carousels on saves and completion, not likes — saves signal reference value (the algorithmic win for carousels), and where per-slide analytics exist (Instagram professional insights, LinkedIn document analytics, or third-party tools), drop-off position tells you which slide broke the swipe chain. When a carousel underperforms, the fix is usually slide 1 (didn't stop the scroll) or the framework choice (list content forced into a rant structure), not the middle slides. Track per-framework performance and double down on the two that fit your audience — see reverse-engineering.md for the analysis workflow.