LinkedIn Post Ideas: 30 Questions That Turn Your Work Into Posts

Most lists of LinkedIn post ideas give you formats: share a lesson, celebrate a win, post a behind-the-scenes photo. A format is a useful start, but it has no content in it. Ask ChatGPT for "a post sharing a lesson I learned this year" and you get a lesson nobody learned, written in the patterns readers already skip (we covered those in How to make AI writing sound human).

The ideas below are written as questions instead. Each one points at a specific place in your work where a post is already sitting: a decision, a client conversation, a number, a mistake. Answer the question in three to five sentences, and you have the core of a post. Format comes second.

How to use this list

Pick one question and answer it as if a colleague asked you over coffee. Then check the answer for one of these: a number, a date, a name of a tool or a place, words someone actually said, a decision you made. If it has one, it's a post. If the answer is something like "communication is key", move to the next question; that one doesn't have your material in it yet.

You don't need all 30. Most people find four or five questions that keep producing posts for them and come back to those every week.

From your decisions

1. A decision you'd make differently. What did you decide in the last month that you'd now decide another way, and what changed your mind? The interesting part is what you knew then and what you know now.

2. A trade-off you made on purpose. What did you knowingly give up last quarter, and what did you get for it? Readers rarely see the cost side of a result.

3. A best practice you skipped. Which standard advice did you ignore, and what happened? Say whether it worked; a skipped practice that backfired makes an equally good post.

4. A tool you stopped using. What did you drop, when, and what do you use instead? Name the tools. A comparison from someone who used both is worth more than a feature table.

5. A number that changed your mind. Which metric surprised you recently, and what did you do the next day because of it?

From clients and colleagues

6. The question you answer every week. What do clients, juniors or new hires ask you again and again? Write down the answer you usually give out loud, in your own words.

7. A misunderstanding. Where did a client expect one thing and you delivered another? What do you now say at the start to prevent it?

8. A sentence that stuck. What did a client, manager or candidate say that you still think about? Quote only real words, and ask before you name anyone.

9. A request you turned down. What did you say no to, and how exactly did you phrase it? People save posts like this because they need the wording.

10. Credit to a specific person. Whose work made your last result possible, and what exactly did they do? "Thanks to the team" says nothing; "Dana rebuilt the import over a weekend" says a lot.

11. Criticism that turned out to be right. What feedback on your work annoyed you at first and later proved correct?

From mistakes and problems

12. A mistake with a price. What went wrong, what did it cost in hours or money, and what check do you run now because of it?

13. A task that took three times longer than planned. Where did the time actually go? Estimates are a topic almost everyone in your field has an opinion on.

14. An assumption that was wrong. What did you believe about your customers, your market or your team that turned out to be false? How did you find out?

15. An experiment that failed. What did you try, what was the result in numbers, and what won't you try again?

16. A warning sign you missed. Looking back at a problem, what was the first signal, and why didn't it look like one at the time?

From how you work

17. Your process, including the boring parts. How do you actually do one recurring task, from the first step to the last? The boring steps are usually the ones readers didn't know about.

18. A template or checklist you use. Share it, with a line on why each item is there.

19. How you prepare for one kind of meeting. A sales call, a performance review, a kickoff: what do you do in the hour before?

20. Before and after. Something you rewrote or redesigned: an email, a slide, a pricing page. Show both versions and say what changed and why.

21. Where your week really goes. Track one week of work and share the split. It's often far from what your job title suggests.

22. A small habit that saves time. One thing you do every day that others in your role usually don't.

From your field

23. Common advice you disagree with. Which popular advice in your field doesn't match your experience, and what happened when you followed it? The experience is what makes this more than a hot take.

24. A shift you see from the inside. What's changing in your work that hasn't reached the news yet? Describe what you saw, not what it means for the future of the industry.

25. A term people misuse. Which word in your field do clients or newcomers use in the wrong sense, and what problems does that cause?

26. Your job explained to an outsider. How would you explain what you do to a friend from a different industry, with one example from last week?

27. Two approaches you've tried. You did the same task two ways. Which was faster, which held up better, and in which case would you still pick the other one?

From your path

28. Why you're in this field. The specific moment or person, not the general motivation.

29. A milestone with the work behind it. If you announce a launch, a promotion or a client win, add the part people don't see: what took the longest, what nearly went wrong.

30. What you're stuck on now. A problem you haven't solved yet. Posts in progress get some of the most useful comments, because readers can actually help.

Keep the answers when they happen

Most of these answers show up on a Tuesday afternoon, in the middle of work, not when you sit down to write on Sunday. By then the detail is gone: the exact number, what the client said, the order things happened in.

Keep one place for notes and write down a line and the detail when something happens. "Client asked again whether we do audits; third time this month" is enough. When it's time to write, you pick from real material instead of staring at a format.

Elynd helps you write posts like this from your own material - try it free

From answer to post

Once you have an answer with a real detail in it, most of the work is done. A few things to keep in mind when you turn it into a post:

• One episode, one point. If the answer has three lessons, you have three posts.
• Start with what happened. Skip the setup that promises a twist. The episode is interesting enough.
• Keep your own words. If you use AI to draft, paste your answer first and ask it to keep your phrasing. Then check the draft against the patterns that give AI text away and read it out loud.
• End when the story ends. A closing question to readers works only when the post gives them something specific to answer.

If you post once a week, a list like this lasts for months. Questions 6, 12 and 17 alone can fill a quarter, because the answers change as your work does.