Building in public, one prompt at a time
Building in public runs on a simple deal: post the small stuff, often, and people follow along. The deal breaks the moment "post the small stuff" turns into "open a design tool and spend fifteen minutes on a screenshot" — that's when daily updates quietly turn into weekly ones, and then into whenever you remember.
Here's a workflow that keeps the deal intact.
Pick two or three formats and reuse them
Consistency reads as intentional, not repetitive. A tweet card for one-line thoughts, an iOS reminder for "shipping X today," and a quote card for the occasional bigger realization covers most build-in-public updates without reinventing the format every time.
Try: "reminder: ship the onboarding rewrite before Friday" or "tweet: spent all day on a bug that was one missing await."
Write the update, not the design brief
The point of describing instead of designing is that you spend your words on the actual update, not on font choices. If the first draft is close but not quite right, tweak the line in place instead of starting over.
Schedule the week, not the day
If you know Monday's the ship-log post and Thursday's the metrics post, queue both now instead of remembering to open the app twice this week. Connect your accounts once and let the schedule carry the habit on the days your memory doesn't.
The actual goal
Nobody follows a build-in-public account for the production values. They follow it for the consistency. Anything that makes daily posting easier to sustain is doing more for the habit than a nicer template ever will.