How to get LinkedIn ideas from your meetings

Publish the lesson, not the meeting

A meeting is not a post. It is raw material. If you publish it as it happened, you usually fall into one of two traps. You either share details nobody outside the room cares about, or you get too close to information you should not share.

The useful question is not what happened. It is what you understood better because of what happened. That might be a common customer objection, a confusion in your market, a product decision, a way to prioritize, or a communication mistake you keep seeing.

For example, you do not need to write that a specific client was worried about a deadline, a budget, or a proposal. The publishable idea might be that many decisions get stuck because the person does not need more information, they need to reduce the risk they feel. Now you are not talking about someone. You are talking about a pattern.

That shift protects people and improves the content. LinkedIn does not need the minutes from your morning. It needs an idea your reader can take back into their own work.

What parts of a meeting make good content

The best ideas often show up in the sentences that stay in your head after the call ends. A question that forced you to explain your work more clearly. An objection you have heard too many times to ignore. A small decision that reveals a bigger principle.

There is also useful content in the healthy tensions of work. Choosing between speed and quality. Saying no to a reasonable request. Simplifying something that was becoming too complicated. Admitting that one metric does not tell the whole story. These topics travel well because many people live through the same tensions, even in different industries.

Look at what you have had to repeat. If you explain the same thing in three different meetings, there may be a post there. Not because the market is slow, but because the idea may be poorly explained, the expectation may be unrealistic, or the question may not be getting a clear answer.

The signal is not always a grand insight. Sometimes it is a simple sentence that would have saved you time a few years ago. That kind of content is often more useful than an inflated recap of a busy workday.

Remove sensitive details without emptying the idea

Anonymizing a story is not as simple as changing a name and leaving everything else intact. If you keep the industry, role, timing, exact problem, and outcome, the person may still recognize themselves. Other people may recognize them too.

The safer move is to go up one level of abstraction. Instead of telling the case, explain the pattern. Instead of naming the company, describe the type of situation. Instead of quoting the exact sentence, reframe the question in more general terms. Instead of narrating the internal decision, explain the criterion you would use to decide.

Before publishing, run the idea through a simple test. If the person involved read the post, would they feel you had used the conversation to make yourself look good? If the answer is close to yes, you need more distance.

Removing sensitive details does not mean writing bland content. You can be specific without being indiscreet. You can talk about real problems without pointing at anyone. You can defend a point of view without turning a private meeting into a performance.

Avoid the corporate diary

The corporate diary starts when the post only proves that you worked. We had an intense meeting today. We learned a lot. We are building something big. It may all be true, but there is usually not much for an outside reader to use.

A better test is to ask what the reader can do with the post after reading it. Can they change how they explain something? Can they review a decision? Can they name a problem they already had more clearly? If the answer is no, you may only be documenting activity.

The alternative is to write from the work, not about the work. You do not need to share the meeting agenda. You can start from a conversation and turn it into an idea about sales, product, leadership, communication, hiring, strategy, or whatever subject you have real judgment on.

This also keeps you away from posturing. Every week does not need to become an epic lesson. Sometimes an honest observation, tightly framed and calmly written, is enough.

Capture the idea before it goes cold

Ideas that come from meetings have a short shelf life. If you wait until you have time to write, you may remember that there was something interesting, but forget the nuance that made it useful.

After a call, write down or record a short note with three things. What happened in general terms, what pattern you noticed, and what someone who was not there could learn from it. You do not need to draft the post right away. You only need to preserve the spark with enough context to recover it later.

Talking often works better because the conversation is still in your head. That is the logic behind Yapto too: capture a spoken idea when it appears, organize it later in your own writing voice, and turn it into a LinkedIn post, an X thread, a post for X, or a video script when that format fits.

The point is not to publish more meetings. It is to stop losing the ideas your own work is already giving you. When you separate what is publishable from what is private, LinkedIn depends less on inspiration and more on your daily judgment.

Frequently asked questions