--- title: "Content ideas from saved posts, without rewriting anyone" description: "Two thousand saves and still a blank composer. The four things you can honestly do with someone else's post, and the one everybody does that should stop." canonical: "https://www.linkedmash.com/blog/linkedin-content-ideas-from-saved-posts" last-updated: "2026-09-01" --- # Content ideas from saved posts, without rewriting anyone Two thousand saves and still a blank composer. The four things you can honestly do with someone else's post, and the one everybody does that should stop. Canonical HTML: https://www.linkedmash.com/blog/linkedin-content-ideas-from-saved-posts Agent-readable Markdown: https://www.linkedmash.com/blog/linkedin-content-ideas-from-saved-posts.md Last updated: 2026-09-01 By [Ramya Chinnadurai](https://www.linkedin.com/in/ramyachinnadurai/) · 2026-09-01 · 8 minute read Category: playbooks There is something absurd about staring at a blank composer with two thousand saved posts one tab away. You have spent a year collecting the most interesting things in your industry and you still cannot think of anything to say. That is not a discipline problem, and no amount of reviewing your saves more diligently will fix it. It is a category error about what a saved post is. ## Your saves are not material The instinct is to treat the library as a supply of raw content: find a good post, restate it in your own words, publish. This produces the specific kind of LinkedIn post everybody has learned to scroll past, and it fails for a reason worth understanding rather than just avoiding. You saved that post because it was already good. Restating it can only subtract. And you are publishing to roughly the same feed the original came from, so a meaningful share of the people reading your version have seen the better one. The gap between them is the impression you leave. What the library actually is: a year-long record of what you find interesting, gathered without you performing anything for anyone. That is a much rarer asset than a pile of source material, and it is useful in a completely different way. > Nobody needs your summary of a post they can read. They might need what you know that the author did not. ## Four things you can honestly do with someone else's post Every one of these requires you to bring something the original did not have. That constraint is the whole method: if you cannot name what you are adding, you are rewriting, and you should not publish it. ### 1. Disagree, with the specific reason The strongest posts in most people's libraries are the ones they saved while slightly irritated. Something was too clean, or true for a company with forty people and not for one with four. That irritation is the most reliable content signal you have, and it is the one people skip past because disagreeing publicly feels risky. The version that works is narrow. Not "this advice is wrong", which is a position nobody can check, but "this holds until you have a support team, and here is what broke for us before we did". You are not attacking anyone. You are adding the boundary condition the original left out, which is a genuine contribution and reads as one. ### 2. Apply it, and report what happened You read something, you tried it, it worked or it did not. That post costs you nothing to write because you already did the expensive part, and it cannot be written by anyone else, which is more than can be said for most of what gets published. **The one rule that makes this work** You have to have actually done it. An invented result is the fastest way to become someone whose posts are not worth reading, and it is obvious more often than people think, because real attempts have odd details and invented ones are tidy. ### 3. Connect two saves that do not know about each other This is the highest-value move and the one that only works if you have been saving for a while. Two posts, months apart, from people in different corners of your feed who would never read each other, making arguments that turn out to be the same argument, or the exact opposite one. Neither author can write that post. You can, because your library is the only place those two things sit next to each other. Nothing else you publish will be as difficult to replicate. ### 4. Translate it for people who would never see it Something excellent from a discipline next to yours, carried over with the terminology stripped out and the example replaced with one your audience recognises. Credit the original and link it. You are doing the work of moving an idea across a boundary it was not going to cross on its own, which is real work even though it feels like it is not. ## The pattern you can only see in aggregate All four moves above start from one post. The best ideas in a library are not in any single post at all: they are in the shape of the collection. You cannot see that by scrolling, because the thing you are looking for is a frequency, and frequency is invisible one item at a time. Ask across the library instead. The questions that produce the most are the ones about your own behaviour rather than about the content: - **What do the people I save disagree with each other about?** Every live disagreement in your industry is a post, and you have a year of evidence about which ones are actually live rather than merely loud. - **What have I saved five versions of?** Five saves on one narrow problem means you have been quietly researching it. You know more than you think you do, and you have almost certainly not written about it. - **What did I save a lot of last year and none of this year?** Something either got solved or got abandoned. Which one it was is a genuinely interesting post, and nobody else is positioned to notice it. Answers come back with the original posts attached as sources, which matters here: you want to reread the three saves behind a pattern before you build a claim on it. [More on asking your library](/chat-with-linkedin-saved-posts) if that is the part you want. ## From idea to draft without losing the thread The failure at this stage is mundane. You find the thing, you mean to write it up later, and later you have the fact but not the reason it seemed interesting. Draft while the reaction is still attached, even badly. Two sentences written in the moment beat a polished attempt three days after the feeling wore off. The composer opens with your saved posts beside it, so the source stays in view while you write against it, and it can shorten or sharpen a draft once the thinking is done. Use it on the second pass, not the first: a post that was written entirely by rewriting reads exactly like one. [Video: Drafting with the saved post still on screen, so you are writing against the source rather than from memory of it.](https://www.linkedmash.com/assets/blog/composer.mp4) Then schedule it. Not because posting times matter much, but because [a queue survives a bad week and a good intention does not](/blog/linkedin-posting-times-vs-consistency). If you want the full weekly loop this sits inside, [the 30-day system](/blog/linkedin-saved-posts-30-day-system) is the version with the cadence attached. ## The one to stop making "Ten lessons from the best posts I saved this month." It looks like the obvious use of a library and it is the worst one. It has no argument, so there is nothing to agree or disagree with; it flatters ten people, which is transparent; and it tells the reader what other people think rather than what you think, which is the only reason they followed you. Pick one of the ten. Say the thing you actually believe about it. That is a worse-looking post and a much better one. ## Frequently asked questions ### Is it okay to post about something I read in someone else's LinkedIn post? Yes, as long as you add something the original did not have and credit it when you are building directly on it. Restating a post with no addition is the version that reads badly, not the version that gets you in trouble. ### How do I get content ideas from saved posts without copying? Bring something the source lacks: disagree with a specific boundary condition, report what happened when you applied it, connect two saves that do not know about each other, or translate it for an audience that would never see the original. ### What is the best question to ask my saved posts library? Questions about your own behaviour rather than the content. What do the people I save disagree about, what have I saved five versions of, and what did I save a lot of last year and none of this year.