“What If My Boss Sees This?” — Posting Publicly While You Still Have a Job - MAC164

You've written the post. It's good. It's a real lesson from a real project, and you know it would help somebody. Your thumb is over the button, and a second voice shows up that has nothing to do with whether the post is any good: what if my boss sees this?

I've spent a run of episodes on public posting. In You Need to Be Posting Publicly (MAC-144) I made the case for why. In What to Post When You Think You Have Nothing to Say (MAC-153) I gave you the catalog of what to post. And in The Empty Result (MAC-154) we looked at whether anyone can actually find it. This episode is the objection I never fully answered in any of them. How do you build a public body of work while you still have a job, without leaking anything confidential, without badmouthing the place that pays you, and without your manager quietly concluding that you're halfway out the door?

The Fear Is Reasonable

Most advice on this topic treats hesitation as imposter syndrome. Just be confident, just share your journey, just hit publish. That isn't what's going on for most of the people I talk to. They aren't worried that they have nothing to say. They're worried that they'll say the wrong thing. They signed an NDA they haven't read since their first week. They work somewhere with a social media policy they've never opened. And at some point they watched a colleague post something that seemed harmless and then get a call from HR. That isn't insecurity. It's pattern recognition.

So I'm not going to tell you the fear is wrong. I'm going to tell you it's aimed at the wrong target. When you unpack it, it's two fears tangled together. The first is the fear of leaking: saying something about a client, a number, a project, or a person that isn't yours to say. The second is the fear of signaling: posting in a way that makes your manager wonder whether you're looking. Those are different problems with different fixes, and the reason most people stay frozen is that they never separate them.

Visibility vs. Exposure

Here's the distinction I want you to carry out of this episode. Visibility means people can see how you think: your judgment, your expertise, the way you approach a problem, the lessons you've drawn from the work. Visibility is about you. Exposure means people can see things that aren't yours to show: your employer's clients, numbers, internal decisions, a colleague's mistake. There is a second kind of exposure too, which is your own plans. Anything that tells the world, and your manager, that you're looking for the exit is exposure. Exposure is about them, or about your next move.

Most people treat these as the same thing. They assume any public presence carries exposure risk, so the safe choice is silence. But silence isn't safe. It's just invisible. As we covered in the Empty Result episode, when someone with the power to change your career goes looking for you and finds nothing, they don't conclude "no data." They draw a conclusion about you. And the people searching aren't only recruiters. Managers look you up. Skip-levels look you up. The VP deciding who gets the new initiative looks you up. The goal isn't to avoid being seen. The goal is to be visible without being exposed.

Now the signaling fear, which is the one people talk about least and feel most. What actually makes a manager wonder if you're leaving? It's mostly not posts about your field. People who study the mechanics of quiet job searches point out that the clearest signals are statements about your plans: a headline announcing you're seeking a new position, membership in job-hunting groups. Regular posts about your profession read as what they are, a professional who's engaged in their field. A post about how you think through a vendor negotiation says I'm good at my job. A headline that says open to new opportunities says I'm leaving my job. One is visibility. The other is exposure.

A strong public presence, done well, also does something for your current employer. It makes them look like a place with thoughtful people in it. Not because you're writing press releases, because you shouldn't be a corporate mouthpiece, but because a smart practitioner who happens to work there is good for everyone. Engaged reads very differently from disloyal.

The Abstraction Ladder

That handles the signaling fear. The leaking fear needs a tool rather than a reframe, and the tool is what I call the Abstraction Ladder. Every piece of work you do can be described at three levels, three rungs on a ladder.

The bottom rung is the situation: the specific thing that happened. Who, what, when, how much. Names, numbers, the client, the internal fight. The bottom rung belongs to your employer. The middle rung is the pattern: what tends to happen in situations like this one, anywhere. The specifics are stripped out but the shape remains. The top rung is the principle: the lesson that would hold in any company, in any industry, in any year. The rule is simple. You post from the middle rung or the top rung. The bottom rung stays inside the building.

