Grow without losing the work

Growth is repeated discovery and return

For a Build in Public project, growth is not only a larger audience. It is an increasing number of relevant people who can discover the work, understand it, try it, and return when something changes.

That requires distribution, but distribution should grow from the work rather than consume it.

Build a content ladder

One week of real work can produce several layers without inventing several stories:

1. A private work log captures raw details.
2. A short public update shows one artifact and lesson.
3. A weekly note connects several decisions.
4. A durable guide explains the lesson after it has been tested.
5. The project page links the resulting knowledge back to the product.

You do not need to publish every layer every week. The ladder shows how one source of truth can serve different levels of context.

Choose one discovery channel

Pick the place where relevant people already spend attention. Learn its culture and publish there consistently enough to understand the response.

Then choose one owned destination: your website, README, documentation, or email archive. The discovery channel brings people in. The owned destination preserves context and gives them a reason to return.

Add another channel only when the first system works and the new audience is meaningfully different.

Create recurring formats

Recurring formats reduce the cost of deciding what to publish:

• a Friday build note;
• one decision explained after each release;
• a monthly retrospective;
• a public changelog;
• a short demo whenever a user-visible behavior changes.

The format is a container, not a quota. Skip it when there is no useful evidence.

Make the archive navigable

As the project grows, organize public material around reader questions:

• What is it?
• Why does it exist?
• How do I begin?
• What changed recently?
• Which decisions shaped it?
• Where can I ask or respond?

Tags, topics, collections, and internal links should help a new reader follow a path instead of facing a reverse-chronological wall.

Measure healthy growth

Track measures connected to the project:

• relevant visitors who reach the working artifact;
• people who return after a release;
• conversations that change a decision;
• successful setups, uses, contributions, or purchases;
• search queries that reveal unanswered questions;
• percentage of publishing time compared with building time.

Follower growth can be observed, but it should not be allowed to define the roadmap.

Know when to stop a channel

Leave a channel when it repeatedly creates performance pressure, attracts the wrong audience, or demands a format that damages the work. Preserve the durable archive and redirect your energy.

Consistency does not mean remaining loyal to an ineffective distribution method.

Growth checklist

• [ ] One discovery channel reaches relevant people.
• [ ] One owned destination preserves the full context.
• [ ] Recurring formats come from actual work.
• [ ] Internal links give every useful page a next step.
• [ ] Metrics connect attention to behavior.
• [ ] Building still receives more energy than publishing.

Growth should make the work easier to find and understand. It should not make the builder disappear behind the content system.