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 what you heard, and then announce the program you had designed anyway. You call it community input. What it really is: a performance of listening designed to build buy-in for decisions that were already made. The distinction matters because communities can tell the difference, and being consulted decoratively costs you more trust than never asking would have. This lesson separates performative engagement from authentic co-creation, and gives you three working frameworks for the real thing along with the honest conversation about power that has to accompany them.

The Spectrum from Extraction to Genuine Partnership

Understanding co-creation requires understanding what it is not. Arnstein's Ladder of Citizen Participation, developed in 1969 and still uncomfortably relevant, maps the spectrum from control exercised over a community to control exercised by it. At the bottom sits non-participation, which takes two forms: manipulation, where you tell people what you decided and frame it as their input, and therapy, where you ask the community to change themselves rather than changing your programs. In the middle sits tokenism, which covers informing, where communication runs one direction only, consultation, where people give feedback and you decide, and placation, where the community has influence but you retain final power. At the top sits citizen power: partnership, where you decide together, delegation, where the community makes some decisions independently, and control, where they lead and you support.

Most nonprofits operate in the tokenism zone. They ask for input and retain all decision-making authority, and there is nothing inherently wrong with that; it is often an honest reflection of who is accountable for the money and the legal obligations. The problem is the naming. Consultation described as consultation is respectable. Consultation described as co-creation is a promise you are not keeping, and the community will notice the moment their input fails to change anything. True co-creation means sharing decision-making authority, not gathering input more thoroughly.

When Co-Creation Makes Sense

You do not want to co-create everything. It is slower, more complex and requires more governance than deciding internally, so reserve it for the decisions where the extra weight buys you something. Four conditions justify it. The first is when community expertise is essential: designing a program for people facing homelessness should involve people with lived experience of homelessness, because their knowledge is expert knowledge and no amount of professional training substitutes for it. The second is when implementation depends on community buy-in, since a program designed without input and announced at the end is a program people do not show up to. The third is when the decision affects the community directly, as with how your group handles conflict, how members are treated, or what gets funded. The fourth is when you genuinely do not know the answer: you have a budget, you do not know how to allocate it, and asking community members to decide and then respecting the decision harnesses collective wisdom you do not otherwise have access to.

Equally, some decisions should not be co-created. Which accounting software to use, what font goes on the website, staff hiring where community members would be placing friends into positions of power, and strategic personnel decisions all belong inside the organization. Trying to co-create them wastes the community's time and dilutes the practice where it matters.

Before proposing co-creation at all, ask yourself one question: if the community decided something different from what you think is right, would you implement it? If the answer is no, do not propose co-creation. What you would actually be running is manipulation, and it will be recognised as such.

Three Co-Creation Framework Models

Framework 1: The Design Committee

A standing committee of five to eight community members, representing the key stakeholder groups, meets monthly and makes decisions about program design, resource allocation and community direction. Staff attend as informational support rather than as decision-makers, which is the structural detail that distinguishes this from an advisory group. The committee decides; staff implements.

This works best for stable organizations with a clear scope, where the committee knows precisely what it is deciding about and the decisions affect a bounded community. "What should our literacy program teach?" is a committee question. "What should our entire organization do?" is not. The challenges are practical: members may not have time to prepare, decisions can become slow and political, and you need skilled facilitation to keep discussions productive rather than circular. In implementation, provide reading materials a week before each meeting, compensate members for their time, use a professional facilitator rather than a staff member, and create a charter that states the committee's decision authority explicitly so that nobody has to infer it.

Framework 2: The Co-Design Cycle

Rather than a standing body, each new program or major change gets its own dedicated design cycle. Staff bring an initial concept and ask what is missing. A community co-design working group, recruited specifically for this project, meets three or four times over two months to refine the program. The group then presents the refined design back to the broader community for feedback, and implementation follows. Authority is shared: the community group shapes the design and staff implement it.

This suits major new initiatives, and its main advantage is recruitment. A defined timeline and a clear scope attract people who would never commit to an open-ended committee, and because the group goes deep on one problem, the expertise they bring to bear is concentrated rather than diffuse. The difficulty is the flip side of the same feature: recruiting for a time-limited commitment takes more effort than filling ongoing seats, and you need to run multiple cycles to sustain a co-creation culture rather than a single well-received experiment. In practice, recruit through signup forms rather than informal asks, be explicit about the commitment, provide food and childcare, share an initial concept clear enough to react to rather than starting from a blank page, and pay a stipend for participation.

