> For the complete documentation index, see [llms.txt](https://wiki.oikos-international.org/oikosmos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.oikos-international.org/oikosmos/best-practices/community-building.md).

# Community Building

Creating a connected, purpose-driven chapter

{% hint style="info" %}
Here's the uncomfortable question for a busy chapter: if you cancelled every event for two months, would anything still hold your members together? If the honest answer is no, then what you have is an event calendar with a membership list attached - and the moment the calendar gets thin, so does the chapter.
{% endhint %}

### Introduction

At the heart of a strong oikos chapter is not an event calendar. It's a community - and the job of that community is to move people along a line.

<div align="left"><img src="https://2965938342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McTWLVc9mrD4Wj9307R%2Fuploads%2FTqp8WxOCecGXz1TtByL7%2FMember%20progression?alt=media&amp;token=a63cdd6e-cf1c-495e-8870-206d0615268f" alt="Member progression" height="149" width="540"></div>

### 🧭 Here's What You'll Walk Away With

* Four stages - Attract, Connect, Engage, Sustain - to organise everything you do
* Concrete ways to build relationships between members, not just between members and the board
* Why traditions and rituals do more for retention than another workshop
* Health metrics that tell you whether people actually belong

### What Is “Community Building” Here?

Everything that makes someone feel this is a group they're part of rather than a service they consume: how easy it is to walk in, whether they know anyone's name, whether they're trusted with real work, and whether any of it survives the next handover.

### Why Does This Matter for oikos Specifically?

Because events are a terrible retention mechanism on their own. Attendance is cheap to give and cheap to withdraw; students have endless competing options. What keeps someone through a difficult exam period is not the programme - it's the three people who'd notice they were gone.

And because every other section of this Toolbox depends on this one. Recruitment fills a community; handover passes one on; leadership is shared within one; alumni are what a community becomes. Without it, each of those is just administration.

### How: Attract → Connect → Engage → Sustain

<div align="left"><img src="https://2965938342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McTWLVc9mrD4Wj9307R%2Fuploads%2FBvADwPEyEklk4MhWhMwZ%2FCommunity%20funnel?alt=media&amp;token=a6834d1e-ef10-461f-8caa-09f3aa3e47db" alt="Community funnel" height="261" width="500"></div>

#### 1. ATTRACT - Make It Easy to Walk In

People are drawn in by purpose and people, not organisational charts. Offer several different doors: welcoming onboarding, personal invitations, open events, projects, working groups, volunteering, informal gatherings, discussion circles.

{% hint style="info" icon="globe-pointer" %}
Overlaps heavily with Recruitment Strategies - attraction is where the two sections meet.
{% endhint %}

Would someone new feel comfortable walking into our community?

#### 2. CONNECT - Membership Is Not Belonging

Someone can be on every mailing list and still feel like a stranger. Belonging comes from shared experience and from horizontal relationships.

Build relationships between members, not only between members and leaders: peer mentoring, buddy systems, small groups, project teams, accountability partners.

The harder question is how often. Belonging is built by cadence, not by one big event:

<div align="left"><img src="https://2965938342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McTWLVc9mrD4Wj9307R%2Fuploads%2FQHckzfIHumlOxbKJ9qcO%2FThe%20community%20rhythm?alt=media&amp;token=f74d8269-6674-4387-b4bd-c68347459800" alt="The community rhythm" height="203" width="540"></div>

The annual row is where traditions come from. A welcome gathering, a chapter celebration, a handover ritual, a graduation farewell - repeated three years running, these become identity. They are also, conveniently, the cheapest things on the list.

#### 3. ENGAGE - Move People From Participation to Ownership

Give members real opportunities: lead small initiatives, facilitate meetings, manage projects, support partnerships, contribute to strategy, mentor newer members, experiment with new ideas.

Strong communities create many small opportunities to lead.

And recognise contributions - particularly the invisible work. The person who booked the room, chased the caterer and stayed to stack chairs rarely gets named in the recap post. They are also exactly the person you cannot afford to lose. People stay where they feel valued.

{% hint style="info" icon="globe-pointer" %}
For the mechanics of handing over real ownership, see the delegation ladder in Purpose-Led Leadership.
{% endhint %}

#### 4. SUSTAIN - Outlast the Handover

Connect the generations: current members, former members, alumni, faculty, partners. A community that only contains this year's cohort restarts every year.

Document the soft things too: traditions, onboarding practices, community rituals, lessons learned, engagement approaches that worked. These almost never make it into a handover document, and they're the hardest to rebuild.

Then run regular feedback loops. Four questions, asked honestly, once or twice a year:

* What makes you feel connected?
* What should we do more of?
* What should we stop doing?
* What would make this community more meaningful for you?

#### Measure Community Health, Not Attendance

<div align="left"><img src="https://2965938342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McTWLVc9mrD4Wj9307R%2Fuploads%2FIKSq07XlTlGC43c6Sw8S%2FCommunity%20health%20metrics?alt=media&amp;token=79a34f86-ed3f-4855-892a-437932520cb2" alt="Community health metrics" height="194" width="530"></div>

### The Final Test

Ask your board these six questions once a year:

* Are relationships forming naturally?
* Are members becoming contributors?
* Is leadership shared?
* Are new people welcomed?
* Does our community survive leadership changes?
* Would people remain connected even if there were fewer events?

If the answers are yes, you are building more than an organisation. You are building a community.

### Summary

Make the chapter easy to enter, then deliberately build belonging through shared experience and member-to-member relationships. Move people from participating to owning, recognise the invisible work, connect current members to alumni and faculty, document the traditions as carefully as the processes, and measure belonging rather than attendance.

### 🎯 Main Takeaway

> Events fill a calendar. Community is what makes people come back to it - and what's still there when the calendar is empty.

### 💡 Tips & Tricks - Try This Tomorrow

* Name one tradition you already have and write it down so next year's board repeats it. Two repetitions make a habit; three make an identity.
* Pair every new member with a buddy. Costs nothing, and directly addresses the most common reason people drift away.
* Thank someone publicly for invisible work at your next meeting - logistics, admin, the unglamorous things.
* Ask the four feedback questions in a five-minute anonymous form this month. You'll learn more than from any attendance sheet.
* Schedule one purely social gathering with no agenda and no speaker. Connection is the point; it doesn't need a programme.
* Count how many members took ownership of something this semester. If the number is only the board, that's your community's growth edge.
