Building Sustainable Guilds - Revision history

Nthmost: New page: Guild sustainability guidelines based on community communication analysis

2026-01-29T10:16:18Z

New page: Guild sustainability guidelines based on community communication analysis

@@ Line 4: / Line 4: @@
 == Core Principles ==
 === Build Guilds, Not Kingdoms ===
@@ Line 32: / Line 48: @@
 # Have that person train 2 others
 # Celebrate when trainees become trainers
 == Possible Guild Structure ==

Nthmost: reorg'd, added flavor

2025-12-26T06:39:52Z

reorg'd, added flavor

@@ Line 4: / Line 4: @@
 == Core Principles ==
 === Build Guilds, Not Kingdoms ===
@@ Line 48: / Line 32: @@
 # Have that person train 2 others
 # Celebrate when trainees become trainers
 == Possible Guild Structure ==

Nthmost: Reframed corporate language: metrics→signs, intervention→suggestions, phases→ideas; more organic anarchist vibe

2025-12-26T04:04:26Z

Reframed corporate language: metrics→signs, intervention→suggestions, phases→ideas; more organic anarchist vibe

← Older revision		Revision as of 21:04, 25 December 2025
Line 41:		Line 41:
	The output of a guild isn't just work - it's more people who can do and teach the work.		The output of a guild isn't just work - it's more people who can do and teach the work.

	'''~~Metric~~''': ~~For every~~ skill ~~you have~~, ~~3+ people should be able to teach it~~.		'''A good sign''': Multiple people can teach any given skill, not just one person.

	'''Process''':		'''Process''':
Line 127:		Line 127:
	* Celebrate accomplishments (completed projects, new certifications, successful events)		* Celebrate accomplishments (completed projects, new certifications, successful events)

	== ~~Health Metrics~~ ==		== Signs Things Are Working ==

	~~{\| class="wikitable"~~		You'll know a guild is healthy when you notice:
	~~! Metric !! How to Measure !! Healthy !! Warning~~
	\|-		* Multiple people answer questions, not just one person
	~~\| Channel diversity \|\| Top poster % of channel \|\| <10% \|\| >15%~~		* New folks are learning skills and teaching others
	\|-		* People thank each other openly
	~~\| Active trainers \|\| People who've taught in past 3 months \|\| 3+ \|\| <2~~		* When someone steps back, others step up naturally
	\|-		* The vibe feels welcoming, not territorial
	~~\| Certification rate \|\| New certs per quarter \|\| 5+ \|\| <2~~
	\|-		== Signs Something Might Be Off ==
	~~\| Active volunteers \|\| People stepping up to do things \|\| Stable/growing \|\| Declining (not seasonal)~~
	\|-		Watch for these patterns - they often develop gradually:
	~~\| Credit ratio \|\| Thanks given / "I did" statements \|\| >1 \|\| <0.5~~
	\|}

	~~== Warning Signs ==~~		* One person becomes the go-to for everything
			* All questions get directed at the same person
			* Helpers quietly drift away
			* "No one volunteers" becomes a refrain
			* Access to equipment or knowledge gets bottlenecked

	* Single person dominates channel (>15% of messages)		== If You Notice Things Are Off ==
	* All questions directed at one person
	* No new trainers certified in 3+ months
	* Fewer people volunteering to do things (outside of seasonal dips)
	* "No one volunteers" complaints
	* Equipment/access bottlenecked through one person

	~~== Intervention Triggers ==~~		These aren't rules, just things that have helped:

	~~If a guild shows 3+ warning signs~~:		* Have an honest conversation about what's happening
	~~# Facilitate a guild health discussion~~		* Ask: who else could learn to do this?
	~~# Identify bottlenecks~~		* Look for people willing to share the load
	~~# Create explicit succession plan~~		* Make sure knowledge is written down, not just in someone's head
	~~# Set term limits for current coordinators~~		* Appreciate the people who've been carrying things, and help them step back gracefully
	~~# Recruit~~ and ~~train alternates~~

	== Anti-Patterns to Avoid ==		== Anti-Patterns to Avoid ==