Framework 3: Consensus-Based Governance

Here the entire organization, or a large subset of it, makes decisions together by consensus. There are no votes. Decisions must be acceptable to everyone, and where someone holds a serious objection the group works to address it until agreement emerges. Authority is fully shared.

Consensus works for small organizations, under roughly 50 active members, with a strong culture of trust, and it works particularly well where the community effectively is the organization, as in member-owned cooperatives and many community groups. It is the right instrument for decisions that genuinely affect everyone. Its costs are real: consensus is slow, one obstinate person can block everything, and the process demands high emotional intelligence and strong facilitation. It does not scale. If you adopt it, establish it from the start, because retrofitting consensus onto an existing hierarchy requires a culture shift most organizations cannot execute. Use trained facilitators, create a clear process for standing aside, meaning "I disagree but I accept the group's decision", document decisions explicitly, and keep consensus for values and direction rather than operational decisions.

Cost tracks the structure. Committees and design cycles carry recurring compensation, per meeting in the first case and per cycle in the second, and the appropriate amounts depend on your local context and the demands you are making. Consensus-based governance can run at very low direct cost, since the expense is time and facilitation rather than stipends, though that low figure is misleading if the meetings pull people away from paid work.

The Honest Conversation About Power and Privilege

Co-creation does not happen in a vacuum. Your organization probably has money, legitimacy and institutional power. Community members may have deep lived expertise and far fewer institutional resources. Acknowledging that imbalance is the first step, and there are four asymmetries worth naming out loud rather than managing quietly.

• Information asymmetry. Staff know the budget, the legal constraints and the history of past decisions. Community members usually do not. Share that information proactively rather than releasing it when someone asks the right question.
• Time and resource asymmetry. Staff are paid to attend meetings. Community members are not. Compensate participation, and treat that as a condition of the process rather than a nice gesture.
• Representation. Who is actually at the table? Co-creation with five educated members drawn from your existing network is not co-creation with your community. Recruit deliberately among people who are not already connected to you, and pay people to bring in their peers.
• Veto power. Who can overturn a decision? If the executive director can override the community group, this is not co-creation. Be explicit about what is genuinely co-decided and what is advisory.

The most dangerous co-creation processes are the ones that pretend power imbalances do not exist, because the imbalance operates anyway and the pretence removes the vocabulary to name it. The healthiest processes state the position openly: we have budget authority, you have expertise authority, and here is exactly how we are sharing decision-making power in this process.

How to Actually Implement Co-Creation

Phase 1, design the process, two to three weeks before launch. Define the decision clearly, so that everyone can state what is being co-created in one sentence. Determine the framework: committee, design cycle or consensus. Identify who needs to be at the table and design the recruitment that will get them there. Set compensation and logistics. Then draft a charter or agreement setting out how decisions will be made, which is the document you will be grateful for when the process comes under strain.

Phase 2, recruitment. Use your existing community networks but do not stop there, because stopping there is how processes quietly reproduce your current circle. Be explicit about the commitment and the compensation. Have one-to-one conversations, and ask people you trust to bring others. Over-recruit by 20 to 30 percent, since people will drop out and a group that starts at full strength ends undersized.

Phase 3, onboarding. Share the background information: budget, constraints, history. Explain the decision-making process explicitly rather than assuming it is obvious. Clarify what co-creation means for this specific process, which is where you convert an abstract commitment into a concrete one.

Phase 4, execution. Meet regularly, monthly for committees and three or four times for design cycles. Create psychological safety, where disagreement is welcome and shouting is not. Document decisions and share notes after every meeting. Acknowledge explicitly when the group has influenced an outcome: because you asked, we are redesigning this. That acknowledgement is what proves the process is real.

Phase 5, learning and iteration. After the process ends, ask the community group what worked, what did not, and what they would change. Use their answers to design the next cycle, and show them how their input shaped decisions. Celebrate the wins publicly, because a visible successful cycle is the best recruitment tool for the next one.

