You Can't Rent a Community

There is a comfortable assumption behind most community building, which is that if you get the space right, the people will follow. Book the venue, fill the calendar, open the doors, and a community is supposed to form on its own. It sounds reasonable, and I spent the early part of my career believing some version of it, until I had watched it fail enough times to know better.

There is also a quieter assumption nested inside the first one, which is that we got the space right to begin with. Everyone is convinced that their location is the best, their design is the best and their offering is the best, and they rarely stop to ask the obvious question, which is best for whom. That verdict is almost always reached from one side of the table, which is ours. It reflects our taste, our logic and our own sense of what good looks like, none of which is the same as what actually works for the people we are hoping will show up and stay. We mistake our preferences for theirs, and then we are surprised when the community does not behave the way we designed it to.

I have spent close to twenty years building communities, starting with Nakhwah, the first volunteer network in the Arab world, which grew to 19,000 volunteers across 17 countries on almost no budget at all. There was Mix N' Mentor at Wamda, which we ran across the region, and the founding community at Hub71, where we built value-creation programmes for more than a hundred startups. More recently I have been managing the Community Hub at Yas Creative Hub for twofour54, Abu Dhabi's media and creative campus, where the lesson keeps proving itself inside a building designed for exactly this. Different cities, different sectors and the same lesson every time: the communities that lasted were rarely the ones with the best space or the biggest events. They were the ones where people had a reason to come back that had nothing to do with us.

The drift nobody plans for

What nobody plans for is the slow drift that sets in once the excitement of launch fades. Every community starts warm and gradually turns into a transaction, where members become users, participants become attendees and the regulars you counted on become names on a list. Nobody decides to let this happen. It happens because the things that are easy to count, like headcount and sign-ups and footfall, quietly take over from the things that actually matter but are much harder to see. You start optimizing for the numbers that go in the report, and the report has no column for whether anyone felt like they belonged.

So if a community is not the space and not the calendar, what is it. After two decades of building them, I have come to think of it as a small number of things that are unglamorous to work on and almost impossible to fake.

A reason specific enough to exclude people

A community needs a reason to exist that is specific enough to exclude people. Networking is not a reason, it is a venue. The communities that hold are the ones that can finish the sentence "this is a place for people who" in a way that makes some people lean in and others walk away. Nakhwah worked because it was not for everyone, it was for people who wanted to give their time to a cause, and that clarity did more to build it than any feature we ever shipped. A community that tries to be for everyone ends up as a room that anyone can pass through and no one needs to stay in.

The first week decides it

Most of the energy in community building goes into attracting people and almost none into what happens in the days right after they arrive, which is exactly backwards. Belonging is decided early, in whether a newcomer has a real interaction, makes a first small contribution and meets one person who learns their name, all before the initial motivation wears off. At Hub71 we obsessed over this, because a founder who had a useful introduction or an honest conversation in their first week behaved completely differently three months later than one who had been handed a tote bag and a login. Onboarding is not paperwork. It is the moment the community either becomes real to someone or quietly does not.

A ladder, not a door

People do not arrive ready to belong, they grow into it, and a healthy community gives them rungs to climb, from showing up, to speaking up, to helping someone else, to eventually hosting the thing they once attended. If there is no path from consuming to contributing, you are not running a community, you are running an audience, and audiences are rented by definition. Some of the most useful work I have done was designing those rungs on purpose, so that a quiet member always had an obvious next step that turned them, over time, into one of the people holding the place up.

Rhythm is the heartbeat

Communities live or die on cadence, on the sense that something is always about to happen and that missing it costs you something. When I built the monthly calendar at Hub71, the mentorship sessions and workshops and pitch events were not just programming, they were a heartbeat, a reason for the community to assemble on a predictable rhythm so that connection became a habit rather than an occasion. A community with no rhythm is just a directory, and nobody feels they belong to a directory.

The tissue runs between members, not through you

The mistake most organizers make is letting the connective tissue run through them instead of between the members. It is flattering to be the person everyone comes to, the hub that every spoke depends on, but a community routed through its organizer is one resignation away from collapse. The real work is making members need each other rather than you, surfacing the connection a member did not know to ask for, introducing the two people who should have met months ago and then getting out of the way. The day members start doing that for each other without you is the day you actually have a community.

Keeping it human at scale

The hardest part is keeping all of this human as the numbers grow. Care is easy when you know everyone by name, it starts to strain at a hundred people and it breaks somewhere in the thousands unless you have built something underneath it that protects the personal feeling at scale. That, to me, is the real engineering problem in community work, and it is strange how rarely anyone treats it as one. It is the difference between a place that feels smaller than it is, in the best way, and a place that feels like a crowd the moment it grows.

The wrong numbers

This is also why the health of a community is so badly measured. The numbers that make it into the deck are attendance and sign-ups and followers, none of which tell you whether anyone would notice if you disappeared. The signals that actually matter are quieter, like how many members came back without being chased, how much happened that you did not organize and how many introductions the community made on its own. Those are the leading indicators of belonging, and they are the first to fall when a community is drifting toward transaction, long before the headline numbers show it.

Belonging is the growth

None of this is the soft alternative to growth, which is the framing I spend the most time arguing against. Belonging is what produces growth in the first place, because people refer, invest, build and stay where they feel they belong, and the members who feel like owners are the ones who go out and bring the next hundred. The economic outcomes everyone is chasing tend to sit downstream of a trust that most organizations never take the time to build, and you cannot shortcut your way there with a better venue or a bigger launch.

So you can put your money into the space, the launch and the noise, or you can do the slower and less visible work of giving people a reason to belong, a way to climb, a rhythm to return to and each other to rely on. One of those keeps costing you to maintain. The other quietly starts paying you back.

You cannot rent a community. You have to build one, and you have to mean it.