What to post on LinkedIn when you think you have nothing to say

When you have nothing to say on LinkedIn, stop looking for an opinion and report something that happened. A decision you postponed, a question two people asked you, a number you checked twice, a tool you gave up on. The reflex most people reach for instead is to ask the audience a question, and in our data that is the weaker move: within the productivity topic, 1,300 posts from 46 creators, a question mark appears in 28.2% of the topic's own bottom-half hooks and 13.1% of its own top decile. Having nothing to say is a filtering problem, not a supply problem. Below are 34 prompts that go and get the material back.

Why do you feel like you have nothing to say?

Because you are filtering against the wrong standard. Somewhere in the last few years the implicit bar for a LinkedIn post became “a fully formed insight that will change how somebody works”, and almost nothing in a normal week clears that bar. So you scan the week, find nothing that qualifies, and conclude the week was empty.

The week was not empty. You rejected the material. You had a meeting where two people disagreed and you sided with the quieter one. You spent forty minutes fixing something that should have taken five. You looked at a number and felt slightly sick. You decided not to hire someone and could not fully explain why. Every one of those is a post, and you discarded all of them within about a second each, for being too small, too obvious, or not resolved yet.

Unresolved is the one that matters most. People throw out the best material because they have not finished thinking about it, which is precisely the state in which it is most interesting to read. A finished conclusion is a lecture. An open question about something that actually happened to you is a conversation, and it is the only kind of post where the comments are worth reading.

What does the data say about reaching for a question?

This is the honest reason to write this article at all. When people run dry, they post a question, because a question requires no material. We can see what happens to those posts.

The productivity topic is the closest thing in our corpus to “posts about an ordinary working week”: 1,300 posts from 46 creators, covering focus, meetings, tools, habits and how people get through the day. The comparison below is within-topic. It ranks productivity posts against other productivity posts, then compares that topic's own top decile (130 posts, 10 authors) against its own bottom half (650 posts, 25 authors).

Two rows are doing the same work from opposite directions. Questions halve as you move up. First-person openings double. The posts that landed are the ones where somebody said what happened to them. The posts that did not are the ones where somebody asked the audience to supply the content.

The engagement distance is large. The median post in this topic's top decile drew 329 reactions and 92 comments. The median post in its bottom half drew 70 reactions and 3 comments. Reactions roughly quadruple. Comments go up about thirtyfold. Which is the joke buried in the question post: it exists to generate comments and it generates almost none, because “what do you think?” from someone who has told you nothing is not a question anyone owes an answer to.

Does that mean you should never ask a question on LinkedIn?

No, and the counterexample sits in our own data, which is a good reason to distrust anyone who gives you a universal rule about hooks.

Across the whole cohort of 12,988 posts, question marks appear in 19.0% of top-decile hooks and 14.2% of bottom-half ones, which runs the opposite way to the productivity topic. And within career growth content, 1,389 posts from 50 creators, the topic's own top decile (138 posts, 19 authors) says “you” somewhere in the hook 64.5% of the time against 34.4% in its own bottom half (695 posts, 33 authors). In some genres, pointing the sentence at the reader is exactly right.

The distinction that survives both findings: a question works when it is a real one you cannot answer alone, arriving after you have given the reader something. It fails when it is the entire post. “Are you struggling with focus?” is not a question, it is a stalling device. “I killed our Monday standup six weeks ago and nobody has asked for it back, which surprised me. What am I missing?” is a question worth answering, and it only exists because something happened first. More on this in the hooks study.

Where does an ordinary week actually hide postable material?

In six places, all of which you can check in under ten minutes. The prompts in the next section are organised by these sources rather than by post type, because “write a listicle” does not help a person who feels empty, and “open your sent folder” does.

What are 34 things you can post about from a normal work week?

Each of these is answerable in one sitting. Do not try to work out which will perform. Pick the one you already know the answer to and write that.

From last week's calendar

1. The meeting that changed your mind, and the sentence that did it.
2. The meeting that should have been an email, and what specifically made it one.
3. A recurring meeting you cancelled, and what happened in the three weeks after.
4. The thing you prepared for that turned out not to matter.
5. How you actually spend a Tuesday, hour by hour, without tidying it up.

From your sent folder and your messages

