You Cannot Launch an Empty Community and Call It a Community

I’ve been thinking a lot about community products lately.

And one thing keeps becoming clearer:

Community features are not the same thing as community.

You can build profiles. Followers. Comments. Direct messages. Notifications. Feeds. Groups. Reactions. Events.

And after all of that, you can still have an empty product.

Because the technology is not the community.

The reason people care about each other is.

A lot of community products seem to begin with a familiar checklist.

We need a feed. We need profiles. We need comments. We need messaging. We need notifications.

Those are all useful tools.

But they answer the question: How will people interact?

They don’t answer the more important one: Why would they want to interact in the first place?

That part has to exist before the mechanics matter.

A gardener doesn’t necessarily want another social network. But they might want to see what people nearby are growing.

Someone going to a festival probably doesn’t need another feed. But they might want to find someone attending the same event.

A traveler might not want to “join a community.” But they might want advice from somebody who just stayed in the neighborhood they’re visiting.

The connection starts with relevance.

The community comes after.

The strongest communities usually have an object at the center.

A place. An activity. A problem. A shared identity. A specific moment.

Something people already care about independently of the platform.

That changes everything.

Instead of asking users to manufacture content for the sake of keeping a feed alive, the product can start with something meaningful.

“This is my garden.”

“I’m going to this festival.”

“I’ve been to this restaurant.”

“I’m planning this trip.”

“I’m trying to solve this problem.”

“I made this.”

Now someone else has a reason to respond.

Not because the product told them to “engage.”

Because they recognized something.

I’m increasingly suspicious of the word engagement.

It reduces a lot of human behavior into a metric.

Clicks. Comments. Sessions. Notifications opened.

Those things matter if you’re running a product.

But they don’t necessarily tell you whether a community is healthy.

I’m much more interested in moments like:

“I know that username.”

“I met them at the last event.”

“They helped me before.”

“They’re growing the same thing.”

“We’re going to the same place.”

“I want to see what they post next.”

Those moments create continuity.

A person stops feeling like a random account.

The product starts feeling inhabited.

That’s different from engagement.

It’s recognition.

And recognition is what starts turning a collection of users into a place.

This is one of the hardest problems with building community products.

A new user arrives.

There are technically people there.

But nothing feels alive.

The feed is sparse. The profiles are incomplete. Nobody has commented lately. The conversation someone joins has one post from three weeks ago.

Everything functions.

Nothing feels inhabited.

It’s like walking into a party where the lights are on, the music is playing, and nobody is talking.

The obvious instinct is to get more people.

Sometimes that’s the answer.

But often the better question is: What should one person be able to do here even if nobody else shows up today?

• Can the person discover something?
• Save something?
• Plan something?
• Learn something?
• Record something?
• Explore somewhere?
• Create something they’ll want later?

If the product is useful alone, community can make it better.

If the product is useless until hundreds of people arrive, you have a much harder cold-start problem.

I think some of the most interesting community products start as tools.

A map. A directory. A planner. A journal. A collection. A recommendation engine. A marketplace.

Something that provides individual value first.

Then other people slowly become part of the experience.

You discover another person because they added the place you were looking at.

You start following them because their recommendations keep being useful.

You message them because you’re attending the same event.

You recognize their name the next time they appear.

The social graph emerges from the utility.

That feels much more natural to me than asking someone to build a social graph before the product has earned it.

This is also why I’ve become fascinated by the first 25 users.

Not the first 25,000.

The first 25.

Those people are doing more than testing software.

They’re establishing culture.

What do people post here? How polished does something need to be? Do people answer questions? Is it okay to be new? Do people share photos? Do they make jokes? Do they help strangers? Are people using their real names? Does anybody come back?

The answers to those questions become invisible instructions for everyone who arrives afterward.

That means early community building is less like growth marketing and more like hosting.

You’re setting the table. Introducing people. Starting conversations. Making sure nobody walks into an empty room. Recognizing contributions. Helping people understand why the place exists.

That work doesn’t scale particularly well.

That might be why it matters.

Another thing I’ve been thinking about is notifications.

Push. Email. Daily summaries. Someone followed you. Someone commented. Someone sent you a message. Someone joined something you’re part of.

These can bring people back.

But there’s a dangerous version of this where notifications become a substitute for having something worth returning to.

A notification can remind someone that a relationship exists.

It cannot create the relationship.

The best notification is probably not: “Come back to our app.”

It’s: “Something happened here that you actually care about.”

Someone replied. Someone you met posted something. Someone joined your trip. A place you follow changed. Your friend is attending the same event.

The notification works because the underlying event matters.

Not because the copy was optimized.

I used to think community building meant scale.

A busy feed. Thousands of members. Constant activity.

Now I think it starts with something much smaller.

Two people recognizing each other.

One person answering another person’s question.

Someone returning because they remember a conversation.

A user contributing something because they believe somebody else will actually see it.

A small group gradually developing shared context.

That’s much harder to manufacture than engagement.

But it also feels much more durable.

So when I’m thinking about community products now, I’m trying to stop asking: “How do we get people to post more?”

And start asking: What would make one person genuinely care that another person is here?

That question leads to very different products.

And probably much better communities.