Rewriting a thread hook so people read the second post

A thread lives or dies on post one, because a reader scrolling decides there and nowhere else. Generated hooks promise value without saying anything, which is why they get scrolled past.

Short answer

• One claim, one number, one thing the reader can check.
• No 'let me explain' or 'here's what I learned'. Start with the result.
• The hook must be specific enough that a stranger could disagree with it.
• Do not put a link in post one if you are new. It suppresses the post.
• Each post should stand alone. Readers arrive mid-thread from search.

Claim first, context later

The hook is a claim, not a setup. 'We cut our deployment time by 80% by deleting a test suite' works because it contains a decision someone can argue with. 'Here is what I learned about deployments' does not, because it makes the reader wait.

Then the thread earns the claim: what you tried, what broke, the number, and what you would do differently. The last post should say the thing you would not want a competitor to read.

Hooks that read as generated

Any of these can be made honest by replacing the promise with the fact.

Keep the thread short

Six to ten posts holds attention. Past that, engagement drops sharply and the honest reason for the length is usually that you have not decided what the point is. If you cannot say it in six, write an article instead.

Before / after

Questions