What to Post When You Have Nothing to Say - MAC153
Agreement is the cheapest thing you will ever get from an audience.
A few weeks ago I made the case that you need to be posting publicly — building a searchable body of work outside your company's walls, before the day you actually need it. You Need to Be Posting Publicly (MAC-144) laid out why. What came back, over and over, was people telling me they agreed. Completely. And then posting nothing.
This piece is the other half: what do you type into the empty box? I'm not re-litigating why you should post — that case still holds up. I want to take apart what happens in the four seconds after you agree with me, the moment you open the app, put the cursor in the box, and discover you apparently have nothing worth saying.
You do. Here's the proof, and a list you can run for the rest of your career.
The objection is not a shortage. When someone tells me "I have nothing to say," I've learned to hear a different sentence underneath it: I have nothing I'm qualified to say. Not that the well is empty — that they haven't been issued a permit to draw from it. One of those is a supply problem. The other is a permission problem. Only one of them is real.
This show exists because of that exact permission problem. When I started Managing A Career, I was trying to talk to myself — the version of me from five or six years earlier who couldn't get a straight answer from anyone. As I've told before, including in Using AI to Learn Leadership (MAC-128), I once asked what I needed to do to get to the next level, and the answer was "be more strategic." No roadmap, no definition, no next step. I had to run into the wall, back up, and figure it out myself — which is why I started this show.
A hundred and fifty-three episodes later, the well hasn't run dry. The person you were several years ago is an inexhaustible audience, because they keep having new problems you've already solved. I didn't run out of material. I ran out of the belief that I had anything worth saying — a very different problem, and one that doesn't fix itself with experience.
Here's what makes it stubborn: it doesn't get better as you get more senior. Researchers looking at why imposter syndrome so often intensifies rather than fades with experience point at a fairly cruel mechanism — the more you learn about your field, the more precisely you can see the edges of what you don't know. A novice doesn't know enough to feel unqualified. You do. Your own competence built the instrument that now measures your gaps.
Longtime listeners know I've circled this before. I called it a feeling in Faking It (MAC-083), and more recently, in Which Career Body Are You (MAC-152), I put a harder edge on it, because the research reframes it entirely. It isn't only a feeling — it's a measurement error, and it's the majority one: about two-thirds of professionals place themselves below where outside evidence puts them. Read that against the blank box: the odds are better than even that the person convinced they have nothing to offer is standing a full level higher than they believe.
The failure mode this produces isn't silence, which would at least be honest. It's safe posting — the congratulations comment, the reshare with no opinion attached, content kept shallow enough that it cannot possibly be wrong. That's not modesty. That's posting in a way that guarantees nobody learns your name.
Mastery vs. recency. So let's go after the permission problem directly, because the credential you think you need is not the credential that actually works. Being an expert at something makes you worse at teaching it, not better.
Think about the most knowledgeable person in your function — twenty years deep in forecasting, or brand strategy, or systems design. Watch what happens when a new hire asks them how something works. They're generous, patient, and almost always unhelpful, because the answer comes out as a finished object with the scaffolding removed. They skip steps without noticing and use shorthand they've forgotten isn't universal. They can't reconstruct the confusion; they haven't felt it in decades.
Now picture the person who learned that same thing eleven months ago. They still remember exactly where the trail went cold, which explanation didn't land, which thing looks obvious in the documentation but isn't. The expert knows more about the answer. You remember more about the question.
I know this in my bones — it's how I got into computers. My mom was taking a night class and wasn't understanding the material, so I picked up her textbook. I wasn't an expert; I was one or two pages ahead of her. But I could get her to understand what the textbook's own author couldn't, because I'd just been confused by the same thing and still remembered what it felt like. The author had forgotten that decades earlier.
I want to name that gap, because it's the single most useful idea in this piece. Call it the Recency Window — the period after you learn something during which you still remember what was confusing about it. It opens the moment the thing clicks and closes, quietly, as you get good. While it's open, you are the best possible teacher of that thing, to a degree the actual expert can't match no matter how generous they are. Being early in a skill is not a disqualification from writing about it. It's a wasting asset with an expiration date.
This isn't a private theory. The writer and developer Swyx built one of the more widely read essays on the internet around exactly this, arguing for publishing what he calls your "learning exhaust" — the notes and half-built explanations you generate while still figuring something out, rather than waiting until you're qualified to teach. The word worth holding onto is exhaust: a byproduct of work you're already doing, most of which gets thrown away.
That framing generalizes well past software. An accountant closing their first quarter under a new revenue standard generates exhaust. So does a marketing manager running their first campaign on an unfamiliar platform. Both are inside a Recency Window now, and both think they should wait until they're better at it. By the time they are, they'll have nothing to say — not because they know less, but because they'll have forgotten what it was like not to know.
Two years behind you. That's the qualification question answered. But there's a quieter assumption underneath it, and it's the one that actually freezes the fingers: who do you picture reading what you post?
I've asked people this, and the answer is remarkably consistent. They picture the most senior, most credentialed, most skeptical person in their field, and imagine writing up — presenting to a panel of judges who are all more qualified than they are and, in this fantasy, all in a bad mood. Of course you have nothing to say. You've cast the wrong reader.
Here's the correction, and it's the whole piece in one sentence: you are not writing for the expert above you. You are writing for the person about two years behind you — often just you, two years ago, with worse information and more anxiety. Someone in your organization, or three companies away, is sitting where you sat twenty-four months ago, staring at the same badly labeled system, about to spend weeks working out something you already know. Not because they're less capable. Because nobody told them, and you didn't have anyone to tell you either.
This is where "it's too obvious to post" collapses, because obviousness isn't a property of the information — it's a property of your relationship to it. The thing you're dismissing feels obvious for one reason: you already climbed past it, and you're reporting back that the view from the top is unremarkable. It wasn't obvious. You just already learned it. That's the measurement error again, felt from the inside: it doesn't feel like low confidence, it feels like accurate assessment, like everyone already knows this — a statement about the world, not about you, and exactly why it never gets examined.
So here's the pre-writing exercise: name the reader before you type a word. Not a demographic — a person. The analyst who joined in March. Your own self in the first ninety days of this job. Put one specific human on the other end, then just tell them the thing. Writing to a crowd is performance and it's terrifying. Writing to one person is just help, and everyone already knows how to do that.
Document, don't invent. Now the mechanics. There's a third, more expensive assumption hiding in "I have nothing to say": that content has to be made — conceived, drafted, polished, produced in time nobody has. Measured against that standard, of course the answer is no.
Gary Vaynerchuk has a phrase for the way out that's stuck around for a decade because it's correct: document, don't create. The distinction is structural, not stylistic. Creating means producing something that didn't previously exist. Documenting means noticing something that already happened and writing it down. One requires inspiration and free time. The other requires attention and fifteen minutes.
I live this every week. I manage a team, and this show's topics come from work I'm already doing. A team member raises a challenge in a one-on-one — a promotion conversation that didn't land, a skill gap they've just noticed — and mid-conversation I realize the thing I'm explaining to them is probably what a few thousand other people are also trying to figure out. That's not creation. That's noticing. Someone in the audience pushes back on something I said, or tells me "you covered X but never Y" — that's not inspiration striking, it's a request for the next episode, phrased as feedback on the last one. The habit builds the habit; I notice more now, at episode 153, than I did at episode ten.
And when none of that is flowing, I go back to recent episodes and look for something that deserves a deeper dive. This piece is that example: MAC-144 made the case for why to post, and the most common response was "okay, but what do I post?" That question was the raw material for everything here. I didn't invent a new topic. I followed the thread the audience handed me. None of it was invented. All of it was noticed.
Once you make that switch, the supply question inverts. You had a hard week. You made a call with incomplete information. You sat in a meeting where two functions used the same word to mean different things and it took forty minutes to notice. That's several posts, from one week, that you already lived. You are not short on material. You are short on the habit of noticing it.
Six things you're already doing. "Notice more" isn't an instruction anyone can act on, so here's the concrete catalog: six shapes, not six ideas. Ideas run out in a week; shapes don't. This isn't a private theory either — when the social media teams that do this professionally publish their standing lists of what actually earns attention on a professional feed, the categories converge on roughly the same handful.
- The Lesson. Something you learned recently, plus what you believed before you learned it. That before-and-after is the whole post. "I used to think the quarterly forecast was a prediction. Two years later, I think it's a negotiating position." Nobody can argue with your own experience.
- The Breakdown. How a thing actually works, explained the way you wish someone had explained it to you — the real version, with the part everybody gets wrong flagged in the middle. You're inside a Recency Window on at least one of these right now.
- The Question. A genuinely open problem, stated well. Posting a question is posting — we spent a whole episode on this in The Question Is the Credit (MAC-151): the person who reframes a problem gets credited with the insight, even when someone else supplies the answer.
- The Contrarian Take. Where your lived experience diverges from the standard advice. Say so, carefully, aimed at the practice, never at a person, backed by your own evidence.
- Behind the Scenes. The process, the failed first attempt, the messy middle nobody publishes — the most under-supplied shape on the internet, because everyone posts the finished thing. People trust process more than polish.
- The Curation. Something you read, watched, or heard, and why it changed your mind. Without that second half you're just a repost. The lowest-authority-claim shape, and the right on-ramp for anyone who's never posted before.
None require you to be right about the future, have a result to brag about, or be the most qualified person in the room. Four of the six don't even require you to be an authority on anything.
Mining the record you already keep. A few months back I made the case for the brag document (MAC-141) — the private running log of what you did, why it mattered, and what came of it. My guess is a meaningful number of you started one and haven't opened it since. Go open it. Every entry already answers what did I do, why did it matter, what happened — structurally, most of a post.
What stands between a brag entry and a public post is one pass, mostly subtraction. Names, client identities, and internal numbers come out or get converted to relative terms — "cut the cycle nearly in half" instead of the actual figure. Anything covered by a signed agreement stays put. If you'd hesitate to say it in a crowded elevator in your building, it doesn't go out. Then the orientation flips: the private entry proved you did something; the public one helps someone else do it.
Two failure modes are worth watching for. The first, covered in MAC-144: self-promotion versus value-sharing — "here's what I'd do differently" serves the reader, "and that's why I got promoted" serves you. Readers feel the difference in the first line, every time. The second is newer: "learn in public" has curdled, in places, into extraction wearing the costume of humility — performing confusion at volume so more experienced people do your thinking for you, for free. The sharper critiques of that turn draw a clean line: documenting your process is not the same as using an audience as an unpaid tutor. The test: post the answer you found, not the homework you want done.
Your action plan. Name the reader before you name the topic — pick one real person roughly two years behind you; everything else gets easier with a specific human on the other end. Book a fifteen-minute capture block, not a writing block, once a week, and list what you did, what surprised you, and what you now know that you didn't on Monday — just capture, don't polish yet. Pick the shape before you pick the topic: run the six (lesson, breakdown, question, contrarian take, behind the scenes, curation) and ask which one this week's raw material fits. Publish the one that feels too obvious — the entry you dismissed fastest, the one where you thought everyone already knows that. Three short paragraphs is a post. And put next week's on the calendar before you close the app — one post a week, not when inspiration strikes. Fifty-two ordinary posts will do more for you than one you agonized over in March.
Agreement is cheap. Everybody agrees that posting publicly is a good idea, the same way everybody agrees about the gym in January. What separates the people who build something from the people who intend to isn't conviction or talent. It's that one group solved the empty-box problem and the other is still waiting to feel qualified. You are not going to feel qualified — that feeling arrives, if it ever does, long after the window where you had something useful to say has quietly closed.
So don't write from the top of what you know. Write from the edge of it — for the one person about to hit the wall you just climbed over. The distance between agreeing with this and posting something is exactly one sentence long. Go write that sentence this week, and send it to managingacareer.com/contact. I read everything that comes through, and if you've written something that shares real value for the person two years behind you, I'll use this podcast and my reach to help amplify it.
Links & References
Learn In Public — Swyx
https://swyx.io/learn-in-public
Why I Hate What's Become Of 'Learning In Public' — Maggie Delano
https://maggiedelano.com/2022/07/30/learning-in-public.html
Document, Don't Create — Gary Vaynerchuk
https://medium.com/@garyvee/document-dont-create-creating-content-that-builds-your-personal-brand-c2957c8c813a
Does Social Media Cause Imposter Syndrome? — Psychology Today
https://www.psychologytoday.com/us/blog/why-bad-looks-good/202408/does-social-media-cause-imposter-syndrome
15 Inspiring LinkedIn Post Ideas and Examples — Sprout Social
https://sproutsocial.com/insights/linkedin-post-ideas/
You Need to Be Posting Publicly (MAC-144)
https://managingacareer.com/144
The Brag Document (MAC-141)
https://managingacareer.com/141
Using AI to Learn Leadership (MAC-128)
https://managingacareer.com/128
Which Career Body Are You (MAC-152)
https://managingacareer.com/152
The Question Is the Credit (MAC-151)
https://managingacareer.com/151
Faking It (MAC-083)
https://managingacareer.com/83
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.