When Co-Creation Fails, and How to Fix It

Elite capture. The same handful of educated, well-connected people show up to everything, and co-creation ends up reproducing the hierarchies it was meant to interrupt. The fix is structural rather than rhetorical: pay people to recruit their peers directly, invite people to bring a friend and pay both, and recruit across multiple networks rather than the one that is easiest to reach.

Slow paralysis. The group meets endlessly and nothing gets decided, and attendance decays as people conclude their time is being spent rather than used. Set decision deadlines, invest in skilled facilitation, and use voting or weighted decision-making where consensus is not converging. Not every decision requires consensus, and treating every decision as though it does is what produces the paralysis.

Implementation gap. The group decides something and staff do not implement it, which is the failure that destroys trust fastest and most permanently. Prevent it before launch by confirming that leadership is genuinely committed to being bound by the community's decisions. If you are not ready for that, do not run co-creation. A consultation honestly labelled does far less damage than a partnership that turns out to be conditional.

What to Do Next

Choose one decision your organization will genuinely co-create in the next six months. Pick something meaningful but not existential: not whether to dissolve the organization, but what to fund, or how to handle conflict. Choose the framework that fits your context, your size and your capacity for facilitation. Then design the recruitment and process plan, including compensation, before you invite anyone, so that the first conversation you have with a community member already contains an honest answer about what they are being asked to decide.

Anti-Patterns

Calling consultation co-creation. Gathering input and retaining every decision is a legitimate practice with an accurate name. Using the language of partnership for it sets an expectation you will break at the first disagreement, and the community will read the broken expectation as a statement about how much their contribution was ever worth.

Proposing co-creation on a decision you have already made. If you would not implement an outcome you disagree with, the process is manipulation wearing the vocabulary of partnership. The test question exists precisely to be asked before the invitations go out, not afterwards.

Recruiting only from your existing network. The people already connected to you are the easiest to invite and the least likely to tell you something you do not already believe. Without deliberate outreach and paid peer recruitment, co-creation becomes a conversation between your organization and its most comfortable supporters.

Asking unpaid people to do expert work. Staff are compensated for the hours they spend in these meetings and community members frequently are not, which quietly restricts participation to people who can afford to donate their expertise. That filter selects for resources, not for insight.

Leaving veto power undiscussed. If the executive director can overturn the group's decision, the group needs to know that before it starts deliberating. Silence on the question is not neutrality; it reserves the power while allowing everyone to assume it has been shared.

Running one cycle and declaring a culture. A single successful co-design cycle is an event. Co-creation becomes a culture only when it repeats, when the next group can see what happened to the last group's decisions, and when the learning from each cycle visibly shapes the next.

Practice Prompts

• Take your three most recent community engagement activities and place each one honestly on Arnstein's ladder. Note which of them you described publicly as co-creation.
• Write down one decision coming up in the next six months and answer the test question in writing: if the community decided differently from you, would you implement it? Keep the written answer.
• List everyone who attended your last community input session and mark how many were already connected to your organization before the invitation.
• Draft a one-page charter for a hypothetical design committee, stating what it decides, what it advises on, and who if anyone can override it.
• Cost out a co-design cycle for a real upcoming program, including compensation, food, childcare and facilitation, and identify where the money would come from.
• Interview two community members who have participated in one of your processes about whether they believed their input changed anything, and record their answers without arguing.

Reflection

Think about the last time you asked your community for input and then made a decision. Can you point to a specific element of the final design that exists because someone outside your organization asked for it, and could that person recognise their contribution if they saw the program today? If the honest answer is no, that is not necessarily a failure of intent; it is usually a failure of structure, because nothing in the process required the input to travel any further than the room it was spoken in. The uncomfortable follow-up is what you told the community the process was. The gap between what you called it and what it structurally was is where trust is spent, and it is spent whether or not anyone says so out loud.

Glossary

