X — work in progress
Working on [feature or project] this week. Current state: [honest status]. Hardest part so far: [specific problem]. What we are trying next: [approach]. [Screenshot of work in progress]
LinkedIn — decision we made
A decision we debated for [time] this month: [the decision]. Option A: [option and its benefit] Option B: [option and its benefit] We chose [option] because [reasoning in 2 to 3 sentences]. What we gave up: [honest tradeoff]. I will share in [time] whether it was the right call.
Bluesky — tools we use
How [team size] of us ship [product]: - Planning: [tool] - Code: [tool] - Design: [tool] - Support: [tool] The one we would not give up: [tool], because [reason].
Mastodon — a day on the team
A normal [weekday] at [Company]: [time] [activity] [time] [activity] [time] [activity] Less glamorous than it sounds, and that is fine. #BuildInPublic #[TopicTag]
Tips
- Show one real artifact per post: a sketch, a screenshot, a whiteboard, or a snippet. Images of real work beat stock photos.
- Include one thing that went wrong. Honesty about setbacks is what makes behind the scenes content credible.
- Check screenshots for private data such as emails, customer names, or internal URLs before posting.
- Promise a follow-up and deliver it. 'Here is how that decision turned out' posts often outperform the original.
Frequently asked questions
What should I not share in behind the scenes posts?
Customer data, unannounced deals, security details, colleagues who have not agreed to appear, and anything under NDA. When unsure, blur it or leave it out.
Can a team review behind the scenes posts before they go out?
Yes. Drafts can wait in an approval inbox in SocialHandoff, so a teammate checks screenshots and wording for private details before the post is scheduled.