Line 198:		Line 194:
	# '''Monthly "unsung hero" highlight''' - Find invisible contributors		# '''Monthly "unsung hero" highlight''' - Find invisible contributors

	== ~~Implementation Checklist~~ ==		== Ideas to Get Started ==

	~~=== Phase 1: Immediate ===~~
	* Create #kudos channel
	* Document current trainers for each guild
	* Identify 3 potential co-facilitators per guild

	~~=== Phase 2: Short-term (This Month) ===~~
	* Create guild template wiki page
	* Establish trainer list format
	* First "train the trainer" sessions

	~~=== Phase 3~~: ~~Medium-term (Next Quarter) ===~~		If you're starting a new guild or trying to strengthen an existing one:
	* All guilds have 3+ trainers
	* Succession plans documented
	* Credit metrics being tracked
	* Monthly guild health reviews
	* Steward rotation system active

	~~=== Phase 4: Ongoing ===~~		* Set up a Discord channel and pin some basic info
	* ~~Quarterly guild audits~~		* Write down who can teach what
	* ~~Annual coordinator rotation~~		* Think about who else might want to learn
	* ~~Continuous trainer development~~		* Make thanking people a habit, not an afterthought
	* ~~Credit ratio monitoring~~		* When you notice yourself becoming a bottleneck, start training someone
	* ~~Bottleneck detection and intervention~~

	{{boxend}}		{{boxend}}

Nthmost: Removed model community builder patterns section (not relevant to guild structure)

2025-12-26T03:46:34Z

Removed model community builder patterns section (not relevant to guild structure)

@@ Line 197: / Line 197: @@
 # '''Meeting kudos time''' - 2 minutes per meeting for recognition
 # '''Monthly "unsung hero" highlight''' - Find invisible contributors
 == Implementation Checklist ==

Nthmost: Revised: guilds need dedicated Discord channels; removed thread/forum prescriptions; celebrate accomplishments

2025-12-26T03:43:19Z

Revised: guilds need dedicated Discord channels; removed thread/forum prescriptions; celebrate accomplishments

