Guide 2 · 4 minute read
Thread structure templates for X
Six outlines you can fill in, with a plan for each post and notes on when each shape fits.
By the Tweet Engine Team · Updated
Most good threads follow one of a handful of shapes. Picking the shape before you write saves time, because it tells you what each post needs to do and where the thread ends. The six outlines below cover the large majority of threads that get read through. For each, the post-by-post plan is a starting point. Add or drop middle posts to fit the material.
All six share two rules. The first post states the topic and the payoff, and every post should make sense on its own.
1. The list
Use it for tips, mistakes, tools, lessons or anything that comes in separate pieces. It is the easiest shape to read and to repost from, because each post is self-contained.
| Post | What it does |
|---|---|
| 1 | Topic, number of items, and why this list is worth reading ("7 mistakes I made in my first year freelancing, and what each one cost") |
| 2 to n−1 | One item per post: the item in the first line, then one or two sentences of explanation or an example |
| n | A one-line summary or the single item that matters most, plus an optional link |
Order matters more than people think. Put a strong item second, because post 2 decides whether readers continue. Save another strong item for the end so the thread doesn't fade out.
2. The how-to
Use it when the reader should be able to do something by the end: set up a tool, cook a dish, file a form. Number the steps in the text as well as with the thread counter, since readers will scroll back to find step 4.
| Post | What it does |
|---|---|
| 1 | The result, how long it takes, and what you need |
| 2 | Anything to prepare or check first |
| 3 to n−1 | One step per post, written as an instruction, with the reason for the step if it isn't obvious |
| n | How to tell it worked, and what to do if it didn't |
Screenshots help here, and on X they don't cost characters. Attach one to each step that involves clicking something.
3. The story
Use it for something that happened: a project, a mistake, a day that went wrong. Stories hold readers well when each post ends on a small turn.
| Post | What it does |
|---|---|
| 1 | The situation and the hook: what was at stake or what went wrong |
| 2 to 3 | Setup: just enough context to follow |
| 4 to n−2 | Events in order, one beat per post |
| n−1 | The outcome |
| n | What you took from it, in a sentence or two |
The main risk is too much setup. If the interesting part starts in post 5, move it up and fill in the background later.
4. The explainer
Use it to explain a concept, a news story or a decision. The aim is understanding, so the order runs from simple to detailed.
| Post | What it does |
|---|---|
| 1 | The question the thread answers, in plain words |
| 2 | The short answer, in one or two sentences |
| 3 to n−1 | The parts of the answer, each with an example or a number |
| n | What it means for the reader, or what to watch next |
Putting the short answer in post 2 feels like giving the game away. It works anyway: readers who get the answer early stay to understand it, and those who leave still got something.
5. The case study
Use it to show results from a project, a test or an experiment. Readers want the numbers and the method, so give both.
| Post | What it does |
|---|---|
| 1 | The result in one line, with the number ("We cut support tickets by 38% in three months") |
| 2 | The starting point and the problem |
| 3 to n−2 | What you changed, one change per post, with its effect if you measured it |
| n−1 | What didn't work |
| n | What you'd do again, and a link to the full write-up if there is one |
The "what didn't work" post is often the most shared one. It makes the rest more believable.
6. The roundup
Use it to gather links, news or posts on a topic: the week's releases, the best talks from a conference, reading on a subject.
| Post | What it does |
|---|---|
| 1 | What the roundup covers and the time frame |
| 2 to n−1 | One item per post: what it is, why it matters, and the link |
| n | Where readers can find more, or when the next roundup is due |
Every link costs 23 characters, so a roundup post has about 250 left for the description. That's plenty for two sentences. Resist putting three links in one post. Only one gets a preview card, and the others look like clutter.
Matching template to material
If you aren't sure which shape fits, ask what the reader should walk away with:
- A set of separate ideas: the list.
- The ability to do something: the how-to.
- A sense of what happened: the story.
- An understanding of something: the explainer.
- Evidence that something works: the case study.
- Places to go next: the roundup.
Filling a template with the splitter
Write the posts in the order of the template, separated by blank lines, and paste the whole thing into Tweet Engine. When each planned post is a single paragraph under the limit, the splitter keeps them as separate posts. If a paragraph runs long, it gets split between sentences, and the card for that post shows where. Merge or edit from there.
Template tables like these are also a good way to check a draft. Write down what each of your posts does in a few words. If two posts do the same job, merge them. If a job in the template is missing, like the outcome in a story, your readers will notice the gap.
Questions
Can I mix two templates in one thread?
Yes, and many good threads do. A case study often contains a short how-to, and a story can end with a list of lessons. Pick one shape as the backbone so readers know where they are, and borrow from the others inside it.
Do templates make threads sound the same?
Only if you copy the wording. The outlines here describe what each post does, not what it says. Your examples, numbers and voice are what make the thread yours.
Tweet Engine is independent and not affiliated with X Corp. X changes its features and limits from time to time; X's help center has the current rules.
Have a draft ready?
Split it into a thread