structures

Framework Library

the underlying architecture of a hook. frameworks are the shapes (problem → solution, before → after, open loop) that you pour your specific idea into.

Framework

Problem → Solution

Name a sharp pain→Agitate the cost→Reveal the fix

The oldest structure in persuasion. Lead with a problem the reader feels in their body, make the cost of inaction vivid, then position your idea as the release valve. Works because it mirrors how people actually make decisions — away from pain first, toward gain second.

Framework

Before → After

Paint the old world→Cross the bridge→Show the new world

Sell the transformation, not the feature. Anchor the reader in a painful 'before,' then contrast it with a desirable 'after' they can picture themselves in. The bigger and more specific the gap, the more magnetic the pull.

Framework

Expectation → Reality

State the common belief→Snap to what's true→Explain the gap

Set up what the reader expects, then break it. The dissonance between expectation and reality is a pattern interrupt that forces attention and makes your insight feel like a revelation rather than a lecture.

Framework

False Belief

Name the belief they hold→Prove it wrong→Replace it

Target a belief the reader is quietly certain about, then dismantle it. Because you're correcting them rather than informing them, the stakes feel personal and the payoff feels essential. Always replace the old belief with a better one — never leave a hole.

Framework

Contrarian

State the consensus→Take the opposite side→Back it with proof

Stake out the unpopular position. A defensible contrarian take is the fastest way to stop the scroll and start a conversation — people can't help but weigh in. The risk is being contrarian without substance; always earn the take with evidence or experience.

Framework

Story

Drop into a moment→Raise the stakes→Land the lesson

Open mid-scene, not with context. A specific moment ('It was 2am and the deploy was failing') pulls the reader into a world before they decide whether to care. Stories bypass skepticism because the brain processes them as experience, not argument.

Framework

Question

Ask what they're already wondering→Sharpen it→Promise the answer

A well-aimed question mirrors the reader's own internal monologue, creating instant relevance. The best hook-questions are ones the reader can't answer confidently — which opens a curiosity gap they'll read to close.

Framework

Prediction

Claim a shift is coming→Show the early signal→Position the reader

Predictions borrow the authority of foresight. By calling a shift before it's obvious and pointing to the early signal, you position yourself as ahead of the curve and the reader as smart for listening. FOMO does the rest.

Framework

Mistake

Confess the error→Show the cost→Extract the lesson

Vulnerability is magnetic. Admitting a mistake lowers the reader's guard, and the implied lesson ('so you don't have to') makes the payoff feel like a gift. The bigger and more specific the cost, the harder it lands.

Framework

List

Promise a countable payoff→Signal density→Deliver fast

Lists promise a clear, finite payoff with low cognitive cost — the reader knows exactly what they're getting and that it won't ramble. Specific numbers ('7 tools', '3 mistakes') set expectations and boost saves. The hook must promise density, not filler.

Framework

Authority

Establish credibility→Share the insider view→Give the takeaway

Lead with earned credibility — a number, a role, a body of work — then trade on it to deliver an insight the reader couldn't get elsewhere. Authority lowers skepticism; the specific insight earns the follow.

Framework

Open Loop

Tease the payoff→Withhold the key detail→Pull them forward

Promise something valuable is coming, but withhold the detail that resolves it. The unresolved tension keeps the reader moving through your content to reach the close. Master storytellers stack loops to hold attention far past the hook.