Navigating Common Challenges
Trust Building
Show up consistently. Start with listening. Be transparent about intentions. Deliver on small promises. Bridge across difference — the hardest trust to build is often the most valuable. Red flags: Rushing to organize before relationships exist. Assuming digital connection equals trust.
Burnout & Sustainability
Co-build from day one. Rotate roles. Set boundaries. Celebrate small wins. Rest is not failure — if things stop when you rest, the infrastructure wasn't sustainable. Red flags: "I'll just do it myself." Checking group chats constantly. Guilt about time off.
Scale & Complexity
Deepen before you widen. Use the pod model (5-15 people with bridges between groups). Layer your channels. Delegate whole domains, not just tasks. Accept messiness — the "river, not the gardener" means letting go.
Digital Literacy & Access
Always maintain an analog channel. Choose lowest-barrier tools. Offer gentle onboarding. Design for phones. Translate if multilingual. Red flags: Assuming "everyone is on WhatsApp." English-only defaults.
Language & Cultural Barriers
Learn the landscape. Find bridge-builders who move between communities. Translate key infrastructure. Respect different organizing traditions. Show up at their events before inviting them to yours.
Conflict & Disagreement
Normalize disagreement. Create structured spaces for hard conversations. Focus on shared interests. Don't take sides as a builder. Know when to step back and refer to mediation.
Maintaining Momentum
Rhythm over events. Rituals matter. Regularly invite new people. Evolve the offering. Celebrate milestones.
-
Methodology
A Relational Tech Practice
-
Methodology
Embedded Design: A Guide for Builders
-
Methodology
Measuring What Matters: Agency, Belonging, Trust
-
Methodology
Network & Community Connections
-
Methodology
Playbooks for Common Builder Needs
Original source: https://github.com/The-Relational-Technology-Project/rt-mcp-server
See something to fix or add? Suggest an edit on GitHub — the commons lives in git too, and its history is the changelog.
methodologyrtp