The anatomy of a readable thread
Threads fail for boring reasons: the hook does not promise anything, the middle posts are walls of text, or the last post just stops. Formatting fixes most of that before you ever touch the writing.
- 1Hook postState the payoff and set the scope. "7 mistakes that quietly kill your reach. Number 4 is the one nobody admits to:"
- 2One idea per postEach body post makes a single point. If a post has two ideas, split it. White space is a feature, not wasted room.
- 3Bridge between postsEnd posts on a small cliffhanger or a natural handoff so the reader keeps going.
- 4Close with a point and a nudgeRestate the takeaway in one line, then invite a reply, a repost, or a follow. Do not let the thread just trail off.
Formatting rules that keep people reading
- Keep body posts to a few short lines, not a full 280 wall every time.
- Use line breaks inside a post to separate a claim from its example.
- Number your posts (1/, 2/) only if the thread is a list. For a story, numbers can flatten the tension.
- Avoid trailing a sentence across the post boundary. Each post should read cleanly on its own.
- Put your strongest example, not a summary, in the middle so mid-thread readers get rewarded.
- Save links and the call to action for the final post so early posts stay pure signal.
| Thread type | Opening shape | Closing shape |
|---|---|---|
| List / how-to | "[N] ways to [outcome]:" | "That is the list. Which one are you trying first?" |
| Story | "[Time] ago I [situation]. It nearly [stakes]." | "Here is what I would tell past me:" + one line lesson |
| Teardown | "I studied [thing]. Here is why it works:" | "Steal the pattern, not the post." + follow nudge |
I wrote 200 threads before one took off. The difference was not the writing. It was 5 formatting habits I ignored for a year:
That is the whole system.
Hook, one idea per post, bridge, close.
If this helped, a repost of the first tweet gets it in front of someone who needs it.