Co-Creation Frameworks: Building Programs WITH Your Community

Many nonprofits practice what looks like co-creation but is actually extraction. You host a "listening session," ask for feedback, go back to your planning meeting, ignore most of it, and then announce the program you designed anyway. You call it "community input." What it really is: a performance of listening designed to build buy-in for decisions you've already made. This lecture distinguishes performative engagement from authentic co-creation and provides frameworks for the real thing.

The Spectrum from Extraction to Genuine Partnership

Understanding co-creation requires understanding what it isn't. Arnstein's Ladder of Citizen Participation (developed in 1969, still relevant) maps the spectrum:

Non-participation: Manipulation (we tell you what we decided and frame it as your input). Therapy (we ask you to change yourself, not change our programs).

Tokenism: Informing (we tell you what we're doing, one direction). Consultation (you give feedback, we decide). Placation (you have influence, but we have final power).

Citizen Power: Partnership (we decide together). Delegation (you make some decisions independently). Control (you lead, we support).

Most nonprofits operate in the tokenism zone. They ask for input but retain all decision-making authority. This isn't bad — it's honest about power dynamics. But call it what it is, don't call it co-creation.

True co-creation means sharing decision-making authority, not just gathering input.

When Co-Creation Makes Sense

You don't want to co-create everything. It's slower, more complex, and requires more governance. Save co-creation for decisions where:

• Community expertise is essential: Designing a program for people facing homelessness should involve people with lived experience of homelessness. Their knowledge is expert knowledge.
• Implementation depends on community buy-in: If you design without input and announce the program, people won't show up. Getting input builds ownership.
• The decision affects the community directly: How your group makes decisions about conflict, how community members are treated, what gets funded — these affect people directly and justify their participation in deciding.
• You genuinely don't know the answer: You have a budget. You don't know how to allocate it. Genuinely asking community members to decide, then respecting the decision, harnesses collective wisdom.

You don't need to co-create: which accounting software to use, what font to use on the website, staff hiring (community shouldn't hire their friends into positions of power), strategic personnel decisions.

Three Co-Creation Framework Models

Framework 1: The Design Committee

How it works: Form a standing committee of 5-8 community members representing key stakeholder groups. They meet monthly. They make decisions about program design, resource allocation, and community direction. Staff members attend as informational support, not as decision-makers.

Decision authority: The committee decides. Staff implements.

When it works: For stable organizations with clear scope. The committee knows what they're deciding about. Decisions affect a bounded community (e.g., "What should our literacy program teach?" not "What should our entire organization do?").

Challenges: Committee members may not have time to prepare. Decisions can become slow and political. You need skilled facilitation to keep discussions productive.

Implementation tips: Provide reading materials 1 week before meetings. Compensate members for time ($25-50 per meeting). Have a professional facilitator, not a staff member. Create a charter outlining decision authority explicitly.

Framework 2: The Co-Design Cycle

How it works: For each new program or major change, run a dedicated design cycle: 1) Staff brings an initial concept and asks "what's missing?" 2) Community co-design working group (recruited for this specific project) meets 3-4 times over 2 months to refine the program. 3) The community group presents the refined design back to the broader community for feedback. 4) Implementation follows.

Decision authority: Shared. The community group shapes the design; staff implements.

When it works: For major new initiatives. The defined timeline and clear scope attract participants who don't want to commit to ongoing committee work. The co-design group gets deep into the work and brings real expertise to bear.

Challenges: Recruiting people for a time-limited commitment is harder than ongoing committees. You need multiple cycles to maintain the co-creation culture.

Implementation tips: Use signup forms to recruit, not informal asks. Be explicit about time commitment (3 meetings, 2 hours each). Provide food and childcare. Share an initial concept that's clear enough to respond to (don't start completely blank). Pay a stipend ($100-300 total per participant).

Framework 3: Consensus-Based Governance

How it works: The entire organization (or a large subset) makes decisions together using consensus. No votes. Decisions must be acceptable to everyone. If someone has a serious objection, the group works to address it until agreement emerges.

Decision authority: Fully shared.