6. The long reply you wrote to one person this week. Publish it, minus the names.
7. The thing you have now explained three times and should have written down once.
8. A message you drafted and did not send, and why you did not send it.
9. The document you rewrote, and what was wrong with the first version.
10. A decision you communicated badly, and the version you would send now.

From questions people asked you

11. The question two different people asked you this month, answered properly.
12. The question you get asked that has no good answer, said out loud.
13. Something a junior colleague asked that you had stopped noticing was strange.
14. A question a customer asked that revealed you had explained something badly.
15. The question you wish people asked you instead of the one they ask.

From the work itself

16. A number you looked at more than once this week, and why it bothered you.
17. A tool you stopped using, and what you replaced it with.
18. A small process you fixed, described precisely enough that a stranger could copy it.
19. The part of your job that nobody outside it understands.
20. The thing that always breaks, and what you now do to catch it early.
21. The step you removed from a workflow, and what you were afraid would happen.
22. What onboarding a new person taught you about how your team really works.

From what you got wrong or changed your mind about

23. Something you believed two years ago and no longer do.
24. Advice you used to give and have stopped giving.
25. A decision you postponed this week, and what you are waiting for.
26. Something you said no to, and who was disappointed.
27. A mistake that cost you time, with the amount of time stated.

From other people

28. One person who did something specific well this week, named, with permission.
29. What you learned from watching someone worse at your job than you.
30. An idea you stole from another industry and applied badly.
31. A recurring complaint you hear from your customers, described in their words.

From what you read, watched or googled

32. The thing you googled this week that you were embarrassed not to know.
33. The article you disagreed with, and the specific paragraph that was wrong.
34. The idea you have repeated to three people since you heard it, and who to credit.

Notice how few of these require an opinion. Most ask you to report. That is deliberate, because reporting is available to you on a bad Tuesday and having a fresh insight is not. If you want these arranged into a repeatable weekly rotation instead of picked at random, the content calendar guide lays one out.

How do you turn a prompt into a post in ten minutes?

Write the fact first, in one plain sentence, before you try to make it good. “I cancelled our Monday standup six weeks ago.” That sentence is the post. Everything else is arrangement.

1. State the event in line one.No preamble, no “I have been thinking a lot about”. The event, mid-motion.
2. Add the cost or the risk in lines two and three. What it might have gone wrong, what it took, what you were afraid of. This is what carries a reader past the fold.
3. Say what happened next, in order, including the part that did not work.
4. Say what you now think. One sentence, and it is allowed to be tentative.
5. End on the part you have not resolved.Not “thoughts?”. The actual open question, which is a real one because you genuinely have not settled it.

Keep the whole thing under ten minutes on purpose. A post you spent an hour on is a post you will be reluctant to publish, and the reluctance compounds. The hook length worry is not worth your ten minutes either: across our whole cohort, median visible hooks run 206 characters in the top decile and 205 in the bottom half, so length is not where posts are won.

If you want more scaffolding for the arrangement step, the post templates library has structures you can drop material into, and the storytelling guide covers the ordering question in more depth.

What should you not post when you have nothing to say?

Five things, all of which feel like posting and none of which are. Each is recognisable because it contains nothing that could only have come from you.

• The empty question. Covered above. It is the most common filler on the platform and the data does not like it.
• The quote graphic.Someone else's sentence, in a serif font, on a gradient. It is a way of appearing in the feed without saying anything, and readers know it.
• The recycled listicle. Seven habits, five lessons, three things nobody tells you. If the list would be identical written by a stranger, it is not your post.
• Motivational Monday. The weekly greeting exists to maintain presence and maintains nothing.
• The reshare with “great read” on top. Shared article and link posts over-index in the bottom half of our cohort at 32.7% against 22.1% in the top decile. Within the productivity topic the same split is 22.6% against 13.1%. Sharing a link is not the sin. Sharing it with no argument attached is.

There is a real cost to filler beyond the post itself. Every empty post trains your audience that seeing your name is not a reason to stop scrolling, and that lesson survives long after the post is gone. If posts have stopped getting seen at all, the diagnosis is in our piece on posts that get no views.

That post is not clever and was not agonised over. It is a person showing you where they were at a moment when everyone was curious about exactly that. The bar is lower than you think in one direction (it can be small) and higher in another (it has to be actually yours).

