A thread is a long-form argument that has to survive being read on a phone, one post at a time, while the reader’s thumb hovers over the scroll. Most threads die at post two because the first post over-promised and the second under-delivered. A workflow fixes that, because it forces decisions about the hook, the order and the close before anyone starts typing.
This guide is about building the thread itself. For single posts, see X content from your website . Here we assume you have a long source: a blog post, a case study, a comparison page, or a teardown, and you want to turn it into 6 to 12 connected posts.
The hook carries the whole thread
On X, post one decides whether posts two through ten are ever seen. It has to do one thing: create a gap the reader needs closed. Three hook patterns that reliably open a thread:
- The number drop. “We rewrote our onboarding 4 times in 18 months. The version that finally worked broke every rule we’d been told. Here’s what changed:”
- The contradiction. “Everyone says ship fast. We slowed our release cycle down by half and shipped more. The math is counterintuitive:”
- The specific promise. “How a 2-person team writes a month of content in one afternoon (the actual workflow, not motivation):”
Notice what these avoid: no “thread 🧵,” no “let’s dive in,” no throat-clearing. The hook states the payoff and the proof in one breath.
Map the page to posts before you write
Open your source page and pull out the load-bearing points. A good thread is one idea per post, in an order that builds. The structure below is the spine most strong threads share.
| Post | Job | What goes here |
|---|---|---|
| 1 | Hook | The gap + a hint of proof |
| 2 | Stakes | Why this matters now, or what it costs to get wrong |
| 3-7 | Body | One idea per post, each a complete thought |
| 8 | Turn | The non-obvious insight, the part people screenshot |
| 9 | Recap | The whole argument in 3 lines, for the skimmers |
| 10 | Close | One next step, one link, one ask |
The body posts are where source material matters most. If post four is “be consistent,” you have summarised, not compressed. If post four is “we posted at 7am for a month and our reply rate doubled, so we made it a rule,” you have given the reader something to do.
Pace the payoff
The mistake that kills retention is front-loading every good point. If posts two and three are your best material, the reader leaves at four. Spread the strong lines: put one early to confirm the hook was honest, save the sharpest for post eight, the “turn.” Each post should also end slightly open, so the reader’s eye carries down. A post that ends “…and that’s when it broke” pulls harder than one that ends “…which was good.”
Keep individual posts short. Two or three lines. White space is retention on a phone.
Write the close as a soft handoff
The last post is the only place a link belongs. Recap in three lines for everyone who skimmed, then offer exactly one action: follow for more, read the full piece, or reply with their version. Asking a question in the final post is the single best way to earn replies, and replies are what the algorithm reads as “this was worth a conversation.” Tie that close to a deliberate social media CTA strategy rather than a generic “thanks for reading.”
A reusable drafting checklist
Run this before you publish:
- Post 1 states the payoff, not the topic
- No post says something a competitor could also say
- The strongest line is around post 8, not post 2
- Every body post is one idea, two to three lines
- At least one post contains a checkable number
- The close has one link and one question, not three CTAs
- A reader who only sees posts 1, 9 and 10 still gets value
Measure thread-specific signals
A thread’s health is not its like count on post one. Track bookmarks on the thread (intent to revisit), replies (conversation, which extends reach), and the drop-off shape: if impressions on post two are 60% of post one, your hook over-promised. Threads that hold their audience past the turn are the ones worth rebuilding into a blog to social posts pipeline and repurposing elsewhere.
Utin is being built to draft threads from your site this way: it pulls the load-bearing points from a long page, proposes a hook-to-close structure, and keeps each post tied to its source so reviewers can check the claims. You can register interest in the early pilot if that fits how your team works.