The Quiet Build: Why I’ve Stopped Announcing Every Half-Baked Idea

Build in public has become the default setting for anyone with a side project and a LinkedIn login. For a while, I bought it. I posted the wireframes. I shared the tiny wins. I wrote earnest updates about what I had learned from a week of not very much. It felt productive. It also felt, increasingly, like a second job that happened to involve my actual job.

I am not against sharing work. I run a small independent site, and I like hearing how other people make things. But somewhere along the way, the habit tipped from useful openness into performance. The update became the product. The story of the build became more important than the build itself.

The performance of progress

There is a particular kind of post that does the rounds in UK freelance and indie-maker circles. It usually starts with a confession, includes a bullet list of lessons, and ends with a question designed to encourage comments. It is polished, vulnerable and almost entirely about the person posting it.

That is not a crime. Social media rewards that sort of thing. But it creates a strange incentive. If you know you are going to write about your week, you start shaping your week around the post. You choose the tidy lesson over the useful dead end. You pick the screenshot that looks like progress rather than the afternoon you spent untangling a boring technical problem.

For independents, the pressure is worse. We are already selling ourselves as competent, reliable and interesting. Build in public adds another layer: now we are also meant to be transparent, consistent and generous with our process. It is a lot to carry when you are just trying to get a small thing off the ground.

What the applause actually rewards

Build in public rewards visibility, not substance. The algorithm does not care whether your project works. It cares whether the story is engaging. A half-formed idea with a nice graphic will often travel further than a finished tool with no marketing budget.

That can be useful when you are launching. It is less useful when you are still deciding what the thing is. Early ideas are fragile. They need room to be bad, contradictory and boring. They need a few weeks where nobody asks how it is going.

The UK independent scene is full of people doing genuinely interesting work in spare rooms, kitchens and shared offices. Most of that work does not need a live commentary. It needs time, attention and a bit of nerve. The more we normalise the running update, the harder it becomes to admit that the most productive thing you did this week was think quietly and delete half your plan.

The quieter alternative

So I am trying something different: build in private, publish once.

That does not mean secrecy for the sake of it. It means treating the early stage as protected space. I keep notes. I talk to one or two people I trust. I test things with a small group when there is something to test. But I do not turn every decision into a public post.

The rule is simple: share when there is something someone can use. A finished project. A proper write-up. A clear explanation of what worked and what did not. Not the eleventh draft of my thinking, and not a daily diary disguised as thought leadership.

Publishing once is also a useful discipline. It forces you to finish. You cannot keep relaunching the same idea in public and calling it momentum. At some point you have to put the thing down, look at it, and decide whether it is good enough to show someone.

Where I still share

I am not suggesting everyone retreats into a shed and emerges three years later with a manifesto. Accountability helps. So does feedback, and so does the odd conversation with someone who has done it before.

I still have a private check-in with a friend who asks me what I actually shipped this week. I still write a short log for myself, mostly so I can remember why I made certain choices. And after a project is out, I am happy to talk about the messy bits. In fact, that is when the messy bits are most useful, because they are attached to a real outcome rather than a hopeful guess.

In 2026, the internet is loud enough. There is no shortage of people explaining what they are about to do. There is a shortage of finished things, clearly explained, with the rough edges left in.

A permission slip

If you have been posting every step because you thought that was what builders do, you can stop. You are allowed to disappear for six weeks and come back with something that works. You are allowed to keep the half-baked idea to yourself until it has a bit more substance.

Build in private. Publish once. Then, if you want, tell us how it went. That feels like a better use of everyone’s time.