What if your job is genuinely boring?

Then you are sitting on the best material on the platform and cannot see it, because you have confused “boring to me” with “boring”. Those are different properties. Your work is boring to you because you have done it four hundred times. It is opaque to almost everyone else, and opacity is the raw material of an interesting post.

The reliable move is to explain the unglamorous mechanics of something people only see the outside of. How a claim actually gets assessed. What happens to a purchase order between approval and payment. Why the stock is wrong even though the system says it is right. Nobody outside your function knows any of this, and the people inside it will argue with you in the comments, which is the best outcome available.

Two related angles work for the same reason. The first is the thing everyone in your industry knows and nobody says out loud, which reads as courage but is mostly just accurate reporting. The second is the number that surprised you when you first learned it: how long something really takes, how many people touch a document, what proportion of a day is spent waiting. You stopped being surprised by it years ago. Your reader has never heard it.

How small is too small for a post?

Smaller than you think, with one condition: it has to be something only you could have reported. A tiny specific thing beats a large generic one every time, because the large generic one has been posted four thousand times already this year.

A useful way to sort your candidates:

• Too small: a thought you had. Not an event, no detail, nothing anyone can check or use.
• The right size:a thing that happened, with a date attached and one consequence. “I moved our retro to Thursday and attendance went from four to nine.”
• Also the right size:a thing you noticed repeatedly, with a count. “This is the third client this year who tried to solve a pricing problem by hiring a salesperson.”
• Too big: anything requiring you to speak for an entire industry. That post has no evidence in it and you will end up writing platitudes to fill the space.

The failure mode almost nobody has is publishing something too small. The failure mode everybody has is scaling a genuine observation up into a general claim, losing the detail on the way, and publishing the version that could have been written by anyone.

Is it okay to skip a week?

Yes, and this is the section most articles in this genre refuse to write, because their premise is that you must publish.

A missed week costs you very little. Nobody is tracking your cadence, and the audience you imagine noticing your absence is not watching that closely. What does cost you is a run of posts you did not want to write, because filler is visible and it is the thing that teaches people to skip your name.

The distinction worth making is between a blank Tuesday and a blank month. A blank Tuesday is normal and the prompts above will fix it. A blank month, where nothing about your work feels worth describing to anyone, is usually not a content problem. It is tiredness, or a job that has stopped producing anything you are proud of, and no prompt list solves either. Take the month off and come back when there is something to report. Consistency is measured in quarters, not in weeks, and the posting frequency analysis covers what cadence actually buys.

How do you run a fifteen-minute weekly harvest?

The reason people run dry is not that nothing happened. It is that nothing was written down while it was still specific. By Friday the meeting has compressed into “a good meeting”, and the detail that would have made it a post is gone.

1. One line a day, ten seconds. Not an idea. An event: what you decided, changed, refused, fixed, or were asked. Anywhere you will actually look at it.
2. Friday, fifteen minutes. Read the five lines. Pick the two you have most to say about. Do not pick the ones you think are impressive.
3. Write the fact sentence for each, not the post. One sentence, plain.
4. Draft on Sunday, publish on the weekdays. Two posts a week from ten minutes of note-taking is a sustainable rate for almost anyone.
5. Keep the rejects.The lines you did not use are next month's bank, and they age better than ideas do, because events stay true.

One habit that multiplies all of this: read your own comments. The replies to your last post contain the questions your audience actually has, and answering one of them properly is a post that is guaranteed to have a reader. The comments strategy guide covers the wider habit.

What this analysis cannot tell you

These are correlations, not causes. We can say that question-shaped hooks are twice as common in the productivity topic's weakest posts as in its strongest, and we cannot prove that removing a question mark would improve anything. The topic's top group draws on 10 authors and its bottom half on 25, so author effects are mixed in with format effects. The cohort skews toward established creators, all with at least 1,000 followers and 65 accounts in total, so treat every figure as directional if you are starting small. Engagement counts are lifetime totals at the time of collection and post ages vary. And every text finding here describes the visible hook above the “see more” fold rather than the full body of the post, which is why this article says nothing about how long a post should be. The full method is in our study of 34,012 LinkedIn posts, and real examples from this topic sit on the productivity examples page.