Minimal Viable Structure

A counter-intuitive insight from community builders: more structure often produces more community, not less.

The popular intuition is the opposite. We imagine community as warm, spontaneous, free-flowing. Structure feels formal, bureaucratic, the opposite of relational. So community builders often try to keep things light: no rules, no roles, no schedules, no expectations.

The result is usually disappointment. A gathering with no structure attracts the people who'd be friends already and excludes everyone else. The unspoken norms become the actual norms; newcomers can't read them. The work concentrates in a few hands.

The opposite move: just enough structure to make participation easy and clear, and no more.

This framework owes most to writing by Mia Quagliarello and others at the grouphug Substack, alongside long traditions in organizational design and group facilitation.

What "just enough" looks like

A minimal viable structure has a few specific elements:

A clear purpose. Why are we gathering? What is this for? "Get to know neighbors" is fine. So is "share grief" or "plan the block cleanup" or "have fun playing weird games." Vague purposes attract vague participation.

A predictable rhythm. When does it happen? Where? How often? The strongest community gatherings recur on a fixed schedule. The third Thursday. The first Sunday. Every other Saturday. Predictability lets people plan; it also makes the gathering easier to remember.

Clear roles. Who is hosting? Who is making sure new people feel welcome? Who's bringing what? Even informal gatherings benefit from someone explicitly playing host. The host doesn't have to be charismatic; they have to be present and attentive.

Light rituals. A consistent opening (a check-in question, a moment of silence, a song). A consistent closing (a round of gratitude, a goodbye ritual). The bookends help people enter and exit the gathering with intention.

A clear way in. New people should know how to join. Is there a sign-up? A "first-timers welcome" message? A specific person who introduces them? The threshold matters more than the content for new participants.

That's it. Five elements, each minimal. Add only what you need.

What "too much structure" looks like

Structure becomes counter-productive when:

• It serves the structure rather than the community. Rules become more important than the people they were meant to serve.
• It exists to manage anxiety. Hosts who feel uncertain sometimes over-structure to feel in control. The structure may not serve the participants.
• It excludes new energy. Long-standing structures can become barriers to newcomers who'd contribute differently.
• It substitutes for relationship. Process becomes a way of avoiding the actual messy work of being with each other.

What "too little structure" looks like

The more common failure in community building. Symptoms:

• People aren't sure if the gathering is happening. Last-minute confusion about whether to come.
• One person is doing everything. They're burning out. Nobody else knows how to help.
• New people don't know how to participate. They come once and don't return.
• Conflict has no path to resolution. Tensions accumulate until they break out.
• The gathering depends on one personality. When that person is gone, the gathering ends.

If you're seeing these symptoms, more structure is the medicine.

The principle: structure for what's actually hard

Structure should solve specific problems, not exist for its own sake.

• *Hard: getting people to come.* Solution: predictable rhythm and clear invitations.
• *Hard: new people feeling welcome.* Solution: a greeter role and a ritual for introductions.
• *Hard: one person carrying everything.* Solution: distributed roles and rotation.
• *Hard: conflict.* Solution: community agreements (see [Community Agreements](../recipes/04-gathering-design/community-agreements.md)) and a process for addressing tension.
• *Hard: knowing when to stop a thing that's run its course.* Solution: explicit end-of-season check-ins.

Each new structural element should solve a hard problem you actually have. If it doesn't, leave it out.

In practice

When you're starting a new gathering or practice:

1. Pick the purpose. One sentence.
2. Pick the rhythm. Frequency and time.
3. Pick the host. Even if it's you, name it.
4. Pick the simplest opening ritual you can. A name round, a check-in question, a song.
5. Run it three times before evaluating. Patterns become visible in repetition.
6. Add structure when a problem emerges. Don't add it preemptively.

The result is a gathering that's easy to start, easy to join, and easy to sustain. Not because it has no structure, but because it has just enough.

Where to read more

• *More Structure, Not More Community* and related essays at grouphug.substack.com
• Priya Parker, *The Art of Gathering*
• *The Tyranny of Structurelessness* by Jo Freeman (a foundational 1970s essay on why no-structure organizations develop hidden hierarchies)
• Adjacent recipes: [Art of Hosting](../recipes/04-gathering-design/art-of-hosting.md), [Community Agreements](../recipes/04-gathering-design/community-agreements.md), [Block Stewards](../recipes/01-knowing-your-neighbors/block-stewards.md)

Details

• file path: frameworks/minimal-viable-structure.md