A carousel with nine excellent slides and one weak opening slide performs like a carousel with one slide — because nobody swipes past a hook that doesn't work, and the other nine never get seen. Slide one isn't equal to the rest; it's the gatekeeper for all of them.
What a hook slide's one job actually is
Not to summarize the carousel, not to introduce the topic politely — to create one specific reason to swipe to slide two. A hook slide that reads like a title page ("5 Tips for Better Mornings") is dramatically weaker than one that makes a claim or asks a question specific enough to create genuine curiosity ("The one morning habit that's actually wasting your time").
Why summarizing the content is the most common mistake
The instinct is to use slide one to explain what's coming — but a slide that already tells the reader the gist removes their reason to keep swiping. The hook should create a gap between what's promised and what's delivered, not close it early. Save the actual content for the slides earning the swipe, not the one asking for it.
Type size and hierarchy matter more here than anywhere else
Because a hook slide is evaluated in a fraction of a second during a scroll, its text needs to be readable at a glance — larger type than you'd use anywhere else in the carousel, one dominant line rather than several competing ones. If a viewer has to slow down and actually read carefully to get the hook, it's already lost most of its effectiveness against a feed that rewards instant legibility.
Branding without competing for attention
Your logo and brand colors should be present (consistency matters — see what belongs in a brand kit) but sized so they don't compete with the hook text itself. A hook slide is not the place for a prominent logo placement; it's the place for the one line of text doing all the work.
Testing hook slides specifically
Because the hook slide's entire job is measurable (did people swipe?), it's one of the more testable elements in your whole content system — see A/B testing templates for running a genuine comparison between two hook approaches on the same underlying content, and swipe-through rate as the actual metric to design for rather than judging a hook by how it looks in isolation.
Building a repeatable hook formula
Rather than reinventing the hook from scratch each time, a small set of proven patterns — a specific claim, a surprising number, a direct question, a "most people get this wrong" framing — can become a repeatable formula you rotate through, adapted to each carousel's actual content. This is exactly the kind of decision worth baking into a template rather than re-deciding fresh every single carousel.