How to post on LinkedIn without sharing confidential information

Start with the lesson, not the story

The safest way to write about your work is to begin with the idea the experience gave you. Before drafting the post, ask yourself what you learned, what changed in your thinking, or what advice you would give someone facing a similar situation.

When you start with the story, you tend to pull in details you do not need. The client’s name, the exact industry, the size of the company, the date, someone’s job title, or a sentence said in a meeting can feel like useful color. They can also make the post recognizable.

A good filter is to write the general point first. Instead of starting with “yesterday a client asked us to change the whole project two days before delivery,” you could start with “when a project changes at the end, the problem is rarely a lack of work; it is usually a lack of earlier alignment.” The second sentence already contains a useful idea without exposing anyone.

You can add context after that, but only what the reader needs. You do not have to prove the story happened by recreating every detail. You need the reader to understand the pattern and apply it to their own work.

Remove identifiers before you write the post

Anonymizing a post is not just replacing a company name with “a client.” That helps, but it is not enough. Some posts name nobody and still make the person involved easy to identify because of the combination of clues.

Review anything that could identify someone directly or indirectly. That includes names, very specific job titles, small industries, locations, dates, internal figures, proprietary tools, screenshots, direct quotes, and combinations of details that point too clearly in one direction.

The practical question is simple: if the person involved read this post, would they feel I had shared something that was not mine to share? If the answer is not a clear no, rewrite it.

It also helps to move away from the individual case. You can combine several similar experiences into one pattern, change the order of events, remove the exact timing, or write “in many teams, this happens when…” if the lesson does not depend on one specific scene. The goal is not to invent facts for effect. It is to remove unnecessary precision so you protect other people.

Use general context without making the idea empty

Some people are so afraid of revealing too much that they write posts so generic they say almost nothing. “Communication matters,” “you have to listen to the client,” and “processes help” are safe sentences. They are also easy to forget.

The middle ground is to describe the type of situation, not the full case. You can write “in projects with several teams involved,” “in teams that are growing quickly,” “when a technical decision affects sales,” or “in hiring processes with several decision-makers.” That context gives the reader a map without pointing to a specific person.

Then make the idea concrete through observable behavior. Instead of writing “you have to manage expectations,” explain what that means in practice: putting in writing what has been decided, who approves it, what is out of scope, and when it will be reviewed. That gives value without relying on sensitive information.

A professional post does not need to expose private details to be specific. It can be useful when it gets down to decisions, common mistakes, better questions, warning signs, or the criteria you use. That is often the part your reader came for.

Separate your experience from other people’s material

Not everything you experience at work is yours to tell. Sharing a professional lesson is one thing. Turning a private conversation, a client problem, or an internal company decision into content is something else.

Before publishing, separate what belongs to you from what belongs to other people. Your reflection belongs to you. So does your change in judgment, your way of approaching a situation, and the questions you took from it. Business data, internal tension, someone else’s mistake, private messages, and information you know because you are inside a trusted relationship do not belong to you.

If you are an employee, add another layer of caution. Even if you do not name your company, you may still reveal priorities, processes, clients, commercial challenges, or strategic information. If you are unsure, do not publish it, or move the idea to a more abstract level.

Professional trust is also built through what you choose not to say. Good judgment does not make you less transparent. It makes you more reliable.

Create a quick filter before you publish

A filter helps you avoid making the confidentiality decision in a rush after the post is already written. Use it whenever you turn a work idea into a LinkedIn post.

First, check for explicit confidential information. If the post includes internal numbers, names, documents, screenshots, agreements, proposals, private conversations, or client details, remove them. If those details are necessary for the post to work, the post may not be publishable.

Second, check whether someone could recognize themselves or someone else. Do not think only about the average reader. Think about colleagues, clients, suppliers, and people who know the context. If the story points to a specific person for them, generalize it further.

Third, ask whether the post offers a lesson without punishing anyone. If the text needs to make a person or company look bad in order to feel strong, you are probably using the experience badly. Shift the focus to what you learned, what you would do differently, or the judgment you recommend.

Many useful ideas show up when you are not sitting at your computer: after a meeting, on a walk, or on the way home. Capturing them by talking, the way Yapto is built to do, can help you keep the raw reflection. The final post still needs to pass through a filter of confidentiality and professional respect.

Frequently asked questions