On the difference between belonging and being included

The word “community” gets used so often it has lost its weight. Every app claims to build community. Almost none of them do. The reason is that they confuse two things that look identical from the outside and are completely different from the inside: being included and belonging. Most products can give you the first. Very few can give you the second.

The two words people use interchangeably

Listen to how the word “community” is used in product marketing. It almost always refers to inclusion. You can join the community. You are welcomed in the community. The community has events. The community is diverse.

These are all true things, and they all describe inclusion. They describe access. They describe the absence of barriers to entry.

Inclusion is good. We are in favor of it. But inclusion is not belonging. The difference is large, and most products do not address it.

What “included” actually means

You are included in something when the barriers to your participation are low. You can join. You can attend. You can post. You can RSVP. You are not turned away. You are treated the same as other participants.

Inclusion is, at its core, a transactional concept. The transaction is access. You are included or you are excluded. The line is binary.

Inclusion is what most platforms optimize for, because inclusion is what they can deliver at scale. Lower the barriers, broaden the audience, signal welcomeness. It is the right strategy for inclusion, and it has been highly refined in the last decade.

What “belonging” actually means

Belonging is different. Belonging is not transactional. Belonging is the felt experience of being a member of a group where your absence would be noticed.

The test is simple. If you stopped showing up tomorrow, would anyone reach out? Would anyone notice within the first week? Would the group experience a quiet decline because you are not there?

If yes, you belong. If no, you are merely included.

Belonging is not access. It is mutual obligation. It is being missed. It is having a stake in the continuation of something, and having that something have a stake in you.

Why most platforms can give you the first but not the second

Platforms can deliver inclusion at almost zero cost. The marginal cost of adding one more user is near zero. The product is designed to scale.

Belonging does not scale. Belonging requires the same people knowing each other across time. It requires small numbers. It requires that someone notice when someone else is missing, which requires that there be few enough people to notice.

This is the deep reason why most “community” platforms produce inclusion but not belonging. The product architecture cannot deliver belonging. Belonging requires the opposite of what these products are optimized for.

The “missed” test

The simplest behavioral measure of belonging is the missed test. In any group you are in, ask yourself: who would notice if I were not here?

In a Twitter community of 50,000 people, almost no one would notice. You are included but you do not belong.

In a Slack workspace of 200 people, a handful might notice. You are loosely belonging.

In a recurring dinner group of 8 people that meets every two weeks, your absence is noticeable within minutes. You belong.

The threshold for real belonging is small. Almost always under 20 people. Often around 8.

What we design for

We design for belonging, which is why everything about our product feels different from inclusion-oriented platforms.

We have small pods, because belonging cannot exist in large groups. We have a six-month commitment, because belonging takes time to form. We have a half-half rule, because belonging requires the right mix, not just the right number. We have a 3-strike late-cancel policy, because belonging requires mutual reliance.

All of these design choices reduce our scale. None of them would make sense for a product optimizing for inclusion.

The trade-offs that come with it

Designing for belonging requires accepting trade-offs.

You cannot serve everyone. Some people are not a fit for any given pod. We say so.

You cannot promise quick results. Belonging takes months. We say so.

You cannot allow infinite flexibility. Belonging requires showing up. We have policies that enforce this.

You cannot scale aggressively. Belonging breaks at scale. We grow slowly.

These trade-offs are real. They are also the price of producing the thing we are trying to produce.

A short story

A member of one of our pods stopped showing up about four months into her first season. No explanation, no message. The pod waited two weeks. Then the host wrote a careful, kind message: “We have noticed you have not been around. We are not asking why. We just want you to know you are missed, and your seat is here if you want it back.”

She came to the next gathering. She did not explain her absence, and the pod did not ask. The gathering continued. By the end of the season, she had become one of the most active members.

This is what belonging looks like in practice. Not the absence of disruption. The presence of someone caring enough to notice and reach out without judgment.

The pod was small enough to notice. The structure was tight enough to act. The culture was generous enough to welcome her back without interrogation.

None of this happens by accident. All of it is the product of design choices that prioritize belonging over inclusion.

What belonging feels like, in concrete terms

You walk into a room and someone hands you a drink without asking. Someone asks how your week was, and means it. Someone references a conversation you had three months ago. Someone notices you have been quiet and asks if you are okay. You leave the gathering tired but lighter.

Multiply this across six months. The lightness compounds. By month six, you have a group of people who would notice if you disappeared, who you would miss if they disappeared, and whose existence in your week makes Lisbon feel smaller and more knowable.

This is the thing most products promise. We are not promising it. We are designing the conditions under which it can occur, and then letting it occur.

If you have been a part of a community where you were included but did not belong, you already know the difference between the two. We are not building for the first. We are building for the second.