Writing
Voice-to-thread: turning a rambling idea into a clean X thread
Talking is a great way to get an idea out of your head and a poor way to arrange it. Spoken ideas loop back, repeat themselves and save the best line for minute three. A good X thread does almost the opposite. It leads with the point, gives each post one job, and stops.
The trick is to keep talking as the first step, since that's where the raw material comes from, and then do a short, focused edit. Here's the process we use.
Talk first, in a loose shape
You don't need a script. You need a rough shape you can say out loud without notes, and this one works for most threads:
- The claim. One or two sentences that say what you think or what happened. This becomes post 1.
- Why it matters to the reader. One sentence.
- The supporting points, one at a time. Say "next post" between them if you're using CallTweet, or just pause and start a new paragraph.
- One concrete example, number or story.
- What to do with it, or where to read more.
Saying "next post" between ideas is the single most useful habit. It forces you to finish one thought before starting the next, and it leaves a marker the thread splitter treats as a hard break.
If you lose your thread mid-sentence, keep going. You'll cut it later. Stopping to restart every time you stumble kills the flow, and the flow is the reason to speak instead of typing.
Let the splitter do the counting
A minute of natural speech is roughly 130 to 160 words, which is somewhere around 750 to 900 characters. That's three or four posts before any editing. Splitting that by hand on a phone is tedious and error-prone.
CallTweet's splitter fills each post one whole sentence at a time and only breaks inside a sentence when that one sentence is longer than a post. It counts the way X does: each link costs 23 characters, emoji cost 2. With numbering on, it reserves space for the " 3/6" label so every post still fits under 280.
At this stage don't worry about where the breaks land. Get the whole draft down, look at the posts it produced, and then edit.
The five-minute edit
Most of the improvement comes from a handful of edits. Work through them in this order.
Rewrite post 1 by hand
Your spoken opening is almost never your best opening. People tend to warm up ("So I've been thinking about...") before they get to the point. Find the sentence where you actually said the point, often two or three sentences in, and move it to the top. Post 1 is what appears in people's feeds and what decides whether anyone taps through, so it should make sense on its own.
Cut the loops
Spoken drafts repeat themselves. You'll find the same idea said twice in slightly different words, usually because you weren't sure the first version landed. Keep the clearer one. Delete phrases that only exist because you were thinking out loud: "kind of", "basically", "you know", "I guess".
One idea per post
Read each post and ask what it's for. If a post holds the tail of one idea and the start of the next, move the break. Put the cursor before the new idea and type --- on its own line, or say "next post" next time. Posts that stand alone are easier to quote and reply to.
Fix what dictation got wrong
Check names, handles, numbers and words that sound like other words. Type @handles and links by hand. Dictation turns "at" and a spoken name into nonsense often enough that it's quicker not to try.
End on something useful
The last post should give the reader something to do or keep: the link, the takeaway, the question you want answered. Don't restate the first post in different words; people just read it.
Where the breaks should go
Good breaks fall at the end of a complete thought. A few patterns help:
- A post that ends with a colon or "here's why" pulls people into the next one. Use it once, maybe twice. Every post ending on a cliffhanger gets tiring.
- Lists work well with one item per post, numbered in the text if order matters.
- Put a link in its own post near the end, or in the last post. Posts that are mostly a link look like ads in the timeline.
- Keep a quote or statistic in the same post as the sentence that explains it. Split apart, both lose meaning.
A worked example
Here's a spoken draft, roughly as dictation produced it:
so I've been testing standing desks for a month now and honestly the desk matters less than I thought comma what matters is how often you change position period the people who did best in our office weren't the ones standing all day they switched every 30 to 45 minutes period next post also the cheap anti fatigue mat made a bigger difference than the motorized desk period next post if you're thinking about one start with a mat and a timer before you spend 600 dollars
After spoken punctuation, the splitter and a two-minute edit, it becomes:
The desk matters less than how often you change position. After a month of testing standing desks, that's the clearest result. 1/3
The people who felt best in our office weren't the ones standing all day. They switched every 30 to 45 minutes. 2/3
The cheap anti-fatigue mat did more than the motorized desk. Thinking about one? Start with a mat and a timer before you spend $600. 3/3
The edit moved the point to the front, cut "so" and "honestly", and fixed "600 dollars". Everything else came from talking.
Posting the thread
X's share link can only fill in one post, so CallTweet opens post 1 in X's composer and gives the rest copy buttons. You have two ways to finish:
- In the composer, tap the plus button to add the next post, paste post 2, and repeat. Publish them all at once.
- Or publish post 1, open it, and reply with post 2. Reply to post 2 with post 3, and so on down the line.
The first way is faster and keeps the posts together from the start. The second lets you check how each post looks before adding the next.
When not to make a thread
Some ideas are one post. If your draft is two posts and the second only repeats the first, cut it back to one. If it's fifteen posts, it might be two threads, or a piece of writing that belongs somewhere else with a single post pointing to it. A thread earns its length by giving each post a reason to exist.
Ready to try it? Open the voice tool, press the mic and talk through an idea you've been meaning to post.
Questions
How long should an X thread be?
Long enough to make the point and no longer. Most good threads land between three and eight posts. If you're past ten, ask whether it should be an article or two separate threads.
Should I number the posts in a thread?
Numbering such as 1/5 tells readers how long the thread is before they commit, and it helps when a single post gets shared on its own. It costs a few characters per post. For short threads of two or three posts it's optional.
Is it better to post a thread all at once or reply one by one?
Both produce a thread. Adding every post in the composer with the plus button and publishing together is faster and avoids gaps. Replying one by one lets you check each post on the timeline as you go.