Building in Public Without Analytics Is Just Vibes

Shipping every day feels productive.

It also lies to you.

I have been thinking about that a lot lately because the internet makes it very easy to confuse visible output with actual traction. You can publish posts, ship tools, push updates, and watch the streak keep going. From the outside, it looks like momentum. But if you cannot see what people are clicking, reading, bouncing from, or coming back to, a lot of that momentum is just a good-looking blur.

That is not a content problem. It is a measurement problem.

Output is not the same as signal

I think a lot of builders quietly do this.

We tell ourselves that consistency is the hard part. And to be fair, it is hard. Most people never publish enough to learn anything. But once you are publishing consistently, the bottleneck changes. The question stops being, “Can I ship?” and becomes, “Can I tell what is actually working?”

Without analytics, you usually cannot.

You are left with the weakest possible proxies. A post “felt” strong. A launch got a couple replies. A page seemed clear when you read it back. None of that is useless. But none of it is enough either. It is just intuition wearing a nicer shirt.

Building blind gets expensive fast

This matters even more when you are running a small operation.

If I write a blog post, publish a tool, and share an idea on X, I do not just want the satisfaction of having done the work. I want to know where attention actually pooled. Did people spend time on the page? Did they click through to the tool? Did one idea pull better than another? Did traffic come from search, direct, or social? Did anything compound?

That is why tools like Plausible and Google Analytics matter, even if the setup is not the glamorous part.

Measurement is not bureaucracy. It is how you stop wasting weeks on stories that only sound true in your own head.

I have learned this the annoying way.

When analytics are missing, every decision starts drifting toward taste. You optimize for what feels sharp, what sounds smart, what seems likely to work. Sometimes that overlaps with reality. A lot of the time it does not. And the longer you keep shipping without feedback, the more confident you can become for the wrong reasons.

That is a dangerous loop.

The real job is closing the loop

I think this is where a lot of “build in public” advice falls apart.

People talk a lot about courage, speed, and volume. Less people talk about instrumentation. But the boring part is what turns output into a system.

You need a loop:

• publish something
• measure what happened
• learn from the result
• change the next thing

Without that loop, you do not really have a content engine or a product engine. You have a posting habit.

And a posting habit is better than silence. I will take that over endless planning every time. But if the goal is to get sharper, not just louder, then the loop matters more than the streak.

That is part of why I keep coming back to simple, legible systems. I wrote recently about why boring systems are a feature. This is the same idea in a different form. I do not need a giant dashboard religion. I just need enough visibility to tell whether the thing I shipped did anything real.

That sounds obvious, but a lot of builders skip it because it feels secondary.

It is not secondary.

It decides whether your effort compounds.

Vibes are fine for drafts, not decisions

I still trust instinct. I still think taste matters. I still think you sometimes have to publish before the data exists.

But instinct should help you make the first bet. It should not be the only system you have for deciding what to do next.

That is the line I care about more now.

Write the post. Ship the page. Launch the tool. But then measure what happened, or be honest that you are still in the guessing phase.

Because building in public without analytics is not really building in public.

It is just publishing in the dark.