What to Post on LinkedIn When You Have Nothing to Say

The blank page isn't the problem

Something happened this week. You had a conversation that surprised you. You made a decision you second-guessed. You noticed something in your industry that nobody's talking about. You got a question from a colleague that made you realize you'd never actually explained your thinking out loud.

The problem isn't that nothing happened. The problem is that none of it feels like a post yet. The gap between "this happened" and "this is worth writing about" feels enormous. It isn't. The gap is just a question — specifically, the right question to ask about what you already lived through.

According to Orbit Media's annual blogger survey, the #1 obstacle for content creators isn't time or skill. It's generating ideas. Which is a solvable problem, because the ideas are already there.

Stop waiting for the milestone

Most people treat LinkedIn like a press release channel — they only post when something big happens. A new job. A promotion. A company announcement. A product launch.

But the people getting consistent engagement aren't posting big news. They're posting small observations. The thing they noticed in three consecutive client calls. The decision they almost made wrong. The pattern they keep seeing that nobody else seems to be talking about.

Milestone posts get a spike and then disappear. Consistent, specific observations build a presence. The difference is showing up every week with something real — not waiting six months for something worth announcing.

The best posts on LinkedIn aren't announcements. They're dispatches. Small, specific things from the inside of a job that people on the outside can't see.

Six places to look when you think you have nothing

These aren't prompts to fill in. They're places to look in your actual week.

**A decision you made and why.** Not the outcome — the reasoning. Why did you choose that option over the alternatives? The thinking behind a decision is almost always more interesting than the decision itself.

**Something that surprised you.** A customer reaction you didn't expect. A metric that moved in the wrong direction. A competitor doing something you hadn't anticipated. Surprises are interesting because they mean your model was wrong — and explaining why is worth sharing.

**A question you keep getting asked.** If three people have asked you the same thing, ten more are wondering it. Answer it in public. You've already given the answer privately — now give it once where everyone can see it.

**Something you changed your mind about.** Changed minds signal credibility. They show that you actually think, rather than just repeating positions you already held. "I used to believe X. I don't anymore. Here's what changed." That's a post.

**A mistake and what it cost you.** The posts that generate the most trust are honest failures with a specific lesson attached. Not "I failed and here's my generic takeaway" — specific failures with specific consequences and one thing you'd do differently.

**Something you read that changed how you think.** Not a summary of the piece. Your reaction to it. "I read this and it made me realize X, which means Y for how I approach Z." That's different from a book report. That's a perspective.

The one test that separates good posts from generic ones

Before you write anything, ask one question: could someone else with your job title have written this?

If a random VP with your role, or a product manager in your field, or a founder in your space could have posted the same thing — it's not specific enough. You're writing from the category, not from your actual experience.

Generic: "Every marketer needs to remember that data beats assumptions."

Specific: "I ran a campaign with a $40k budget last quarter. It underperformed our projection by 60%. Here's the assumption I made that killed it."

The specific version can only come from you. That's why it gets engagement. That's why it builds trust. That's why the algorithm rewards it — LinkedIn's 360Brew system is explicitly designed to surface content from people with real credentials and real experience, not content that reads like it could have been generated from a prompt.

You don't have to figure out the post — just the story

The hardest part isn't writing the post. It's extracting the story from the week.

If you can answer any of these out loud, you have the raw material for a post: • What happened this week that you didn't expect? • What did you decide, and what was the alternative you almost went with? • What did a client, customer, or colleague say that made you stop and think? • What would you do differently if you could go back? • What did you figure out this week that you didn't know last week?

Once you have the specific answer, the post is mostly there. The details are what make it worth reading — a dollar figure, a specific quote, a timeline, an outcome. Strip those out and you have a generic post. Keep them in and you have something only you could have written.

Say Something turns a two-minute answer to any of these questions into three full draft posts — written in your voice, with your specifics, none of the filler. But even if you're writing manually: the story comes first. The post follows.