Asset-Based Community Development (ABCD)
Concept note — building community from existing capacities rather than assessed needs. From John McKnight and Peter Block.
What It Is
Asset-based community development begins by asking “what can you contribute?” rather than “what do you need?” It maps the skills, knowledge, passions, and relationships already present among residents and creates conditions for those capacities to connect. The community is built from what’s already there, not from what’s missing.
This inverts the conventional community development model:
Needs-based (conventional): Survey a community’s deficits → Design programs to address them → Hire professionals to deliver services → Measure outcomes against the deficit baseline.
Asset-based (ABCD): Inventory a community’s capacities → Create conditions for residents to connect and contribute → Support resident-led initiatives → Measure outcomes by the density and quality of connections formed.
The difference is not just methodological — it’s philosophical. The needs-based model treats the community as a client with problems. The asset-based model treats the community as a citizen body with capacities. The first produces dependence on professional services. The second produces self-sustaining mutual support.
The Heritage Library Connection
The vault’s heritage library concept — making visible the Irohs who are already there — is ABCD in practice. The retired woodworker, the experienced canner, the person quietly doing mutual aid, the teenager who’s good with computers, the parent who organized her child’s school fundraiser — these are assets. The community’s job is not to assess their needs but to make their capacities visible and connectable.
Core Practices
Asset mapping. A structured process for identifying what every person in a community knows how to do, cares about, and has time for. Not a survey — a conversation. The output is a map of human capacity, not a list of deficits.
The connector role. Asset mapping alone is insufficient. Someone needs to introduce people with complementary capacities. The person who wants to learn woodworking needs to meet the person who knows woodworking. McKnight calls this person the “connector” — someone whose gift is introducing people.
For Wellspring, the connector might be a rotating role, a spatial feature (the community kitchen where people cross paths and discover each other’s skills), or a visible artifact (a skill board, a tool library catalog, a heritage library directory). The infrastructure makes the connecting possible. The connecting makes the community real.
Contribution, not volunteerism. McKnight distinguishes between volunteering (donating time to an institution’s program) and contributing (offering your capacity within a relationship). Volunteering is institutionally directed — you serve the program’s goals. Contributing is relationally directed — you offer what you have because someone you know needs it. The heritage library runs on contribution, not volunteerism.
The Anti-Service Argument
McKnight’s most provocative claim: professionalized human services often displace community capacity rather than building it. When a professional is hired to “build community,” the implicit message is that the community can’t build itself. When a program manager organizes activities, residents learn to wait for activities to be organized. When a social worker assesses needs, residents learn to present needs rather than capacities. The community becomes a client.
The design implication for Wellspring: hire for building maintenance and financial administration — things that genuinely require professional skill. Don’t hire for “community programming.” The community programs itself through its own participation, facilitated by the shared infrastructure (tool library, community kitchen, common space) that the library economy provides.
This doesn’t mean no one coordinates. It means coordination comes from within — a resident who naturally connects people, a rotating community weaver role, a shared calendar maintained by residents — not from a staff position accountable to a board rather than to neighbors.
Relevance to the Project
ABCD provides the operational methodology for several things the vault currently describes philosophically:
- The heritage library concept becomes asset mapping — a specific, practicable process
- The “good villager is a destination” principle becomes capacity recognition — everyone has something to contribute, and the community’s job is to make that visible
- The anti-commodification principle becomes contribution vs. volunteerism — the difference between institutional programs and relational gifts
- The community self-maintenance model becomes resident-led, not staff-delivered — an organizational design choice with a methodology behind it