Most teams treat content like a tap. Every week it has to be turned on again, from nothing, and every week it runs a little slower. The way out is not writing more. It is reading one thing properly and getting five outputs from it.
A week of posts drawn from a single source reads as one argument seen from five angles, which is roughly how anyone comes to believe anything.
What counts as a source piece
Three kinds of thing qualify.
A report, yours or someone else’s, with numbers in it you can explain. A long interview, with a customer, a colleague or someone in your field, where a person said something you did not expect. A long post you already published and nobody read, because it went out on a Friday afternoon.
What they share is density. A source piece has to contain at least four separate claims, each of which could stand alone in front of a stranger. If you cannot list four before you start, you do not have a week. You have one post, and you should publish it and move on.
The test takes ten minutes. Read the piece with a blank page beside you and write down every sentence that would make someone stop scrolling. Fewer than four, pick another source.
One claim per post
The usual mistake is to summarise. A summary of a good source is a worse version of it, and it gives the reader no reason to go back to the original.
Split instead. Take claim one, give it a post of its own, and spend the whole post on it: what it means, why it holds, what it costs you to act on it. Then claim two, the next day, with no reference to yesterday’s.
A summary of a good source is a worse version of it, and it gives the reader no reason to go back to the original.
Some claims want a particular shape.
The counter-intuitive line, the one that made you raise an eyebrow while reading, becomes the cover of a carousel. Put it on slide one, alone, in the largest type the layout allows. The rest of the slides do the explaining, because a line that surprising needs somewhere to land.
The process, the how-we-did-it part, becomes the story set. Stories tolerate sequence and rough edges in a way the feed does not. Four or five frames, one step each, is enough.
The numbers become a single static post carrying one figure. One. A post with three numbers in it communicates none of them.
The honest overview of the whole source becomes the email.
The discipline here is that each post has to be readable by someone who has seen none of the others. No “as I mentioned on Monday”. If a post only makes sense as part four of a series, you have written a series, and series are read by the people who already follow you closely, which is not the group you were trying to reach.
The order of the week
Publish in the order that builds, not the order the source happened to use.
Monday takes the strongest claim, the one you would defend in an argument. Early in the week people are still choosing what to pay attention to, and a strong claim earns a follow.
Tuesday or Wednesday carries the carousel, because saved posts want a day when people have five spare minutes.
Thursday is the process, in stories. It will be the least polished thing you publish all week and it usually does the most for trust.
Friday takes the smallest claim, the aside, the thing you nearly cut. Low stakes, low effort, and it keeps the rhythm intact.
The email goes out on the following Monday.
Nothing about that order is sacred beyond the shape of it: strongest first, the format that needs attention in the middle, the rough human material near the end, and the leftovers where a miss costs nothing. Keep the shape and move the days to suit your audience.
Why the email goes last
Two reasons, one practical and one editorial.
Practically, by Monday you know which of the four posts actually landed. The email can lead with that one and give the others a line each. You have spent a week testing your own material on a live audience, for free.
Editorially, the inbox is the only place where a reader is alone with you. An email that arrives before the posts is an announcement. An email that arrives after them is a conclusion, and a conclusion is worth more.
Keep it short: a paragraph on what the source was, the claim that got the most response, and a link to the original piece. Nobody has ever unsubscribed from a newsletter for being too brief.
Where the source comes from
The hard part is usually not the split. It is having something worth splitting on a Monday morning.
Markowill’s news and content module is built for that gap. You add the feeds you already read as sources, and articles arrive on a schedule rather than waiting for you to remember. When one looks useful, you have it analysed: it comes back with a summary, an insights block and a relevance score, so scanning the list is quicker than scanning the sites.
From a single article you can generate content ideas, which land in an ideas list rather than straight into a draft, or create a post from it directly. Articles worth keeping can be pulled into a report with a trend analysis across the set, and into a newsletter whose sections each point back to the article they came from.
That last detail matters for this method. Because newsletter sections carry their article references, the Monday email and the week of posts are visibly drawn from the same reading, and you can see at a glance which sources you have already spent.
One constraint worth knowing: the AI actions on an article need a specific brand selected rather than the all-entities view, since a post, an idea or a report has to belong to somebody.
Where to start
Pick the last long thing you read that you can still quote a sentence from. Open a blank page, write four claims out of it, and publish the strongest one tomorrow morning.
If the four do not come, it was never a source piece, and you have lost ten minutes rather than a week.