When it works: For small organizations (under 50 active members) with a strong culture of trust. For organizations where the community IS the organization (member-owned cooperatives, some community groups). For decisions where truly everyone is affected.

Challenges: Consensus is slow. One obstinate person can block everything. Decision-making requires high emotional intelligence and strong facilitation. Doesn't scale well.

Implementation tips: Establish consensus from the start (this can't be adopted later without real culture shift). Use trained facilitators. Have a clear process for "standing aside" (I disagree but I accept the group's decision). Document decisions explicitly. Don't use consensus for operational decisions (use it for values and direction).

The Honest Conversation: Power and Privilege

Co-creation doesn't happen in a vacuum. Your organization likely has money, legitimacy, and institutional power. Community members may have lived expertise but less institutional resources. Acknowledging this imbalance is the first step.

Power dynamics to name explicitly:

• Information asymmetry: Staff know the budget, the legal constraints, the history of past decisions. Community members may not. Share this information proactively.
• Time and resource asymmetry: Staff are paid to participate in meetings. Community members aren't. Compensate participation.
• Representation: Who sits at the table? Co-creation with five white educated members from your network isn't co-creation with your community. Actively recruit people who aren't already connected to you. Pay people to recruit their peers.
• Veto power: Who can veto decisions? If the executive director can override the community group, it's not co-creation. Be clear about what's truly co-decided vs. what's advisory.

The most dangerous co-creation processes are the ones that pretend power imbalances don't exist. The healthiest ones name them openly: "We have budget authority. You have expertise authority. Here's how we're sharing decision-making power in this process."

How to Actually Implement Co-Creation

Phase 1: Design the Process (2-3 weeks before launch)

1. Define the decision clearly. What exactly are you co-creating?
2. Determine the framework (committee, design cycle, or consensus).
3. Identify who needs to be at the table and design recruitment.
4. Set compensation and logistics.
5. Draft a charter or agreement outlining how decisions will be made.

Phase 2: Recruitment

1. Use existing community networks, but don't stop there. Recruit people who aren't already engaged.
2. Be explicit about the commitment and compensation.
3. Have one-on-one conversations. Ask people you trust to bring others.
4. Over-recruit by 20-30% (people drop out).

Phase 3: Onboarding

1. Share background information (budget, constraints, history).
2. Explain the decision-making process explicitly.
3. Clarify what "co-creation" means for this specific process.

Phase 4: Execution

1. Meet regularly (monthly committees, 3-4 times for design cycles).
2. Create psychological safety. Disagreement is welcome. Shouting is not.
3. Document decisions. Share notes after every meeting.
4. Acknowledge when the group influences outcomes. "Because you asked, we're redesigning X."

Phase 5: Learning and Iteration

1. After the process ends, ask the community group: "What worked? What didn't? What would you change?"
2. Use their feedback to design the next co-creation cycle.
3. Share how their input influenced decisions. Celebrate wins.

When Co-Creation Fails (and How to Fix It)

Failure pattern 1: Elite capture — The same five educated people show up. Co-creation reproduces existing hierarchies.

Fix: Pay people to recruit their peers directly. Say "bring a friend" and pay both. Recruit from multiple networks, not one.

Failure pattern 2: Slow paralysis — The group meets endlessly and nothing gets decided.

Fix: Set decision deadlines. Use skilled facilitation. Use voting or weighted decision-making if consensus isn't working. Not every decision requires consensus.

Failure pattern 3: Implementation gap — The group decides something and staff doesn't implement it.

Fix: Before launching co-creation, ensure leadership is genuinely committed to implementing the community's decisions. If you're not ready to be bound by community decisions, don't do co-creation. You'll destroy trust.

What to Do Next

Choose one decision your organization will co-create in the next 6 months. Pick something meaningful but not existential (not "should we dissolve the organization?" but "what should we fund?" or "how should we handle conflict?"). Choose a framework that fits your context. Design a recruitment and process plan. Move to Lecture 2.3.5: Listening Sessions Done Right to learn how to gather input ethically, even when you're not co-creating full decisions.