Building Sustainable Guilds

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 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 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. Process: Document the skill (wiki) Train 1 person to do it Have that person train 2 others Celebrate when trainees become trainers Possible Guild Structure One structure a guild might adopt (adapt as needed): Role Quantity Term Responsibility Coordinator(s) 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 Shadowing coordinator, ready to step up Suggested limit: Consider rotating coordinators every 2 terms to prevent bottlenecks. Onboarding Pipeline Newcomer → Trained Member → Certified Trainer → Steward → Coordinator ↓ ↓ ↓ ↓ greeting certification training maintenance room class others + coord Every stage should have documentation and multiple people who can facilitate. Documentation Suggestions Guilds tend to work better when they 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: [What happened] Thanks to @Person1 who [specific contribution] and @Person2 who [specific contribution] [Call to action if any] Example: 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. 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 Stay consistent - Regular meetings build momentum over time, even if attendance starts small Discord Presence Each guild should have a dedicated channel on the Noisebridge Discord server Pin guild documentation at top of channel Celebrate accomplishments (completed projects, new certifications, successful events) Health Metrics 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 Active volunteers People stepping up to do things Stable/growing Declining (not seasonal) 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 Fewer people volunteering to do things (outside of seasonal dips) "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 coordinators Recruit and train alternates Anti-Patterns to Avoid 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 Implementation Checklist 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) 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 coordinator rotation Continuous trainer development Credit ratio monitoring Bottleneck detection and intervention