Spade — Mutual Aid
Dean Spade, Mutual Aid: Building Solidarity During This Crisis (and the Next) (2020).
The Argument
Mutual aid is not charity. It is not volunteerism. It is not community service. It is a political practice — a way of meeting people’s immediate material needs while simultaneously building the relational infrastructure that makes collective action possible and modeling the society you’re trying to create.
Spade writes from decades of organizing experience in queer and trans communities of color, where mutual aid has been a survival strategy long before the term entered mainstream vocabulary during COVID-19. His argument is that mutual aid must be built deliberately, maintained against co-optation, and designed to avoid replicating the hierarchies it opposes.
Where Kropotkin argues that mutual aid is a natural factor of evolution, Spade argues it is a craft that requires ongoing, conscious effort. The instinct may be natural. The infrastructure is not.
The Charity/Mutual Aid Distinction
Spade makes this distinction load-bearing:
Charity maintains the existing distribution of power. A donor gives to a recipient. The relationship is hierarchical: the donor decides who deserves help, under what conditions, in what quantity. The recipient is a passive receiver who must prove eligibility and perform gratitude. The underlying system that produced the need goes unexamined.
Mutual aid redistributes power. Participants share resources horizontally — everyone is both a potential giver and a potential receiver. No one decides who “deserves” help. No one means-tests. No one is in charge. The act of meeting immediate needs is simultaneously an act of building the relational fabric that makes collective resistance possible.
The structural difference: charity can be scaled through institutions (nonprofits, foundations, government programs) without changing power relationships. Mutual aid cannot be institutionalized without being destroyed — because the institutionalization reintroduces the hierarchy the practice is designed to eliminate.
This is the tension Wellspring navigates. The project uses institutional structures (CLT, LEHC, 501(c)(3) status, CDFI financing) while trying to maintain the mutual aid logic internally. Getting this right means designing institutions that serve horizontal relationships rather than replacing them.
Failure Modes
Spade is candid about what goes wrong in mutual aid organizing — and these failure modes map directly onto the Intentional Community Failure Modes the vault already catalogs:
Burnout. A small number of people do most of the work. They exhaust themselves. The project collapses or narrows to whatever those few people can sustain. The design implication: distribute the work structurally, not by relying on the most energetic volunteers.
Founder syndrome. The people who started the project accumulate informal authority. Their vision becomes the project’s vision. New participants feel like they’re joining someone else’s thing rather than co-creating. The design implication: rotate leadership roles, make decision-making processes explicit, build in succession planning from day one.
Professionalization. As a mutual aid project grows, it hires staff, writes grants, develops programs, creates a board — and becomes a nonprofit. The horizontal relationships are replaced by organizational hierarchy. The participants become clients. The radical practice becomes a service delivery mechanism. This is the Demutualization threat in organizational form.
Co-optation by philanthropy. Funders offer money with strings — reporting requirements, outcome metrics, restrictions on advocacy. The mutual aid project adjusts to meet funder expectations rather than community needs. Over time, the project serves the funder’s theory of change rather than its own. The design implication: diversify funding, maintain independent governance, be willing to refuse money that comes with incompatible conditions.
Replication of hierarchy. Even in explicitly horizontal organizations, power concentrates along existing social lines — race, class, gender, education, confidence, free time. The people with the most privilege tend to dominate even in spaces designed to be non-hierarchical. The design implication: active, ongoing attention to power dynamics, not just structural flatness.
Mutual Aid as Prefigurative Politics
Spade’s deepest argument: the way you organize help models the society you’re trying to build. The means embody the ends. If your mutual aid group has a board, an executive director, a grants department, and a program evaluation framework, you’ve rebuilt the nonprofit industrial complex — even if you call it mutual aid.
This connects directly to the Worn Path’s insistence that the community must be designed so that the process of building it is itself the kind of life the community aims to sustain. You can’t build a horizontal community through hierarchical means. You can’t build a gift economy through transactional relationships. The building is the thing.
The Organizing Insight
Spade argues that meeting material needs and building political community are not separate activities. They are the same activity. When you organize a food distribution, you’re not just feeding people — you’re creating the context in which people who share a material condition (need) come into relationship with each other. Those relationships become the infrastructure for collective action.
This is the village problem stated in organizing language: you can’t mobilize people who don’t know each other. And they won’t know each other without shared practical activity. The LEHC’s communal responsibilities — shared maintenance, cooperative governance, the library economy — are not just cost-saving mechanisms. They’re the organizing activities that produce the relationships the village runs on.
Practical Design Implications
Spade’s work suggests several specific design features for Wellspring:
- Avoid professionalized community management. Hire for building maintenance and financial administration, not for “community programming.” The community programs itself through its own participation.
- Design for distributed labor. Rotation of responsibilities, clear and limited commitments, multiple people capable of filling any role.
- Protect the internal culture from funder logic. Accept financing that respects the community’s self-governance; refuse financing that requires the community to become a service delivery mechanism.
- Build in power-awareness. Regular check-ins on who’s doing the work, who’s making the decisions, who’s being heard. Not as bureaucratic process but as relational practice.