Let me walk one example all the way up. Imagine you just finished a project consolidating three regional vendor contracts into one. It took six months and it saved real money. The hardest part wasn't the negotiation with the vendor. It was the regional team in one office who'd had a relationship with their old supplier for a decade and fought the change at every step.

On the bottom rung, that story sounds like this: "We consolidated our three regional freight vendors into a single contract, saved one-point-two million dollars, and the Midwest team fought us the whole way." Every word belongs to your employer: the vendor, the savings figure, the team that resisted. You don't post that.

Climb one rung and you get the pattern: "When you consolidate vendors across regions, the negotiation is rarely the hard part. The hard part is the local team that's losing a relationship they built, and nobody budgets time for that." Same story, nothing identifiable, and still specific enough to help someone about to run the same kind of project. Climb one more and you get the principle: "Every consolidation project is a change-management project wearing a procurement badge." That one you could put on a slide at a conference.

This works far beyond procurement. A marketing manager who just ran a rebrand has a bottom rung of agency, budget and an executive who hated the new logo, and a middle rung that rebrands stall in the approval chain far more often than in the creative work. A software team that just finished a painful migration has the same three rungs. The ladder doesn't care what department you're in.

Here's what surprises people: the middle and top rungs are the parts readers actually want. Nobody outside your company cares which vendor you picked. They care what you learned that they can use on Monday. Consultants who think carefully about sharing expertise without giving away their intellectual property make exactly this move. They turn detailed execution into principles, frameworks and diagnostic questions, and keep the templates, workflows and internal decision logic private. You're doing the same thing as an employee rather than a firm.

Two Tests Before You Post

The ladder tells you where to post from. You still need a way to check that you actually climbed. I run two tests on anything before it goes out.

The first is the recognition test. Practitioners who write case studies about client work covered by an NDA use a version of it: could the client read this and recognize themselves? I'd widen it. Could your client, your colleague, your competitor or your CEO read this and identify the company, the project or the person? If yes, you're still on the bottom rung. Replace names with generic descriptors, "a regional distributor" instead of the company's name. Turn exact figures into approximations or drop them. Remove the one detail that makes the story unique.

The second is the any-employer test. Would this post still be true if you worked somewhere else? If the lesson only makes sense inside your company, it's probably a situation, not a pattern.

And one more thing, because it's where good people slip: tell the story without a villain. The regional team that fought the vendor change isn't the bad guy in your post. They were losing something real, and the system hadn't given anyone time to manage that. That's not just safer. It's more accurate, and it's the more useful lesson. If your post needs someone to be the idiot for the point to land, you haven't found the point yet.

In plain terms: safe to share are how you think, the frameworks you use, the questions you ask at the start of a project, lessons with the specifics stripped out, and opinions on your field. Not safe to share are screenshots, internal numbers, client and vendor names, org charts, anything about a specific colleague, and anything that only makes sense if the reader knows where you work.

Start Quiet, Stay Steady

One more thing decides how your posting lands at work, and it isn't the content. It's the pattern. Think about how this looks from your manager's side. A person who has posted nothing for five years suddenly starts posting every day, updating their profile and connecting with people at other companies. Even if every single post is clean, the pattern says something changed. The pattern is a signal separate from the posts.

So start quiet. One post a week for the first month, not daily, and not in a burst after a frustrating meeting. A steady drip looks like a practice. A sudden flood looks like an event. It's the same rhythm we talked about in the What to Post episode.

Then do the thing almost nobody does: tell your manager before the internet does. You don't need permission to have a professional presence. But you want the first time your manager notices your posts to be a moment they've already heard about from you. In a one-on-one it sounds something like this: "I'm starting to write a bit publicly about how I approach [your area]: general lessons, nothing about our clients or projects. I'm doing it to build my own expertise and to get better at explaining things. Is there anything about our work you'd want me to steer clear of?"

That last question does a lot of work. It tells your manager you've already thought about the boundary, it gives them a chance to name anything specific to your role, and it turns your public work into something they're in on rather than something they discovered. If you're already sending the monthly note from Busy Is Not Visible (MAC-161), mention it there too. No surprises is the whole game. And if your manager reacts badly to a reasonable, well-framed version of that conversation, that tells you something about the environment. It doesn't tell you to stay invisible. It tells you to be more careful about where you invest your career.

