Lift Where You Stand
Personal principle; connects to Self-Determination Theory (competence), Sacred Pathways, and Being a Villager (eudaimonia/neganthropy)
The Principle
Contribute to community using what you already are. Not what someone assessed you as, not what a role description demands, not what the community “needs” on paper — what you’re actually good at, what you actually enjoy, what you’d do anyway if someone just made space for it.
The phrase resists every clinical framing we’ve tried to put on the competence question — “remedial,” “recovery,” “development,” “training.” All of those start from deficit: you’re missing something, and we need to fix that. Lift where you stand starts from abundance: you’re already somewhere, you already have something, and the community is better when you bring it.
The D&D Example
Running a D&D group at church. Nobody assigned this. No committee reviewed a skills inventory and determined that the congregation had an unmet need for tabletop roleplaying. What happened was simpler: someone was good at running games, enjoyed doing it, and the community had enough open space for it to happen.
The result: a weekly gathering that built genuine connection between people who might never have spoken otherwise. Introverts who wouldn’t attend a potluck showed up every week. Teenagers and adults interacted as equals around a shared table. Stories were told, trust was built, laughter happened. All three SDT needs met simultaneously — competence (I’m good at this and people value it), relatedness (we’re bonded by shared experience), autonomy (I chose this and it’s mine).
No one would have designed this into a community programming plan. It emerged because the context allowed it. That’s the point.
Why the Language Matters
The way a community talks about contribution signals whether it sees residents as capable adults or projects to be developed:
Deficit framing: “We need to help residents build skills so they can contribute.” This undermines autonomy while trying to build competence — you’re telling someone they need to be fixed before they can participate. Even well-intentioned onboarding programs can carry this energy.
Surplus framing: “Everyone here has something. We just need to make space for it.” This assumes capability and creates the conditions for it to surface. The community’s job isn’t to train people — it’s to lower friction and broaden the definition of “contribution” until everyone can find their thing.
The @occuplaytional post nails this distinction in the context of children: “I can’t make them. But I can connect with them. I can interest them. I can help build the underlying skills so their capability grows.” Replace “children” with “residents” and the principle holds. You don’t pull the stem to make it taller. You tend the soil.
Design Implications for Wellspring
The community should have more entry points than it thinks it needs. If the only visible ways to contribute are showing up to workdays and sitting on committees, you’ll get a narrow band of participants and everyone else will feel like a spectator — or worse, a freeloader.
Contribution should be broadly defined and visibly celebrated: the person who runs a game night is contributing. The person who always notices when someone is struggling and checks in is contributing. The person who maintains a little free library or teaches a neighbor’s kid to code or plays music on the porch is contributing. Ranganathan’s Five Laws as Design Principles — “every person has their book” — is this same idea from the systems side.
The practical question isn’t “how do we get people to contribute” — that’s the school system’s question, the one that produces obligation and compliance. The question is “what’s preventing people from contributing what they already have?” Usually the answer is some combination of: they don’t feel safe enough (relatedness), they don’t see a way in (competence), or no one asked and the structure doesn’t allow it (autonomy). Remove those barriers and contribution tends to happen on its own.