Thread or one longer post? How to choose

Sooner or later every short-form writer hits the same fork. You have more to say than one post will hold. Do you break it into a run of short posts, each one a step, the way threads work on timeline sites? Or do you sit down and write one longer piece with a beginning, a middle and an end?

Neither is the grown-up choice. They are different tools and they suit different material. Here is how we would decide, and how to write each one well once you have.

What a thread does well

A thread is a sequence of short, self-contained steps. Each part can be read on its own, and each part moves the reader one notch further. That shape suits some material very well:

• Lists of separate tips. Seven things you learned editing other people’s drafts. Each tip stands up alone.
• Thinking in public. You are working something out and want readers to follow the steps, including the wrong turns.
• Running updates. A project, a reading challenge, a month of daily sketches. The story is the sequence.
• Material people will quote in pieces. If readers are likely to pass on one step rather than the whole, small units help.

The strength of a thread is momentum. Every part is short, so each one is easy to start. The weakness is that it is hard to build an argument that needs its parts held together at once. By step nine, the reader may have forgotten the condition you set up in step two.

What a longer post does well

A longer post gives you paragraphs, and paragraphs give you connective tissue: because, however, which means. That is what you need when the ideas lean on each other.

• Arguments. If point four only makes sense in the light of point two, keep them on the same page.
• Explanations with context. How something works, why a habit helps, what a term means and where it came from.
• Stories. A scene needs room to be set. Cutting it into separate posts breaks the spell every few lines.
• Anything people will come back to. A reference piece is easier to return to, bookmark and link as one page.

The cost is the start. A long post asks for a decision to commit before the reader knows whether it will pay off. That is why the opening and the headline matter more here, and why structure (headings, short sections) does a lot of the work of keeping people with you.

Four questions to decide

When we cannot tell which way a piece wants to go, we ask these, in order:

1. Can each part stand alone? If you could post step five by itself and it would still make sense, the material is thread-shaped. If it would not, lean towards one post.
2. Does the order matter, or the connections? A sequence (first this, then that) splits well. A web of connections (this, because of that, unless the other) does not.
3. Will people come back to it? Reference material, how-tos and guides tend to be revisited. A single page with headings is easier to revisit than a scattered run of posts.
4. How finished is your thinking? If you are still working it out, a thread lets you share as you go. If you know where you are going, a longer post lets you take the reader there efficiently.

You will not always get a clean answer. When in doubt, write it long first. It is easier to cut a finished piece into parts than to stitch loose parts into a whole.

Writing a thread that holds together

If you go with a run of short posts, a few habits keep it readable:

• Promise the shape in the first post. “Five things I changed in how I edit, one per post.” The reader knows how long the commitment is.
• Number the parts if the order matters. It costs a few characters and saves readers from getting lost.
• Make every part earn its place. A thread padded with a part that only says “more on this below” loses people at exactly that point.
• Link forward and back. On a blog, each part is its own page, so add a line at the end pointing to the next one and, where useful, back to the first.
• End with a part that pulls it together. One short post that says what the series added up to. Without it, a thread just stops.

Tags help too. Giving every part of a series the same tag means a reader who finds part three can find the rest in one click.

Writing a longer post people finish

If you go long, do the reader the favour of showing the map:

• Say what the piece covers in the first paragraph or two, plainly.
• Use headings that say something. “Why the first draft is too long” tells a scanning reader more than “Background”. On ReedSpot, long posts get a table of contents built from your headings, so good headings double as navigation.
• Keep paragraphs short but not chopped. One idea per paragraph is a good default.
• Front-load each section. The first sentence under a heading should tell the reader what the section is for.

A longer post is not a licence to ramble. If a section could be dropped without the reader noticing, drop it.

Moving between the two

The two forms feed each other. A thread that got a good response is often a draft of a longer piece: the parts are your sections, and the replies tell you where readers needed more. Going the other way, a long post can be summarised in a short run of posts that each point to a section of it.

What does not work well is posting the same text twice in two shapes. Rewrite for the form. A thread’s parts need to stand alone; a long post’s paragraphs need to connect. The ideas carry over, but the sentences usually do not.

For the single-post end of this spectrum, see writing a short post that stands on its own. For the long end, and how to grow a note into a full piece, see growing a short note into an article. And if you are unsure how tags, categories or the contents list work on your page, the help page covers them.