The word gets used a lot. Co-design. Co-creation. Participatory process. It appears in grant applications and strategic plans, on consultant websites and in board presentations. Everyone, it seems, is co-designing now.

Which is precisely why it's worth pausing to ask what the term actually means—and whether the way we're using it matches the promise it implies.

The spectrum of participation

Not all involvement is created equal. There's a meaningful difference between consultation and collaboration, between informing and sharing power. The language of co-design often obscures these distinctions, flattening a spectrum into a single feel-good label.

At one end: extraction. Communities are asked to provide input that's then processed, interpreted, and decided upon elsewhere. The asking creates an appearance of inclusion, but the power to shape outcomes remains concentrated. This is consultation dressed in co-design clothing.

At the other end: genuine shared authority. Community members aren't just providing input—they're shaping the questions, interpreting the findings, and making decisions alongside (or instead of) institutional actors. The process is slower, messier, and harder to control. It's also the only version that deserves the "co-" prefix.

Most participatory work falls somewhere in between. That's not necessarily a failure—context matters, and full power-sharing isn't always possible or appropriate. But honesty requires naming where on the spectrum a given process actually sits, rather than claiming the high ground by default.

The infrastructure participation requires

Here's what rarely makes it into the project plan: co-design is expensive. Not just in dollars, though that too. It costs time. It demands flexibility. It requires relationships that can't be built on a grant timeline.

Genuine participation means meeting people where they are—which might mean evening sessions, weekend workshops, childcare provisions, translation services, transportation support, or honoraria that recognize the value of lived expertise. It means building in time for trust to develop before asking people to share. It means accepting that the timeline will bend around community availability, not the other way around.

Organizations that want to co-design but haven't budgeted for this infrastructure often end up with something that looks participatory on paper but feels extractive to the people involved. The gap between intention and experience is where trust goes to die.

The facilitation paradox

Co-design requires skilled facilitation. But facilitation, by its nature, shapes what's possible. The person holding the marker, setting the agenda, and synthesizing the sticky notes wields considerable influence—even when they're trying not to.

This is the paradox at the heart of participatory work: someone has to design the process by which others will participate. That meta-design layer is rarely co-created. The frames, tools, and constraints are usually set before community members enter the room.

Good facilitators hold this tension consciously. They name their own positionality. They build in moments for participants to reshape the process itself. They're willing to abandon their carefully designed agenda when the room needs something different. They understand that their job is to distribute power, not just manage logistics.

But let's be honest: most co-design processes aren't facilitated by people with this level of skill or self-awareness. The sector underinvests in facilitation capacity, treats it as a soft skill anyone can pick up, and then wonders why participatory processes feel hollow.

When co-design isn't the answer

Here's something that doesn't get said enough: not everything needs to be co-designed.

Some decisions are technical. Some are time-sensitive. Some involve information that can't be widely shared. Some affect communities that are too diffuse or too burned out to convene. Insisting on participatory process in these contexts doesn't honor communities—it burdens them.

There's also a risk of participation theater: inviting input on decisions that have already been made, or on questions so narrow that the invitation feels hollow. People can tell when they're being managed rather than consulted. The damage to trust is worse than not asking at all.

The more honest approach is to be clear about what's actually on the table. If you're seeking input but retaining decision-making authority, say so. If you're genuinely open to the process leading somewhere unexpected, demonstrate it by following through when it does.

Co-design is a tool, not a virtue. Knowing when to use it—and when not to—is part of the craft.

The long game

Real participatory practice isn't a project phase. It's a relationship cultivated over time.

The organizations doing this well aren't parachuting into communities for a six-week engagement. They're showing up consistently, building trust through presence, and creating pathways for community members to shape organizational direction at every level—not just in designated "input" moments.

This means governance structures that include community voice. Hiring practices that value lived experience. Feedback loops that actually close. A willingness to be changed by the communities you serve, not just to change things for them.

It's slower. It's harder to fund. It doesn't fit neatly into a project deliverable. And it's the only version of co-design that actually delivers on the promise.

