How to write a thread

Before anything else: most threads should not be threads. If the idea fits in one post, post it. If it needs two thousand words and a structure, write an article and link to it. The thread format suits a specific middle case — a sequence of connected points, each of which is interesting on its own, where the accumulation is the payoff.

Writing a thread when you should have written a post is the most common error, and readers notice.

The first post is the whole thing

Nobody sees post 4 unless post 1 earns it. It has to work completely alone — as a statement someone would find worth reading even if the rest never existed.

Strong openers:

• A specific claim. "I read 40 grant applications last month. 31 failed on the same paragraph."
• A concrete number with a surprise in it.
• A short story's first beat. "In 2019 our biggest client left over a single email."
• A useful list, promised. "Nine things I wish I'd known before freelancing full-time." Overused, still works when the nine things are real.

Weak openers: "A thread 🧵", "Let's talk about…", "Unpopular opinion:", and any post whose only content is that a thread is coming.

Do not put "1/" in the first post. Numbering is fine from the second onwards, and some people leave it out entirely so each post can stand alone if shared.

Structure

Post 1: the hook, self-contained.

Post 2: the stakes or the context. Why this matters, or why you know.

Posts 3 to N: one idea each. This is the discipline that makes threads readable — a post with two ideas is a post the reader skims.

Near the end: the strongest single point. Not the weakest, which is where people tend to put it after running out of energy.

Final post: the summary or the turn, and at most one call to action.

Six to twelve posts is the working range. Beyond about fifteen, engagement falls off steeply and you have written an article in the wrong container.

Pacing

Vary the length. A run of identical medium-length posts reads as a wall. A short, blunt post after three dense ones lands hard.

Each post should end in a way that makes the next one wanted — an incomplete thought, a question, a "but". Not cliffhanger manipulation, just ordinary narrative pull.

Put anything visual — a chart, a screenshot, a photo — where the argument needs evidence, not decoratively at the top.

Voice

Write the way you would explain it to one intelligent person who is not in your field. Threads that read as broadcast do worse than threads that read as explanation.

Avoid the platform's stock rhythms: the one-line paragraph stack, the manufactured revelation, "Let that sink in", "Here's the kicker". They are heavily parodied and they signal that the content is optimised rather than considered.

Common mistakes

Threading something that fits in one post. Threading something that should be an article. A first post that only announces the thread. Two ideas in one post. Fifteen posts of throat-clearing before the point. Reusing a well-known anecdote as your own. A call to action in every post. Deleting and reposting to game distribution — readers see the receipts.

Practical tips

• Draft it as a plain list in a notes app, one line per post, before writing any of it out. The structure problems show up immediately.
• Read post 1 in isolation and ask whether you would stop scrolling.
• Check the character count on your longest post before you start posting, not halfway through.
• Wait an hour before posting. Threads written in a rush are the ones that get quote-posted uncharitably.
• If the thread does well, write the article. The thread proved the demand.