You host a "listening session." Twenty people show up. They share stories, ideas, critiques. You thank them, say "we'll integrate this feedback," go back to your team, and design the program you planned anyway. You announce it two months later. The people who came to the listening session feel unheard. You call it "community-centered." It's not. It's performative engagement—a show designed to build buy-in for decisions you've already made. This guide distinguishes performance from authentic co-creation and provides frameworks for the real thing.
The Honest Diagnosis: Most Nonprofits Aren't Actually Co-Creating
Sharing information (we tell you our plan) is not co-creation. Gathering feedback (you tell us your thoughts) is not co-creation. Even incorporating feedback (we use some of what you said) is not co-creation. Co-creation is sharing decision-making authority. It means the community helps decide what happens, not just advises. It means you might implement a decision you personally disagree with because the community decided it. If you're not willing to be bound by the community's decision, don't call it co-creation. Call it consultation. Consultation is legitimate. But it's not the same thing.
Most nonprofits practice consultation, not co-creation. They ask for feedback but retain all final decision-making power. This is honest and often appropriate. What's inappropriate is pretending it's something it's not. The communities you serve can tell the difference. Pretending to co-create erodes trust more than being transparent about who decides.
When Co-Creation Makes Sense
Co-creation is slower and more complex than staff-led decision-making. Don't co-create everything. Save it for decisions where the community's perspective is essential to good outcomes.
Co-create when: The community has expertise you lack (lived experience, cultural knowledge, deep understanding of the problem). Implementation depends on buy-in from people who need to participate. The decision affects the community directly and they're stakeholders in the outcome. You genuinely don't know what's right and want the community's wisdom.
Don't co-create: HR decisions. Which software to use. Personnel policies. Financial audit processes. Decisions where community participation would create conflicts of interest (staff hiring, for example). Day-to-day operations.
The test: If the community decided something different from what you think is right, would you implement it? If the answer is no, don't co-create. You'd be manipulating, not partnering.
Three Co-Creation Frameworks That Actually Work
Framework 1: The Community Decision Committee. A standing group of 6-8 community members meets monthly to make decisions about program direction, resource allocation, or policy. They're not advisory; they decide. Staff implements. This works for organizations with a clear, bounded scope. Challenges: requires compensation, skilled facilitation, and genuine staff commitment to implement decisions. Cost: $1,500-2,500/year.
Framework 2: The Design Sprint. For a specific new program, recruit a working group for 2-3 months. They meet 3-4 times to design it. The process is concrete and time-limited, which attracts people who don't want ongoing committee work. The group gets deep into the details and brings real expertise. You then implement what they designed. Challenges: need multiple sprints to maintain culture; recruitment is harder without ongoing presence. Cost: $500-1,500 per sprint.
Framework 3: Consensus-Based Governance. The whole organization decides together. No votes. Decisions must be acceptable to everyone (or at least not have serious objections). This works only for small organizations (under 50 active members) with strong trust and culture. It's slow but creates deep ownership and relationships. Challenges: paralysis risk, one person can block, doesn't scale. Cost: variable, can be low.
Name the Power Imbalances Openly
Your organization has institutional power, budget authority, legitimacy. Community members have lived expertise and local knowledge. These aren't equal, and pretending they are is dishonest. Instead, name them explicitly: "You have expertise we need. We have budget and institutional capacity. Here's how we're sharing power in this decision."
Share information proactively. Community members should know the budget, the constraints, the history. They should know what's possible and what's not before they start designing. Don't hide information. Compensate participation—staff are paid to be there; community members shouldn't do unpaid labor. Recruit actively—the people already connected to you aren't your whole community. Pay people to recruit their networks. And be clear about veto power. Who can override the community's decision? If leadership can, say that. Don't pretend power exists where it doesn't.
How to Actually Start Co-Creating
Pick one decision your organization will co-create in the next 6 months. Something meaningful but not existential. "What should we fund?" not "Should we dissolve?" Choose a framework that fits your capacity. Design it clearly: who decides, how they'll decide, what authority they have. Recruit broadly and pay for participation. Onboard people thoroughly—share budget, constraints, history. Then actually implement their decision, even if you disagree. If you can't commit to that, don't co-create.
After it ends, ask the group what worked and what didn't. Use their feedback to design the next cycle. Tell them how their input changed what you did. Celebrate wins. Co-creation builds culture through repeated, authentic partnership, not one-off events.
When Co-Creation Fails
Elite capture: The same five educated people show up. Co-creation reproduces existing power structures. Fix: Pay people to bring their friends. Recruit from many networks. Slow paralysis: Endless meetings, no decisions. Fix: Set deadlines, use skilled facilitation, allow voting if consensus stalls. Implementation gap: The group decides something and staff doesn't do it. Fix: Make sure leadership is genuinely committed before you start. If you can't be bound by the community's decision, don't pretend to co-create.