Why We Kept the Small Hangout at the Centre of g3t

A large community looks impressive on a landing page. A newcomer walking into a crowded room may feel something different: Who do I speak to? Am I interrupting a group? Will anyone remember me next week? Our thinking about g3t has kept returning to the value of small gatherings. The goal is not to claim that five people form better friendships than fifty in every situation. It is to make the first real encounter comprehensible, manageable and worth repeating.

The problem we chose to examine

In a small gathering, people can learn names and notice conversational cues without constantly scanning the room. Shared activities provide a reason to meet, while a finite group gives everyone more chances to contribute. Yet the number alone is not a design solution. A group with poor facilitation, incompatible expectations or unclear logistics can feel uncomfortable at any size. We wanted to pay attention to the experience of arrival, the balance of conversation and what happens once the gathering ends.

The design question underneath

A central product question is what participants actually know before attending. Too little information may create anxiety; too much disclosure too early can expose private details. A good process should tell people what kind of activity to expect, where to go, how long it lasts and whom to contact if something changes. It should not require members to become organisers just because a social product has matched their profiles. These are design responsibilities, not proof that every proposed feature has already launched.

What becomes clearer in real life

We have learned to distinguish a pleasant one-off event from a relationship that can develop. The first meeting offers information: whether people enjoy each other, share interests or feel safe. It is not a referendum on friendship. Some people will connect immediately; others may need several ordinary encounters. A small group makes those encounters easier to imagine, but it does not guarantee them. A stronger product must also make subsequent contact respectful and voluntary.

What a good signal looks like

There is a temptation to optimise for the most photogenic activity: a dinner table full of smiles, a rooftop scene or a perfect picnic. But the less glamorous details matter more than the photograph. Was the venue easy to find? Could a shy participant join the conversation? Did anybody need to leave early? Would people be willing to make the same trip again? A small group is a practical design choice only if those everyday questions receive serious attention.

Where our knowledge stops

Small-group design has trade-offs. Cancellation by one person can change the atmosphere. People have different tolerances for silence, conversation and uncertainty. A group of five is still a set of strangers, with safety and privacy needs that require thoughtful handling. We cannot claim that small groups are universally safer or that anyone will make a friend. Our responsibility is to measure actual experiences rather than assume a group-size decision solves social connection.

The questions we need to keep testing

The real outcome we should pay attention to is not simply how many small hangouts can be put on a calendar. It is whether people show up, choose to participate again, and develop relationships on their own terms. The difference matters for the user and for a responsible company. A repeat invitation should never reveal somebody's whereabouts or social preferences without their choice. Trust is part of the mechanism, not a decorative afterthought.

Why the distinction matters

We keep coming back to small gatherings because they give the first encounter a human scale. What happens next depends on the people, the setting and the opportunities to meet again. We want to build for that reality rather than promise instant friendship. This is a draft of the team's rationale and needs explicit founder approval before it can be presented as official history.

Small groups still need deliberate operating rules

A small hangout can make it easier to notice who's speaking, but group size does not solve everything. Four or five participants may still differ sharply in interests, language comfort and energy. One person may dominate a dinner; another may not want to explain why a question felt invasive. A carefully chosen activity can give everyone an external subject, yet somebody still needs to make logistics clear. We believe the design should support a public meeting point, expectations about cost, a simple way to leave, and a respectful channel to raise concerns. None of those duties disappears merely because the table is small.

We also have to resist using attendance as the only measure of whether the format works. Someone can attend once and enjoy the evening without finding a person they want to see again. Others may need several neutral encounters before feeling comfortable. A small group should be understood as a design choice intended to lower some social barriers, not proof that friendship will result. Good feedback includes what did not work: a wrong activity, travel that was too long, a mismatch in pace, or a group that needed better facilitation. Those observations should change what we build next.