Why the week looks empty
Things worth posting about do not feel notable at the time. A decision you made on Tuesday felt like a decision, not an insight. The explanation you gave a colleague felt like answering a question. The thing that went wrong felt like a problem to solve. None of them announced themselves, and by Sunday they have all flattened into an unremarkable week.
This is a capture problem with a capture fix: write things down as they happen, in whatever state, into one place. Everything below is for the weeks when that did not happen and you are sitting in front of an empty file anyway.
Seven prompts that reliably produce something
These work because each one interrogates a week you have already had, rather than asking you to invent a topic.
1. What did you explain to someone? Any explanation you gave more than once is a post. You have already done the hard part — working out how to make it clear to a specific person — and the fact that it needed explaining is evidence somebody wanted to know.
2. What did you get wrong? A position you have changed is more interesting than a position you hold, because it comes with evidence. "I used to think X, here is what changed my mind" is nearly always a better post than "X is true", and it is far harder for anyone else to write.
3. What do people keep asking? A repeated question is a topic with demonstrated demand. If three people asked it, several hundred wondered. Answer it properly once.
4. What did you decide not to do? Decisions against are more informative than decisions for, because the reasoning has to be explicit. Nobody writes these, which is exactly why they land.
5. What is obvious to you and not to others? The hardest to see, because expertise makes things feel trivial. A useful proxy: what do you find yourself impatient about when others get it wrong? Impatience is a reliable marker of knowledge you have stopped noticing you have.
6. What did something actually cost? Real numbers, real timelines, real trade-offs. Specificity is scarce and almost everything published about work is vague, so an honest account of what a thing took is disproportionately valuable.
7. What changed in your field this month, and does it matter? The useful version is not the news — it is the judgement. Everyone can link the announcement. Far fewer will say whether it changes anything, and being willing to say "this does not matter" is its own kind of credibility.
What to stop reaching for
Three things get written when the file is empty and all of them cost more than they return.
Generic advice. "Consistency is key." "Know your audience." True, unattributable, and indistinguishable from every other account. The test is whether a competitor could publish it verbatim. If so, it is not worth your slot.
Engagement bait. Questions with no real interest behind them, polls about nothing, "agree?". These sometimes produce numbers and they train an audience to treat you as noise.
Reposting someone else's insight with a thin frame. Quoting a study and adding "interesting stuff" is not a post. If you have a view on it, the view is the post; if you do not, skip it.
The common thread: each of these is written to fill a slot rather than to say something. A missed slot costs very little. A slot filled with something nobody needed costs a bit of the reason people follow you.
Building a capture habit that survives
The prompts above are a recovery mechanism. The actual fix is upstream.
One place, always. Not three. Whichever is fastest to open on a phone mid-conversation, because that is when most of it occurs.
No quality bar at capture. "the invoice thing" is a valid note. The entire value of the capture file is that it is cheap enough to use while distracted, and any requirement to be articulate destroys that.
Capture the trigger, not the topic. "explained why we dropped the second provider to M" is far more useful in a week's time than "reliability". The trigger carries the specifics; the topic has already lost them.
Review it at the start of the writing block, not the end. Reading the file is what turns a blank page into a choice between five options, which is a completely different task.
A capture file with fifteen entries makes the weekly writing block easy. The same week with no file makes it feel like there was nothing to say — and it was the same week.
When it is genuinely dry
Sometimes it really is thin: a quiet stretch, repetitive work, nothing new. Two honest options.
Use the post buffer. This is what it is for. A fortnight of queued posts means a genuinely empty week costs nothing at all.
Go deeper on something already published. A post that did well is usually the compressed version of something longer. The mechanism behind it, the exception, the thing you left out for length — these are not repetition, they are the detail that was cut.
What not to do is drop the cadence without deciding to. A skipped week that nobody chose becomes two, and the account goes quiet for a month with no decision having been made.
Sources consulted: LinkedIn Help (linkedin.com/help) · Meta Business Help Centre (facebook.com/business/help)
Common questions
How do I come up with social media content ideas?
Interrogate the week you have already had rather than inventing topics. What you explained to someone, what you got wrong, what people keep asking, and what you decided against all reliably produce specific posts. Ideas feel scarce mainly because nothing was written down while it was happening.
Is it better to post nothing or to post something generic?
Post nothing. A missed slot costs very little, while a generic post spends the attention of people who followed you for something specific. The test is whether a competitor could publish the same text verbatim — if they could, it is not worth the slot.
How far ahead should I keep content ideas?
Keep a continuously captured list rather than a planned calendar of topics. Around two weeks of finished posts as a buffer, plus a capture file you add to as things occur, handles both the quiet weeks and the timely material. Planning topics months ahead tends to produce posts that no longer fit by the time they are written.
Should I repurpose old posts?
Going deeper on something that already worked is not repetition — a post that did well is usually the compressed version of something longer, and the mechanism or exception you cut for length is a genuine post. Republishing the same content unchanged is a different thing and is worth much less.
What is the fastest way to turn a note into a post?
Start from the specific thing that triggered the note and write it as you would explain it to the person who prompted it. Most of the time spent turning notes into posts goes on trying to generalise first, which removes exactly the detail that makes a post worth reading.
PostWharf is priced per workspace rather than per connected channel, and every plan carries unlimited channels. See per-brand pricing.