One 1,800-word article yields 7 short posts if you mine it for atomic ideas
Each post carries one claim, one number, one takeaway
Write the long piece first, then split, never the reverse
A 15-minute repurposing pass feeds a full week of distribution
One long article has enough material for a week of short posts, but only if you write the article first and split it second. I used to do it backwards. Now I draft the full piece, then run a 15-minute pass that pulls seven standalone posts out of it.
Here's the method I use every single time.
Why The Long Piece Comes First
Most people try to write short posts and then stitch them into an article. That order fails. Short posts are fragments. When you glue fragments together you get a draft with no spine, and the seams show.
The long piece forces you to think the whole thing through. You build an argument, you support it with examples, you reach a conclusion. By the time you're done you've already made every decision a short post needs: what the claim is, what the number is, and what the reader should do.
So the long piece is the raw ore. The short posts are what you refine out of it.
I write the article to be genuinely complete on its own. 1,800 words, four sections, real examples. It has to stand without any of the short posts existing. If the article depends on the posts to make sense, I've done it wrong.
Then I read it back with a different job in mind. I'm not editing anymore. I'm hunting for atomic ideas.
An atomic idea is the smallest unit of the article that still says something true and useful by itself. It's one claim with one supporting detail and one takeaway attached. If you can't pull it out and have it make sense to someone who never read the article, it's not atomic yet. It's still attached to something.
A good 1,800-word article has somewhere between seven and twelve of these. I only need seven for a week, so I pick the strongest ones and leave the rest.
The trick is that none of these feel recycled, because each one was always a distinct idea. I'm not saying the same thing seven ways. I'm saying seven different things that happened to live in the same article.
The reader who saw all seven on social and then read the full piece feels like they got a preview, not a rerun.
This same discipline shows up in how I name things across projects. If you want the deeper context, The Command Naming Convention Every RAXXO Tool Follows covers the naming logic I reuse here.
The Atomic-Idea Pass, Step By Step
I open the finished article and a blank note side by side. Then I go paragraph by paragraph and ask one question: is there a claim here that could survive on its own?
When I find one, I copy it into the note as a single line. I don't format it yet. I just capture the raw idea. By the end of a first read I usually have nine or ten lines.
Here's what three of those lines looked like for a recent piece.
"A demo GIF should load in under two seconds or it's a dead asset."
"The undo button matters more than any feature you'd put on a landing page."
"Browser tab titles are the cheapest branding you own and most tools waste them."
Each of those is a full thought. Each one has an opinion and a reason baked in. None of them needs the article to make sense.
Then I rank them. The best atomic ideas have a number or a sharp claim. The weak ones are vague ("good design matters"). I cut the vague ones immediately. Vague posts get ignored and they make the strong ones look worse by association.
Once I have seven ranked lines, I expand each into a short post. The format I use is simple: lead with the claim, add one or two sentences of why, end with the takeaway or a question. 40 to 80 words. That's it.
The one-number rule does a lot of work here. If a post has a concrete number it reads as true. "Load in under two seconds" lands harder than "load fast." I steal the numbers straight from the article, because I already did the thinking there.
I vary the shape of each post so the week doesn't feel like a template on repeat. One post is a flat statement. One is a question. One is a short list of two items. One is a confession about a mistake I made. Same source, seven different rhythms.
For the posts that reference a visual, I pull the exact asset from the piece. If you want the longer argument on that, The Demo GIF Every RAXXO Product Page Opens With walks through why the opening visual carries so much weight.
The whole pass takes about 15 minutes once the article exists. The hard work was already done when I wrote the long piece.
Scheduling Seven Posts Without Babysitting Them
Seven posts across a week means one a day. I don't post them manually. I'd forget by Wednesday.
I load all seven into a scheduler at once, right after the repurposing pass. Buffer handles this for me. I drop the seven posts in, set one per day at a fixed time, and walk away. The queue does the rest while I'm working on the next article.
The order matters a little. I lead the week with the strongest atomic idea, the one with the sharpest number. That's the post most likely to get shared, and it points people back to the full article while it's fresh.
I put the question-format post mid-week. Questions get replies, and replies keep a post alive longer than a statement does. Thursday is a good day for it.
The confession post, the one where I admit a mistake, goes near the end of the week. By then anyone following along has seen me make claims for four days straight. A little humility resets the tone and makes the next week's claims easier to trust.
One detail people skip: every post should link back to the long article, but not every post in the same way. If all seven say "read the full piece here," it reads like an ad campaign. So I rotate the approach. Some posts link straight to the article, while others just tease the idea and let it breathe. A few stand completely alone and never mention the article at all.
The standalone posts are the ones that travel furthest, because nobody shares an ad. They share an idea. When the idea happens to come from an article you wrote, the article gets found anyway.
I keep a running doc of which atomic ideas I've already used. That stops me from pulling the same claim out of two different articles and posting it twice a month apart. Overlap between articles is normal. Overlap between posts looks lazy.
If you're building this flow on a store, Shopify makes the article-to-post pipeline easier because the blog and the product pages live in the same place. The short posts drive to the article, the article drives to the product, and you never leave the ecosystem.
The Mistakes That Make Repurposing Feel Cheap
The fastest way to ruin this is to summarize the article seven times. A summary isn't an atomic idea. It's a watered-down version of the whole thing. Post seven summaries and your audience learns nothing new on days two through seven.
So I never summarize. I extract instead, and the difference is enormous. A summary says "here's what the article covers." An extract says "here's one true thing, in full."
The second mistake is padding weak ideas to hit a post count. If the article only has five strong atomic ideas, I post five. I don't manufacture two more to fill a seven-day calendar. A thin post costs you more trust than a missing day does.
The third mistake is formatting all seven identically. Same opening word, same length, same sign-off. The human eye catches repetition instantly.
By post three the reader's brain files you under "automated" and tunes out. Varying the shape isn't cosmetic. It's what keeps people reading.
I also avoid posting all seven in the same voice register. Some articles are technical. If every post is dense, the week feels like homework. I'll soften two or three of them into plain observations. The density stays in the article where people chose to read it.
One more thing I watch: don't give away the whole article in the posts. If the seven posts contain everything, there's no reason to click through. I hold back the connective tissue, the part where the ideas link into an argument. The posts are the highlights. The article is the story that connects them.
I learned the discipline of shipping a clean, reversible version of everything from building tools. Background: The Undo Button Every RAXXO Tool Ships With explains why I treat reversibility as a default, and the same instinct applies to publishing. If a post flops, I can swap it in the queue before it ever goes out.
The cheap feeling comes from effort mismatch. A recycled post feels cheap because no new thinking went into it. An extracted post feels fresh because it carries a real idea, just in a smaller container. Readers can tell the difference even when they can't name it.
Bottom Line
Write the long piece as if the short posts don't exist. Make it complete. Then mine it for seven atomic ideas, each with one claim and one number, and schedule them a day apart. That's the whole system, and it fits in a 15-minute pass after the article is done.
The payoff is the kind of output you only get from order. One draft, written once, feeds a full week of distribution without a single recycled sentence. You're not working harder. You're reading your own work with a sharper question in mind.
If you want the full operating approach I build everything on, start with the Claude Blueprint. It's the backbone behind how I draft long, split small, and ship consistently.
Try it on your next article. Finish the piece, pull seven lines, load the queue. Then tell me which post traveled furthest. My guess is the one that never mentioned the article at all.
This article contains affiliate links. If you sign up through them, I may earn a small commission at no extra cost to you. (Ad)
Top comments (0)