The word gets used a lot. Co-design. Co-creation. Participatory process. It appears in grant applications and strategic plans, on consultant websites and in board presentations. Everyone, it seems, is co-designing now.

Which is precisely why it's worth pausing to ask what the term actually means—and whether the way we're using it matches the promise it implies.

The spectrum of participation

Not all involvement is created equal. There's a meaningful difference between consultation and collaboration, between informing and sharing power. The language of co-design often obscures these distinctions, flattening a spectrum into a single feel-good label.

At one end: extraction. Communities are asked to provide input that's then processed, interpreted, and decided upon elsewhere. The asking creates an appearance of inclusion, but the power to shape outcomes remains concentrated. This is consultation dressed in co-design clothing.

At the other end: genuine shared authority. Community members aren't just providing input—they're shaping the questions, interpreting the findings, and making decisions alongside (or instead of) institutional actors. The process is slower, messier, and harder to control. It's also the only version that deserves the "co-" prefix.

Most participatory work falls somewhere in between. That's not necessarily a failure—context matters, and full power-sharing isn't always possible or appropriate. But honesty requires naming where on the spectrum a given process actually sits, rather than claiming the high ground by default.

The infrastructure participation requires

Here's what rarely makes it into the project plan: co-design is expensive. Not just in dollars, though that too. It costs time. It demands flexibility. It requires relationships that can't be built on a grant timeline.

Genuine participation means meeting people where they are—which might mean evening sessions, weekend workshops, childcare provisions, translation services, transportation support, or honoraria that recognize the value of lived expertise. It means building in time for trust to develop before asking people to share. It means accepting that the timeline will bend around community availability, not the other way around.

Organizations that want to co-design but haven't budgeted for this infrastructure often end up with something that looks participatory on paper but feels extractive to the people involved. The gap between intention and experience is where trust goes to die.

The facilitation paradox

Co-design requires skilled facilitation. But facilitation, by its nature, shapes what's possible. The person holding the marker, setting the agenda, and synthesizing the sticky notes wields considerable influence—even when they're trying not to.

This is the paradox at the heart of participatory work: someone has to design the process by which others will participate. That meta-design layer is rarely co-created. The frames, tools, and constraints are usually set before community members enter the room.

Good facilitators hold this tension consciously. They name their own positionality. They build in moments for participants to reshape the process itself. They're willing to abandon their carefully designed agenda when the room needs something different. They understand that their job is to distribute power, not just manage logistics.

But let's be honest: most co-design processes aren't facilitated by people with this level of skill or self-awareness. The sector underinvests in facilitation capacity, treats it as a soft skill anyone can pick up, and then wonders why participatory processes feel hollow.

When co-design isn't the answer

Here's something that doesn't get said enough: not everything needs to be co-designed.

Some decisions are technical. Some are time-sensitive. Some involve information that can't be widely shared. Some affect communities that are too diffuse or too burned out to convene. Insisting on participatory process in these contexts doesn't honor communities—it burdens them.

There's also a risk of participation theater: inviting input on decisions that have already been made, or on questions so narrow that the invitation feels hollow. People can tell when they're being managed rather than consulted. The damage to trust is worse than not asking at all.

The more honest approach is to be clear about what's actually on the table. If you're seeking input but retaining decision-making authority, say so. If you're genuinely open to the process leading somewhere unexpected, demonstrate it by following through when it does.

Co-design is a tool, not a virtue. Knowing when to use it—and when not to—is part of the craft.

The long game

Real participatory practice isn't a project phase. It's a relationship cultivated over time.

The organizations doing this well aren't parachuting into communities for a six-week engagement. They're showing up consistently, building trust through presence, and creating pathways for community members to shape organizational direction at every level—not just in designated "input" moments.

This means governance structures that include community voice. Hiring practices that value lived experience. Feedback loops that actually close. A willingness to be changed by the communities you serve, not just to change things for them.

It's slower. It's harder to fund. It doesn't fit neatly into a project deliverable. And it's the only version of co-design that actually delivers on the promise.