• Co-creation. A process in which decision-making authority is genuinely shared with community members, as distinct from a process in which their input is gathered and then weighed internally.
• Arnstein's Ladder of Citizen Participation. A 1969 model mapping engagement from non-participation through tokenism to citizen power, used here to name what a given process actually is.
• Tokenism. The middle band of the ladder, covering informing, consultation and placation, where the community has voice but the organization retains final authority.
• Design committee. A standing group of community members with defined decision authority over program design and resource allocation, supported but not directed by staff.
• Co-design cycle. A time-limited working group convened for one program or change, which refines an initial concept and presents it back to the wider community.
• Consensus governance. Decision-making without votes, where proposals must be acceptable to everyone and objections are worked through until agreement emerges.
• Standing aside. A formal position within consensus meaning "I disagree but I accept the group's decision", which prevents a single objection from halting everything.
• Elite capture. The failure mode in which participation is dominated by the most connected and resourced community members, reproducing existing hierarchies inside a process meant to disrupt them.
• Implementation gap. The distance between what a community group decided and what the organization actually did, the failure most destructive to trust.

Related Lessons

• Listening Sessions Done Right: Gathering Feedback Without Performative Engagement
• The Advisory Board Playbook: Building Community Leadership Pipelines
• Community Representation in Nonprofit Leadership: Practical Pathways
• Participatory Evaluation: Involving Your Community in Measuring Impact
• Power-Sharing in Partnerships: Equitable Collaboration
• Why Community Is Your Nonprofit's Most Undervalued Asset

Closing

Co-creation is not a values statement, it is a governance choice with costs attached: slower decisions, more facilitation, real compensation and a genuine transfer of authority over something that matters. The organizations that do it well are not the ones with the strongest commitment to community voice; they are the ones that picked a decision small enough to share honestly, chose a framework their capacity could carry, named the power imbalances at the start, and then implemented what the group decided even when it was not what they would have chosen. The organizations that do it badly usually skipped only one of those steps, and almost always the last one. Start with a single decision, label the process accurately, and let the community see what happened to their input.

Key Takeaways

• Co-creation means shared authority, not thorough consultation. Arnstein's ladder distinguishes non-participation from tokenism and from genuine citizen power, and most nonprofits sit in the tokenism band.
• Accurate labelling protects trust. Consultation honestly named is respectable; consultation named as partnership is a promise that will visibly break.
• Reserve co-creation for the right decisions. Community expertise, dependence on buy-in, direct effect on the community, and genuine uncertainty justify it; software choices and staff hiring do not.
• Apply the test question first. If you would not implement a decision you disagree with, do not run the process.
• Three frameworks cover most contexts. A standing committee of five to eight members, a time-limited co-design cycle meeting three or four times over two months, or consensus governance for organizations under roughly 50 active members.
• Name the asymmetries explicitly. Information, time and resources, representation, and veto power all shape the outcome whether or not they are discussed.
• Compensate participation and over-recruit. Paying community members is a condition of equitable participation, and recruiting 20 to 30 percent above target absorbs the inevitable drop-out.
• The failures are predictable. Elite capture, slow paralysis and the implementation gap each have structural fixes, and the last one has to be prevented before launch rather than repaired afterwards.

Frequently Asked Questions

What if the community decides something I know is wrong? Then you should not have proposed co-creation. If you are genuinely open to implementation, honour the decision. If you think it is a mistake, that is valuable data for the next iteration rather than grounds for overruling this one. Very few decisions are irreversible, and most can be adjusted after three months once you have seen how they land. Trust the process you designed.

How do I prevent domination by one or two loud people? Good facilitation, mostly. Use talking pieces in consensus circles, where the person holding the object speaks and everyone else listens. In committees, use round-robin so that everyone contributes. Have private one-to-one conversations with people whose voices are not being heard, to understand what would help them participate. And collect written input alongside verbal, since the people who dominate a room rarely dominate a document.

Can you co-create with a very large community of 500 or more people? Not easily, and not directly. What you need is representation rather than everyone: a delegated design committee of elected or recruited representatives, or design cycles run with rotating groups. Multiple smaller groups give you diversity of perspective without the chaos of a decision-making body too large to deliberate.

Should community members be compensated for co-creation? Yes. They are providing labour and expertise, and not paying for it privileges the people who can afford to volunteer, who are usually the people with the most resources already. Pay stipends for participation. It also has a practical benefit: compensation filters for serious commitment in a way that goodwill alone does not.