When a thread beats a single tweet
Threads are for ideas that need steps, evidence or a story. If you can say it in 280 characters, say it in one tweet; a thread that should have been a tweet feels padded.
- A process: how you did something, step by step.
- A list: tools, lessons, mistakes, resources.
- A story: a launch, a failure, a turning point.
- An argument: a claim with reasons and examples.
- A breakdown: what someone else did well and why it worked.
A five-part structure
| Part | Job | Length |
|---|---|---|
| Hook | Make the reader want tweet two. State the payoff. | Tweet 1 |
| Context | Why this matters, or why you're the one telling it. | Tweet 2, optional |
| Body | One point per tweet, in a logical order. | 3–6 tweets |
| Payoff | The summary, the lesson, the so-what. | 1 tweet |
| Close | A question, a follow prompt or a link. | 1 tweet |
Five to eight tweets is a good range. Long enough to go deep, short enough that people finish. If you have 15 points, you probably have two threads.
Spend half your time on the first tweet
Most readers only see the first tweet. It has to promise something specific and believable, and give a reason to open the thread.
- Lead with the result or the surprise, not the background.
- Be specific: numbers, timeframes and names of things beat adjectives.
- Signal it's a thread with the structure (“7 lessons”, “Here's how”) rather than a thread emoji.
- Make it worth reading on its own. Some people will only see this one.
More patterns in how to write hooks.
Write the body one idea per tweet
- Each tweet should stand on its own. Tweets in a thread get quoted and shared alone.
- Lead each tweet with its point. Then the reason or example.
- Use line breaks. Two or three short lines read faster than one dense block.
- Number the tweets only if order matters. For a process, “1/” helps. For a story, it can feel mechanical.
- Cut connective filler. “Another thing I learned is that” becomes the thing you learned.
- Add one image where it explains something. A screenshot or diagram, not decoration.
A full example
- Y
Your name@you1/7
I raised my rates three times in one year as a freelance designer. I lost two clients. My income still went up. Here's exactly how I did each increase, and what I'd do differently:
- Y
Your name@you2/7
1/ The first raise was for new clients only. Existing clients kept their rate. New inquiries got a price 25% higher. Nobody pushed back. That told me I'd been underpriced for a while.
- Y
Your name@you3/7
2/ The second raise went to everyone, with 60 days' notice. I sent a short email: new rate, start date, and one line on what had improved in my work. No apology. No long justification.
- Y
Your name@you4/7
3/ Two clients left after that one. Both were the ones asking for the most revisions. My hours dropped more than my income did.
- Y
Your name@you5/7
4/ The third raise came with a change in how I sold. I stopped quoting hourly and quoted per project, with a fixed number of revision rounds. Clients liked knowing the total upfront.
- Y
Your name@you6/7
What I'd do differently: raise sooner, and tie every increase to a date, not a feeling. If you're waiting until you “deserve” it, you're probably already late.
- Y
Your name@you7/7
If you've raised your rates recently, how did your clients react? I'm collecting stories for a follow-up.
Notice the pattern: a specific hook with a tension (lost clients, more income), one move per tweet, a clear payoff, and a close that invites replies. Templates like the lessons learned thread, how-to thread and listicle thread give you the same skeleton for other topics.
Posting it
- Post the whole thread at once as a reply chain, so readers can scroll straight through.
- Keep external links out of the first tweet. Put them in the last tweet or a reply.
- Stay around for the first hour to answer replies.
- Pin a thread that performs well. See what to pin on X.
If you're starting from a long draft, the free thread splitter breaks it into tweets under 280 characters. Extudio's thread maker writes 5–8 tweet threads in your voice, lets you rewrite any single tweet, previews the thread the way X shows it, and posts it as a reply chain on schedule.
Common thread mistakes
- A vague first tweet. “Some thoughts on hiring” promises nothing. “I've hired 30 people. These 5 questions predicted who'd stay” promises something.
- Throat-clearing in tweet two. If the second tweet says “Before I start, some background…”, cut it or move it later.
- Tweets that only make sense in order. Every tweet should survive being quoted on its own.
- Padding to hit a number. Seven strong tweets beat twelve with filler in the middle.
- No ending. A thread that stops after the last point feels unfinished. Summarize and give readers something to do.
- Posting and leaving. Replies in the first hour are where threads get their second wind.
Checklist before you post
- The first tweet makes a specific promise and works alone.
- Every tweet has one point and reads fine if quoted on its own.
- No tweet is over 280 characters, and none is a wall of text.
- The order makes sense; numbering only if it helps.
- The payoff tweet says the lesson in one line.
- The last tweet gives readers something to do.
- Links are out of the first tweet.