The Second Shift Nobody Talks About: What Your 'Building in Public' Habit Is Actually Costing You
Photo: tired freelancer working late at night laptop coffee, via img.freepik.com
There's a particular kind of exhaustion that doesn't show up on any timesheet. It's the one that hits at 11 p.m. when you've finally finished the actual work — the design, the draft, the edit — and then remember you still owe the internet a thread about it.
Building in public has been sold to us as a cheat code. Share your process, grow your audience, land opportunities. And look, sometimes it works exactly like that. But somewhere between the first excited post and the two hundredth, a lot of us quietly took on an unpaid internship with a boss who never logs off: ourselves.
The Job You Never Interviewed For
Think about what documenting actually involves. There's the capturing — screenshots, voice memos, behind-the-scenes footage mid-task. There's the packaging — writing captions, editing clips, picking the thumbnail where you don't look completely dead. There's the distribution — posting across platforms, responding to comments, sliding into the DMs of people who engaged.
None of that is your craft. All of it is labor.
I've talked to enough creators to know the pattern: the person who spent six hours making something and four more making content about making it. The person who can't start a project without already imagining how they'll explain it later. The person whose sketchbook now has a mental asterisk on every page — is this postable?
That last one should stop you cold. When documentation starts shaping creation, you're not building in public anymore. You're performing construction.
Running the Real Numbers
Here's a framework I wish someone had handed me earlier. Before you commit another month to documenting everything, do the math on three columns.
Column one: hours. Track everything — capture, editing, posting, replying. Be honest. For most solo creators, this lands somewhere between five and fifteen hours a week. That's a part-time job's worth of time.
Column two: returns. Not vibes — returns. Actual clients sourced from your posts, actual sales, actual collaborations that came through the content. Not follower counts. Not likes from other creators who are also documenting their documenting.
Column three: cost to the work. This is the sneaky one. What did the documentation habit take from the thing itself? Did the project get smaller because a smaller project was easier to explain? Did you choose the photogenic task over the important one?
Now sit with the result. If column two is strong, great — you've found a channel that works. But if the hours are heavy, the returns are thin, and the work itself is suffering, you're not building an audience. You're subsidizing one.
The Middle Path Nobody Posts About
Here's what doesn't go viral: the idea that you can just... share less.
The all-or-nothing framing around building in public does real damage. You're either an open book or you've 'gone dark.' But there's a whole spectrum in between, and most sustainable creators live there. Monthly recaps instead of daily updates. One honest post when something's actually finished, instead of a running commentary on the mess.
A few moves worth trying:
- Batch the documentation. Spend one hour a week capturing, not constant fragmented attention. Your process doesn't need a live feed.
- Let the work be the content. A finished thing, shared plainly, often outperforms ten process posts. Let it.
- Write for the record, not the reach. If documentation helps you think, keep it — but maybe it belongs in a private doc instead of a public feed.
Permission, If You Need It
You are not obligated to narrate your growth for an audience that mostly scrolls past. The people who genuinely care about your work will still be there if you post twice a month instead of twice a day. And the opportunities building in public promises? They tend to come from the quality of the work anyway — the documentation just gets the credit afterward.
Do the work. Share it when sharing serves you. That's not going dark. That's just having a job description that ends somewhere.