A hook is a promise about what the viewer will learn. The carousel offers six ways to frame that promise: a question, a number list, a before and after, a contrarian instruction, a personal experiment and a mistake. These structures are starting points for testing. None guarantees reach, retention or sales. Choose the form that matches evidence you can actually show.

Before you start

Pick one audience, one concrete problem and one lesson. Gather the example, demonstration or observation that supports it before writing the opening. Define the action you want an interested viewer to take. Keep a small research ledger with each source URL, date, audience, hook structure and the reason you think the example is relevant.

The workflow

  1. The question: identify a real point of confusion and answer it directly. Template: Why does ___ happen when ___? The carousel uses the broader nobody-talks-about opening; only use that framing when it is supportable. A precise question avoids pretending that a well-known topic is undiscovered.
  2. The number list: promise a specific count and deliver distinct items. Template: Three checks before you ___. Decide the order around what the viewer needs to do. Do not add surprise language unless the post gives a real reason for it.
  3. The before and after: show the change and its conditions. Template: I used to ___. Now I ___. Use your own documented experience or clearly label an illustrative example. Include tradeoffs instead of presenting a result as inevitable.
  4. The contrarian: challenge a specific action under stated conditions. Template: Stop ___ when ___. Try ___ instead. Explain why the alternative fits that situation. Avoid turning a limited lesson into an unsupported universal rule.
  5. The I-tried-it pattern: describe an experiment you actually ran. Template: I tried ___ for ___; here is what happened. Show the period, method, observations and limitations. If you have not run the experiment, write a proposed test instead of inventing first-person experience.
  6. The mistake: name an observable error and explain a correction. Template: This ___ mistake causes ___. Check ___. Show the consequence with evidence or present it as a possible failure mode. Give the viewer a useful next step instead of only assigning blame.

Worked example

Illustrative drafting exercise: the lesson is to re-check an invoice before sending a reminder. A question hook could be: Why did a paid customer receive an overdue reminder? A list hook could be: Three checks before your next invoice reminder. Both must lead to the same explanation of current status, last update and send-time validation. These are illustrative openings, not tested winners.

Your worksheet

  • Audience and concrete problem: ___
  • Single lesson the post will deliver: ___
  • Pattern and opening sentence: ___
  • Source, demonstration or personal evidence: ___
  • What the opening promises: ___
  • Where the post fulfills that promise: ___
  • Primary test measure and qualified next action: ___

Test it

  1. Read only the opening and write down its implied promise; confirm the body fulfills it.
  2. Check every number, personal-experience statement and before/after claim against its evidence.
  3. Compare comparable posts or controlled variants, noting audience and distribution differences before attributing results to the hook.

What to measure

Track the measures available for the format, such as initial retention, completion, saves and qualified visits. Include denominators and sample sizes. Views describe attention, while relevant inquiries and completed next actions help assess business usefulness. Treat small-sample results as learning, not proof of a permanent winning formula.