How to Write a Twitter/X Thread That Doesn't Flop

Most threads lose the majority of their readers between the first and second tweet. The hook gets the click to "show this thread," but if tweet two doesn't immediately deliver on what tweet one promised, people bail before tweet three.

The first tweet has one job: create a specific gap

Not "a thread about productivity" — a specific, slightly incomplete claim that creates curiosity. "I tracked every hour of my week for 30 days. The result wasn't what I expected" works because it promises a specific payoff without giving it away.

Tweet two can't be a recap

A common mistake is using tweet two to restate the premise ("Let me explain..."). That's a wasted beat. Tweet two should already be delivering — the first concrete point, not a preamble.

Pace one idea per tweet, not one paragraph per tweet

If a tweet needs to be read twice to land, split it. Threads that read fast feel valuable; threads that require effort per tweet lose people regardless of how good the content actually is.

Use the structure of the gap you opened

• Listicle threads ("7 mistakes I made...") — pace each item as its own tweet, ordered from least to most surprising.
• Story threads — follow the actual chronology; don't flash-forward to the result early.
• Teaching threads — one concept per tweet, with a concrete example attached to each, not stacked at the end.

The payoff has to match the promise

If your hook promised a specific result, the final tweets need to deliver that exact thing — not a vague "hope this helped." Readers who get to tweet ten are your most engaged audience; give them something worth the follow.

End with one CTA, not a list of asks

A single, low-friction ask — follow for more, reply with your experience, or a link to read further — outperforms a stacked list of requests at the end of a thread.