Some practical notes for once you start. Your posts will draw comments, messages and the occasional recruiter. That's the point; it means you're findable. You don't have to respond to recruiters publicly and you don't have to hide from them. Polite and private is fine. You also don't need to lock your profile down or hide your connections, because hiding things tends to look worse than the thing itself. And if a post ever goes wrong, because you misjudged a detail or someone at work raised an eyebrow, the recovery is short. Take it down, tell your manager yourself before they hear it elsewhere, adjust your filter and keep going. One misjudged post is a correction. Going silent for good is a much bigger cost.

Your Action Plan

There are five steps. First, find and read your actual policy: the social media policy, the external communications policy, the code of conduct, and the confidentiality section of anything you signed when you joined. Ten minutes replaces a vague fear with a specific list. Second, walk one recent win up the Abstraction Ladder, writing the bottom rung for yourself only and then the middle and top rungs. The middle rung is your first post. Third, run the recognition test before you post by reading the draft as your client, your competitor, a colleague and your CEO. Fourth, tell your manager before the internet does. Use your own words; this one is a conversation, not a prompt. Fifth, put four posts on the calendar, one a week from the middle or top rung, with no burst and no headline change.

Go back to that moment with your thumb over the button and the voice asking what happens if your boss sees it. If you've climbed the ladder, run the tests and had the conversation, the answer is that your boss sees someone who's good at their job and thinks clearly about it. That isn't a risk. That's the point of posting. Share the thinking. Keep the project. Visibility is about you. Exposure is about them.

Get the Episode + Prompts

The full episode and show notes are at managingacareer.com/164. Three of the action-plan steps come with a prompt you can paste into whatever AI assistant you use. They help with the part people are worst at, which is seeing their own work the way an outsider would. Copy them, and change them to fit how you actually work.

Prompt — the policy read.

I'm going to paste my employer's social media / external communications policy and the confidentiality section of my employment agreement. List every specific restriction they place on what I can post publicly, quoting the exact sentence each one comes from. Then list anything that is ambiguous and that I should ask HR or my manager about. Do not interpret beyond what the text says, do not give legal advice, and if a section seems to be missing or the text is incomplete, tell me what's missing rather than guessing at what it would say.

Prompt — the climb.

Here are my private notes on a recent project, including details that are confidential. Do not repeat any names, client or vendor names, exact figures, dates, or internal details in your answer. Rewrite the story at two levels: (1) the pattern — what tends to happen in projects like this anywhere, specific enough to be useful but impossible to trace to my company; (2) the principle — a one-sentence lesson that would hold at any employer. Don't add details or results that aren't in my notes. If my notes are too thin to find a real pattern, ask me questions instead of inventing one.

Prompt — the red team.

Read the post below as four people: a competitor of my employer, a client, a colleague on my team, and my CEO. For each, list any detail that could let them identify my company, the project, the client, or a specific person, and anything that could read as criticism of my employer or as a sign that I'm job hunting. Quote the exact phrase each time. Don't rewrite the post and don't tell me it's fine if you aren't sure. If nothing is identifying, say so plainly.

Links & References

• Research & sources — LinkedIn Stealth Job Search — Job-Hunt.org
• Research & sources — How Do I Build Trust Without Giving Away IP — The Pedowitz Group
• Research & sources — How to Write a Case Study When Your Client Work Is Under NDA — Fueler
• Related Managing A Career episodes — You Need to Be Posting Publicly (MAC-144)
• Related Managing A Career episodes — What to Post When You Think You Have Nothing to Say (MAC-153)
• Related Managing A Career episodes — The Empty Result (MAC-154)
• Related Managing A Career episodes — Busy Is Not Visible (MAC-161)

TAKE THE SURVEY!

Are you looking for a career coach? If you reach out to me via the contact form, I will arrange an introductory session where we can talk about your career goals and how I can help. If we're a good fit, we can schedule regular coaching sessions.