Most weeks I write one real thing. A blog post, occasionally a long changelog entry. Nearly everything else I publish that week is cut from it.
That is not a productivity trick I read somewhere. It is the only arrangement I have found where someone with a product to build can post daily without the posting becoming the job. Writing seven original things a week is a losing game. Extracting seven posts from one good piece is about an hour of editing.
The catch is that most people hear "repurposing" and picture pasting the same paragraph into five apps. That is cross-posting, and audiences can smell it. Repurposing is different: one piece of thinking, re-argued natively for each place it lands.
Here is the system I run.
Pick an anchor that can carry a week
Not every piece survives being cut up. The ones that do share a few traits.
They have structure. Sections, steps, a sequence of claims. Each of those becomes a post on its own. They contain at least one opinion you would defend in an argument. And they have specifics: a number, a workflow, a mistake, a before and after. Specifics are what make the derived posts feel like content instead of promotion.
What does not work as an anchor: reactions to news, thin listicles, anything where you mostly summarized other people's thinking. If the piece has no spine, the excerpts will not have one either.
The anchor does not have to be text. A video or a podcast episode works the same way, and often better, because you can pull clips as well as ideas. It just has to be yours, and it has to have enough in it.
Extract ideas, not summaries
The most common repurposing mistake is producing seven small summaries of the same piece. By Wednesday your audience has seen the same post three times in different clothes, and they stop reading you.
Instead, go through the anchor and pull out individual ideas, one line each:
- The single claim of each section.
- The strongest opinion, stated bluntly.
- The process, as steps.
- The example, with its specifics.
- The mistake you made, or keep seeing others make.
- The thing you changed your mind about.
That list usually comes out to six to ten lines and takes me about fifteen minutes in a plain text file. Each line seeds one post, and no two seeds overlap. The non-overlap is the whole trick. Summaries compete with each other for the same attention. Ideas do not.
If it helps, run the extraction on the piece you are reading. The opinion: cross-posting is not repurposing. The process: the five steps in the flow above. The mistake: the identical-text experiment I describe below. The example: the Monday hour. That is four posts already, from a piece that is not even a strong anchor by its own standards.
Map each idea to where it fits
Ideas have natural homes. The blunt opinion wants LinkedIn, where a strong first sentence still gets read. The process wants an X thread or an Instagram carousel, one step per post or slide. The example makes a good chart or screenshot post almost anywhere. The mistake makes the best short video for Reels, TikTok, and YouTube Shorts, because confession works face to camera, and one vertical clip covers all three platforms with no extra work. The conversational takes go to Threads and Bluesky, which both punish anything that reads like an announcement.
I do this mapping in the same text file as the extraction. One line per seed, with the platform and format noted next to it. It looks like nothing, and it is the closest thing this system has to a plan.
The map is allowed to have holes. Not every idea fits every platform, and forcing it produces exactly the filler this system exists to avoid. Some weeks my carousel slot is simply empty. Nothing bad happens.
If you are unsure how much each platform can absorb in the first place, I wrote separately about how often to post. Short version: the ceiling is how much you can make good, not how much the algorithm supposedly wants.
Rewrite native, or do not bother
For a while I pushed identical text to every platform. Same first line, same formatting, same link placement. It read fine on LinkedIn and like a press release everywhere else. I stopped.
The fix costs less than it sounds. You are not writing seven originals. You are redrafting one already-extracted idea with each platform's manners. A new first line every time, because the first line does most of the work everywhere and every feed truncates it at a different length. Plain speech on Threads and Bluesky. Room to develop the argument on LinkedIn. On platforms where links inside the post travel badly, the idea goes in the post and the link goes wherever that platform tolerates it.
Redrafting a seed takes a few minutes. The thinking already happened in the anchor. This step is arrangement, not composition, and it is the difference between an audience feeling like you showed up for them or at them.
Schedule the week in one sitting
Extraction and mapping are worthless if you then hand-post every day at whatever hour you remember. Batch it.
My sitting is Monday, right after the anchor ships. I redraft the seeds, spread them across the week, and space each platform so two derivatives of the same anchor never run back to back in one feed. The whole thing, extraction to scheduled queue, takes about an hour.
Order the week deliberately. The opinion or the strongest claim goes early, while the piece is fresh. The process and the example run mid-week. The mistake and the changed mind close the week, because those are the posts people actually reply to.
The mechanics of queues and timing are their own topic, covered in how to schedule social media posts. For the planning layer above it, you can build a working content calendar in an afternoon and slot this weekly batch straight into it.
Keep the leftovers
A good anchor is not spent after one week.
Seeds that did not make the cut go into a scrap file and fill slow weeks later. Posts that earned real replies come back a month later, reworded, because feeds are not archives and almost nobody saw the first run. And every reply thread where you found yourself explaining something at length is a draft outline for the next anchor.
Full disclosure: Planpost, the tool I build, now does the extraction step for me from a URL. But I ran this workflow manually for a long time with nothing but a text file, and it worked. The system is the point, not the tooling.
One good piece and one focused hour. If your calendar keeps running empty, the problem is usually not a shortage of ideas. It is that your best thinking gets published exactly once and then retires.