← Older revision		Revision as of 20:43, 25 December 2025
Line 121:		Line 121:
	# '''Stay consistent''' - Regular meetings build momentum over time, even if attendance starts small		# '''Stay consistent''' - Regular meetings build momentum over time, even if attendance starts small

	=== ~~Channel Hygiene~~ ===		=== Discord Presence ===

			* Each guild should have a dedicated channel on the Noisebridge Discord server
	* Pin guild documentation at top of channel		* Pin guild documentation at top of channel
	* Create threads for specific projects (don't flood main)		* Celebrate accomplishments (completed projects, new certifications, successful events)
	* Regular "state of the guild" posts (monthly)
	* Celebrate ~~graduations~~ (~~new trainers~~, new certifications)

	== Health Metrics ==		== Health Metrics ==

Nthmost: Revised: attendance not a warning sign; focus on volunteer engagement not meeting attendance; consistency builds momentum

2025-12-26T03:41:21Z

Revised: attendance not a warning sign; focus on volunteer engagement not meeting attendance; consistency builds momentum

← Older revision		Revision as of 20:41, 25 December 2025
Line 119:		Line 119:
	# '''Read out kudos''' - Dedicate 2 minutes to thanking contributors		# '''Read out kudos''' - Dedicate 2 minutes to thanking contributors
	# '''Document decisions''' - Post to wiki within 24 hours		# '''Document decisions''' - Post to wiki within 24 hours
	# '''~~Track attendance~~''' - ~~Low~~ attendance ~~is a warning sign~~		# '''Stay consistent''' - Regular meetings build momentum over time, even if attendance starts small

	=== Channel Hygiene ===		=== Channel Hygiene ===
Line 139:		Line 139:
	\| Certification rate \|\| New certs per quarter \|\| 5+ \|\| <2		\| Certification rate \|\| New certs per quarter \|\| 5+ \|\| <2
	\|-		\|-
	\| ~~Meeting attendance~~ \|\| ~~Average attendees~~ \|\| Stable/growing \|\| Declining		\| Active volunteers \|\| People stepping up to do things \|\| Stable/growing \|\| Declining (not seasonal)
	\|-		\|-
	\| Credit ratio \|\| Thanks given / "I did" statements \|\| >1 \|\| <0.5		\| Credit ratio \|\| Thanks given / "I did" statements \|\| >1 \|\| <0.5
Line 149:		Line 149:
	* All questions directed at one person		* All questions directed at one person
	* No new trainers certified in 3+ months		* No new trainers certified in 3+ months
	* ~~Meeting attendance declining~~		* Fewer people volunteering to do things (outside of seasonal dips)
	* "No one volunteers" complaints		* "No one volunteers" complaints
	* Equipment/access bottlenecked through one person		* Equipment/access bottlenecked through one person

Nthmost: Revised: no "leaders", suggestive not prescriptive, no "workers" - guilds as fractal pattern of NB

2025-12-25T18:46:00Z

Revised: no "leaders", suggestive not prescriptive, no "workers" - guilds as fractal pattern of NB

← Older revision		Revision as of 11:46, 25 December 2025
Line 1:		Line 1:
	{{headerbox\|Building Sustainable Guilds\|Guidelines for creating guilds that outlast their founders}}		{{headerbox\|Building Sustainable Guilds\|Guidelines for creating guilds that outlast their founders}}

	This page provides ~~recommendations~~ for building guilds that are self-sustaining, knowledge-sharing, and resilient to ~~leadership~~ transitions. Based on analysis of community communication patterns.		This page provides suggestions for building guilds that are self-sustaining, knowledge-sharing, and resilient to transitions. Guilds are a fractal pattern of Noisebridge itself - no one "leads" them, but people step up to coordinate. Based on analysis of community communication patterns.

	== Core Principles ==		== Core Principles ==
Line 39:		Line 39:
	=== Train the Trainers ===		=== Train the Trainers ===

	The output of a guild isn't work - it's ~~workers~~.		The output of a guild isn't just work - it's more people who can do and teach the work.

	'''Metric''': For every skill you have, 3+ people should be able to teach it.		'''Metric''': For every skill you have, 3+ people should be able to teach it.
Line 49:		Line 49:
	# Celebrate when trainees become trainers		# Celebrate when trainees become trainers

	== Guild ~~Leadership~~ Structure ==		== Possible Guild Structure ==

	~~Every~~ guild ~~should have~~:		One structure a guild might adopt (adapt as needed):

	{\| class="wikitable"		{\| class="wikitable"
	! Role !! Quantity !! Term !! Responsibility		! Role !! Quantity !! Term !! Responsibility
	\|-		\|-
	\| ~~Guild Lead~~ \|\| 1-2 \|\| 6 months max \|\| Coordination, representation		\| Coordinator(s) \|\| 1-2 \|\| 6 months max \|\| Coordination, representation
	\|-		\|-
	\| Certified Trainers \|\| 3+ \|\| Ongoing \|\| Teaching skills to others		\| Certified Trainers \|\| 3+ \|\| Ongoing \|\| Teaching skills to others
Line 62:		Line 62:
	\| Stewards \|\| 2+ \|\| Rotating \|\| Equipment, space maintenance		\| Stewards \|\| 2+ \|\| Rotating \|\| Equipment, space maintenance
	\|-		\|-
	\| Succession Candidate \|\| 1+ \|\| Ongoing \|\| ~~Shadow lead~~, ready to step up		\| Succession Candidate \|\| 1+ \|\| Ongoing \|\| Shadowing coordinator, ready to step up
	\|}		\|}

	'''~~Key rule~~''': ~~No one can be Guild Lead for more than~~ 2 ~~consecutive~~ terms.		'''Suggested limit''': Consider rotating coordinators every 2 terms to prevent bottlenecks.

	== Onboarding Pipeline ==		== Onboarding Pipeline ==

	<pre>		<pre>
	Newcomer → Trained Member → Certified Trainer → Steward → ~~Guild Lead~~		Newcomer → Trained Member → Certified Trainer → Steward → Coordinator
	↓ ↓ ↓ ↓		↓ ↓ ↓ ↓
	greeting certification training maintenance		greeting certification training maintenance
Line 78:		Line 78:
	Every stage should have documentation and multiple people who can facilitate.		Every stage should have documentation and multiple people who can facilitate.

	== Documentation ~~Requirements~~ ==		== Documentation Suggestions ==

	~~Every guild must~~ maintain:		Guilds tend to work better when they maintain:

	# '''Skills wiki page''': What you can learn here		# '''Skills wiki page''': What you can learn here
Line 159:		Line 159:
	# Identify bottlenecks		# Identify bottlenecks
	# Create explicit succession plan		# Create explicit succession plan
	# Set term limits for current ~~leads~~		# Set term limits for current coordinators
	# Recruit and train alternates		# Recruit and train alternates

Line 216:		Line 216:
	* Create #kudos channel		* Create #kudos channel
	* Document current trainers for each guild		* Document current trainers for each guild
	* Identify 3 potential co-~~leads~~ per guild		* Identify 3 potential co-facilitators per guild

	=== Phase 2: Short-term (This Month) ===		=== Phase 2: Short-term (This Month) ===
Line 232:		Line 232:
	=== Phase 4: Ongoing ===		=== Phase 4: Ongoing ===
	* Quarterly guild audits		* Quarterly guild audits
	* Annual ~~leadership~~ rotation		* Annual coordinator rotation
	* Continuous trainer development		* Continuous trainer development
	* Credit ratio monitoring		* Credit ratio monitoring

Nthmost: New page: Guild sustainability guidelines based on community communication analysis

2025-12-25T18:40:37Z

New page: Guild sustainability guidelines based on community communication analysis

New page

{{headerbox|Building Sustainable Guilds|Guidelines for creating guilds that outlast their founders}}

This page provides recommendations for building guilds that are self-sustaining, knowledge-sharing, and resilient to leadership transitions. Based on analysis of community communication patterns.

== Core Principles ==

=== Credit is Infrastructure ===

Credit-giving isn't just politeness - it's the mechanism by which communities replicate themselves.

'''Why it matters''':
* People who feel credited stay and contribute more
* Public credit raises the profile of contributors
* Credit creates incentives for others to contribute
* Lack of credit drives away helpers silently

'''Implementation''':
* Create a #kudos channel for public recognition
* Build thanks sections into wiki pages
* Read out contributor names at meetings
* Make "Thanks to @X who..." a required part of announcements

=== Build Guilds, Not Kingdoms ===

The goal is a self-sustaining community, not a personal fiefdom.

'''Kingdom pattern''' (anti-pattern):
* One person controls access
* All questions route through them
* Knowledge lives in their head
* When they leave, nothing remains

'''Guild pattern''' (target):
* Multiple trained members
* Distributed knowledge (wiki, docs)
* Rotating responsibilities
* Clear succession planning

=== Train the Trainers ===

The output of a guild isn't work - it's workers.

'''Metric''': For every skill you have, 3+ people should be able to teach it.

'''Process''':
# Document the skill (wiki)
# Train 1 person to do it
# Have that person train 2 others
# Celebrate when trainees become trainers

== Guild Leadership Structure ==

Every guild should have:

{| class="wikitable"
! Role !! Quantity !! Term !! Responsibility
|-
| Guild Lead || 1-2 || 6 months max || Coordination, representation
|-
| Certified Trainers || 3+ || Ongoing || Teaching skills to others
|-
| Stewards || 2+ || Rotating || Equipment, space maintenance
|-
| Succession Candidate || 1+ || Ongoing || Shadow lead, ready to step up
|}

'''Key rule''': No one can be Guild Lead for more than 2 consecutive terms.

== Onboarding Pipeline ==

<pre>
Newcomer → Trained Member → Certified Trainer → Steward → Guild Lead
↓ ↓ ↓ ↓
greeting certification training maintenance
room class others + coord
</pre>

Every stage should have documentation and multiple people who can facilitate.

== Documentation Requirements ==

Every guild must maintain:

# '''Skills wiki page''': What you can learn here
# '''Equipment list''': What's available, status, location
# '''Trainer list''': Who can teach what (public, updated)
# '''Certification process''': How to get access/skills
# '''Steward rotation''': Who's responsible this month
# '''Meeting notes''': Decisions, attendees, action items

== Communication Recommendations ==

=== Announcement Template ===

When announcing accomplishments, use this format:

<pre>
[What happened]

Thanks to @Person1 who [specific contribution]
and @Person2 who [specific contribution]

[Call to action if any]
</pre>

'''Example''':
<blockquote>
We received a $5k challenge grant!

Thanks to @Alice who wrote the application
and @Bob who provided the financial documentation.

To unlock it, we need to raise $10k by Oct 1 - see #fundraising.
</blockquote>

=== Meeting Practices ===

# '''Rotate facilitation''' - No one person should always moderate
# '''Read out kudos''' - Dedicate 2 minutes to thanking contributors
# '''Document decisions''' - Post to wiki within 24 hours
# '''Track attendance''' - Low attendance is a warning sign

=== Channel Hygiene ===

* Pin guild documentation at top of channel
* Create threads for specific projects (don't flood main)
* Regular "state of the guild" posts (monthly)
* Celebrate graduations (new trainers, new certifications)

== Health Metrics ==

{| class="wikitable"
! Metric !! How to Measure !! Healthy !! Warning
|-
| Channel diversity || Top poster % of channel || <10% || >15%
|-
| Active trainers || People who've taught in past 3 months || 3+ || <2
|-
| Certification rate || New certs per quarter || 5+ || <2
|-
| Meeting attendance || Average attendees || Stable/growing || Declining
|-
| Credit ratio || Thanks given / "I did" statements || >1 || <0.5
|}

== Warning Signs ==

* Single person dominates channel (>15% of messages)
* All questions directed at one person
* No new trainers certified in 3+ months
* Meeting attendance declining
* "No one volunteers" complaints
* Equipment/access bottlenecked through one person

== Intervention Triggers ==

If a guild shows 3+ warning signs:
# Facilitate a guild health discussion
# Identify bottlenecks
# Create explicit succession plan
# Set term limits for current leads
# Recruit and train alternates

== Anti-Patterns to Avoid ==

{| class="wikitable"
! Anti-Pattern !! Key Sign !! Fix
|-
| '''Bottleneck''' || All roads lead to one person || Train 3+ people for every function
|-
| '''Announcer Effect''' || "We" claims without names || Always attribute by name
|-
| '''Invisible Helper''' || Helpers disappear || Credit immediately and publicly
|-
| '''Process Weaponizer''' || Procedures used punitively || Clear guidelines, protect mediators
|-
| '''Vibe Tanker''' || Low attendance, avoidance || Solicit interpersonal feedback
|-
| '''Martyr''' || Does everything, burns out || Force delegation, limit terms
|-
| '''Territory Marker''' || Possessive language || Use "our", rotate stewardship
|}

== Mediator Protection ==

Based on observed burnout incidents:

# '''Mediator pairs''' - Never solo mediation
# '''Term limits for mediators''' - Max 3 conflicts, then break
# '''Mediator support group''' - Debrief after difficult cases
# '''Clear process abuse guidelines''' - What's NOT acceptable use of conflict resolution processes

== Credit Infrastructure ==

'''Systems to implement''':
# '''#kudos channel''' - Dedicated space for public thanks
# '''Thanks section in wiki pages''' - Contributors listed
# '''Meeting kudos time''' - 2 minutes per meeting for recognition
# '''Monthly "unsung hero" highlight''' - Find invisible contributors

== Model Community Builder Patterns ==

The most effective community builders share these traits:

# '''Credit others generously''' - Give credit more than you take it
# '''Welcome at the edges''' - Spend time in greeting rooms with newcomers
# '''Celebrate publicly''' - Post thanks in main channels, not private DMs
# '''Know their limits''' - Step back before burning out completely
# '''Articulate values''' - Teach by stating principles clearly
# '''Distributed presence''' - Not concentrated in one "territory" but present across community spaces
# '''Enthusiasm is contagious''' - "Massive kudos!" resonates more than "thanks"

== Implementation Checklist ==

=== Phase 1: Immediate ===
* Create #kudos channel
* Document current trainers for each guild
* Identify 3 potential co-leads per guild

=== Phase 2: Short-term (This Month) ===
* Create guild template wiki page
* Establish trainer list format
* First "train the trainer" sessions

=== Phase 3: Medium-term (Next Quarter) ===
* All guilds have 3+ trainers
* Succession plans documented
* Credit metrics being tracked
* Monthly guild health reviews
* Steward rotation system active

=== Phase 4: Ongoing ===
* Quarterly guild audits
* Annual leadership rotation
* Continuous trainer development
* Credit ratio monitoring
* Bottleneck detection and intervention

{{boxend}}

[[Category:Guilds]]
[[Category:Community Building]]
[[Category:Best Practices]]