How to Write an X Thread People Read to the End

A thread on X is a series of connected posts that reads like a short lesson. When it works, people read every post, save it and come back to your profile to see what else you have written. When it doesn't, they read the first line and scroll on, and the rest of your work goes unseen.

The difference is rarely talent. It is a handful of habits you can learn. This post gives you those habits as practical tips, with an example for each, so your next thread is one people read to the end.

What makes an X thread worth reading?#

An X thread is worth reading when it teaches one idea the reader cares about, in an order they can follow. One idea, one reader, one clear path. Most weak threads fail on the first part: they try to cover everything the writer knows about a topic, so the reader never knows what they are supposed to take away.

Before you write a word, finish this sentence: "After reading this thread, you will be able to…". If the end of the sentence is vague, such as "understand marketing better", the thread will be vague too. If it is specific, such as "write a pricing page headline in ten minutes", you already have your topic, your reader and your first post.

This is the same idea behind education content marketing: a reader who gets a small, real result from your thread trusts you more than a reader who only saw your opinion.

How do you write the first post of a thread?#

Write the first post as a promise: name a specific result, who it is for, and give the reader a reason to open the rest. The first post is the only one most people see, so it has to work on its own. It is your headline, and the rules of a good landing page headline apply here too.

Three tips for the first post:

1. Be specific. "How to plan a week of posts in one hour" beats "Content tips". Specific numbers of steps or minutes are fine when they are true for your method.
2. Show the shape. Saying "in 4 steps" or "5 mistakes" tells the reader how long the trip is, which makes them more willing to start.
3. Skip the warm-up. Cut openers like "I've been thinking a lot about…". Start with the result.

How should you structure the rest of the thread?#

Structure the rest of the thread as a climb: each post makes one point, and each point builds on the one before. If a reader could shuffle your posts and lose nothing, the thread has no structure yet, only a list of tips.

Tips for the middle posts:

• One point per post. If a post needs the word "also", it is probably two posts.
• An example in every step. "Write a clear headline" is advice. "Change 'Smart scheduling' to 'Plan your week of posts in one hour'" is a lesson.
• Short lines, white space. Break a post into two or three short lines. People read threads on phones, often in a hurry.
• Name a common mistake. One post about what goes wrong makes the right way stick.
• Number the steps when order matters, so the reader always knows where they are.

End with a post that sums up the lesson in a few lines and gives one step to try today. That last post is often the one people save or share, because it holds the whole idea in one place.

How long should an X thread be?#

An X thread should be as short as the idea allows, usually just long enough for each step to get its own post. There is no magic number. A three-step method needs about five posts: a promise, three steps and a summary. Padding it to fifteen posts doesn't make it more valuable; it gives readers more places to leave.

Readers drop off as a thread goes on, and that is normal. What you can control is where they drop off. A big drop right after the first post means the second post didn't deliver on the promise. A drop in the middle usually means a post repeated an earlier point or had no example.

In an example like this one, the biggest fall is between the first and second posts. That is the spot to fix first: make sure the second post starts paying off the promise right away, with the first step or the reason the result matters, not more background. After the second post, the curve flattens, which means the readers who stayed are getting what they came for.

To read your own drop-off, open the analytics for each post in a thread and compare their views. You don't need exact numbers to learn from it. You only need to see where the steepest fall is.

How do you write a thread in under an hour?#

Write a thread fast by drafting the first and last posts first, then filling the middle, and editing only after the whole draft exists. Most of the time a thread takes goes into rewriting single posts before the shape is clear. Fix the shape first and the posts get easier.

A good source of threads is what you have already made. A newsletter issue, a blog post or a short video each holds an idea you have explained before. Take the main point and its steps, and rewrite each step as one short post. If you write a newsletter, our guide to starting a newsletter people open pairs well with this habit: one issue can become one thread.

Summary#

A thread people read to the end teaches one idea in a clear order. Make the first post a specific promise that stands alone, give each middle post one point and one example, and finish with a summary and a step to try. Keep it as short as the idea allows, and use your post analytics to find where readers leave. If you want help turning lessons into posts you review before they go out, OpenCMO drafts posts you approve and publish.