back to writing

Building in Public / Founder Resilience / Startups

The Hardest Part of Building in Public Is Continuing When It Feels Pointless

Building in public is not only about posting consistently. It is about learning how to keep going when the process feels disappointing and the signal is still unclear.

The hardest part of building in public is not deciding what to post every day. It is not learning how to write better hooks. It is not figuring out how to grow followers.

The hardest part is continuing when the process starts to feel disappointing.

When you have been showing up, but the market does not seem to care yet. When you ship product updates, but nobody reacts. When you find leads, but none of them turn into real customers.

I felt this recently when my X account was suddenly permanently frozen. I hadn't violated any rules. I was just posting and replying normally, but it seems malicious reports are just part of the tax you pay for being visible. Watching that "Permanent" label appear right when you are building momentum is devastating. You appeal, wait a week with zero feedback, appeal again, and just when you're about to give up hope, it's restored.

It's a small victory, but the process is draining. None of these things look dramatic from the outside, but when they stack up, they become heavy. You do not completely break down; you simply start to lose energy. You hesitate before posting. You question whether building in public is even worth it.

But I am starting to realize something: this is not an exception to building in public. This is part of it.

A Low Point Does Not Always Mean You Are Wrong

When things feel bad, the first instinct is to assume the direction is wrong. Maybe the product is wrong, or the positioning is wrong. Sometimes that may be true. But often, especially in the early stage, the signal is simply not clear enough yet.

A post getting no engagement does not always mean the idea is bad. An account getting frozen does not mean the work no longer matters. Early-stage building is painful because you have to keep moving before the evidence is obvious.

You need feedback, but feedback is sparse.

You need validation, but validation is slow.

You need proof, but proof takes repetition.

So a low point is not always failure. Sometimes it just means the system has not produced enough signal yet.

The Most Dangerous Part Is Letting External Noise Take Over

The most distracting voices are not always the people criticizing you. Sometimes they are the people who believe they are helping you. They may genuinely mean well, but they do not have to live with the outcome.

If you abandon your own rhythm because someone else pushed you into a different direction, you are still the one who has to carry the result. This is why it is important to separate feedback that helps you see reality from feedback that only pulls you away from your own operating system.

Turn the Low Point Into an Operating System

When you feel discouraged, you need something more concrete than motivation. You need a system.

1. Admit That It Hit You

Do not pretend it did not affect you. An account being frozen or a lead not converting affects your confidence. Admitting "This affected me" does not make you weak; it makes you aware. You are privately training your ability to keep going through uncertainty.

2. Do Not Make Big Decisions at Your Lowest Point

Low-energy moments produce bad strategic decisions. When you are discouraged, the desire to quit is often just fatigue, not insight. My rule: when emotionally low, only make small moves. Publish one post. Fix one small bug. Keep the system alive, and save the big pivots for when your mind is clear.

3. Replace Outcome Goals With Action Goals

You cannot fully control whether a user buys today. But you can control the action. Instead of asking, "Did I get a result today?" ask, "Did I keep the loop running today?" Results come from action density, not one perfect move.

4. Create a Minimum Viable Version of Consistency

On a weak day, the goal is not to perform at your best. It is to not break the chain. The minimum version might just be writing a 100-word reflection or fixing one small product issue. Building in public fails when the system stops completely, not when it moves slowly.

5. Write the Setback Into the Story

People connect with someone who is still moving despite friction. Sharing that your account was frozen and restored is not complaining. It's useful reflection. It reminds others that the "overnight success" they see is usually just the result of someone refusing to let a difficult season be the end of their story.

The Real Lesson

The people who make it are not necessarily the people who never felt discouraged. They are the people who kept building, kept adjusting, and kept learning on the days when nobody cared and nothing seemed to work.

That is the most honest lesson of building in public: it is not about publicly proving that you are successful. It is about publicly documenting how you keep going before success is obvious.

I write notes like this while building ZeroToUser and SpotAQ in public.

Follow along on XRead more notes