Healthcare Needs More Than Community Engagement. It Needs Co-Design
A healthcare organization spends months developing a new initiative. The need is real. The team has done its research. The proposed solution is thoughtful. Then the organization invites patients, families, community organizations, or local leaders into the conversation and asks a familiar question: What do you think?
The discussion may be meaningful. The feedback may be taken seriously. Changes may even be made. But many of the largest decisions have already happened. The problem has been defined. The priorities have been selected. The basic model has been chosen. The budget has been shaped. The technology may already be underway.
At Living with SHAPE, we believe community engagement matters deeply. But if healthcare wants local knowledge to meaningfully shape better solutions, participation often needs to begin earlier.
That is where healthcare co-design becomes different. Community engagement asks people to participate in the process. Co-design asks whether what they know can influence what gets built.
Engagement and Co-Design Are Not the Same Thing
Healthcare organizations have made important progress in how they involve patients and communities. Listening sessions, advisory councils, surveys, focus groups, community meetings, and patient feedback can all reveal perspectives that an organization might otherwise miss.
The distinction is not that engagement is bad and co-design is good. The distinction is influence. An organization can engage a community extensively while keeping most of the important decisions inside its own walls. People may be present, heard, and appreciated, but still have relatively little ability to shape the direction of the work.
Co-design asks a different question: Did what people knew meaningfully influence what we created?
That might mean community experience changes how the problem is understood. It might change who the initiative is designed to serve first, which barriers deserve attention, what language is used, which local organizations should be involved, or whether the original solution is even the right one.
Engagement gives people a voice in the process. Co-design gives their knowledge influence over the design.
Timing Changes the Value of Community Knowledge
In Why Local Knowledge Should Shape Healthcare Design, we explored why communities often understand parts of an environment that are difficult to see from inside a healthcare organization.
The timing of when that knowledge enters the process matters. Local knowledge is most powerful before assumptions become architecture.
Once the basic solution is already set, community input can often influence only the edges. The wording may change. A workflow may be adjusted. A feature may be added. Outreach may be redesigned.
Those changes can still be useful. But earlier participation can influence something much more fundamental: the direction of the work itself.
It can change how the problem is defined, which barriers are considered most important, what strengths already exist, who needs to be involved, what success should mean, and whether the proposed solution fits the realities of the place where it will operate.
Sometimes the biggest design improvement is not a better version of the original idea. It is realizing earlier that a different idea is needed.
Start by Designing the Problem Together
Organizations naturally want to move toward solutions. A challenge is identified, and teams begin asking what program, technology, workflow, partnership, or service might address it.
Co-design begins one step earlier. Before asking “What should we build?”, ask: “Are we even describing the problem correctly?”
Imagine a healthcare organization sees low participation in a community program.
From inside the organization, the problem may look like awareness. The natural response might be more outreach, clearer marketing, or additional reminders.
But families may describe something different. The location is difficult to reach. The hours conflict with work. The language used to describe the service does not match how people understand the need. The organization providing it is unfamiliar. A previous local initiative created mistrust.
Those perspectives do not simply provide feedback on the solution. They change the problem being solved.
What looked like an awareness problem may actually be a transportation problem, a trust problem, a timing problem, or a design problem.
That is why co-design is not simply a more participatory way to build the answer. It can be a better way to understand the question.
Co-Design Does Not Mean Everyone Decides Everything
This distinction is important because the term co-design can sometimes create the impression that every decision must become a group decision. That is neither realistic nor necessary.
Healthcare leaders still carry responsibilities that community participants should not be expected to carry. Clinical safety, regulation, finances, operations, staffing, evidence, privacy, and organizational accountability all require professional expertise and clear decision-making.
Community members bring another form of expertise: their own lives, environments, relationships, experiences, and understanding of how systems function in practice.
Co-design creates a structure where those forms of expertise can influence one another.
It does not eliminate leadership. It improves the information leadership is able to use.
It does not require consensus on every decision. It requires clarity about where community knowledge can genuinely shape the work and honesty about where constraints already exist.
The goal is not to make every person responsible for every part of the design.
The goal is to stop making important design decisions without perspectives that could materially improve them.
Relationships Matter Before the Design Session
Co-design does not begin when people arrive for a workshop. The quality of participation is shaped long before anyone sits around a table.
Do people understand why they are being invited?
Do they know what is genuinely open to change?
Have they seen evidence that previous contributions mattered?
Do they trust the organization asking for their perspective?
Is participation accessible?
Are expectations clear?
These conditions affect whether people feel they are entering a real design conversation or simply being asked to validate work that has already been decided.
This connects directly to the broader community infrastructure we discussed in Community Organizations Are Healthcare Infrastructure. Trusted relationships are not an accessory to community health work. They are part of the infrastructure that makes meaningful collaboration possible.
A healthcare organization cannot expect trust to appear because it schedules a co-design session.
Trust is built through consistency, transparency, respect, and what happens after people contribute.
If a community repeatedly gives input and sees no evidence that it influenced anything, participation eventually becomes performative even if the process was originally well intentioned.
Co-design therefore depends not only on what happens during the design process, but on the quality of the relationship surrounding it.
Community Contribution Should Leave Something Behind
There is another question worth asking: Who benefits from the participation itself?
Community engagement can become extractive when organizations collect local knowledge, use it to improve their initiative, and then move on without strengthening the people or relationships that contributed.
A regenerative approach asks for something more.
Did participants understand how their contributions affected the work?
Did relationships become stronger?
Did the healthcare organization learn something it can carry into future decisions?
Did local knowledge become easier to access and use again?
Did the process create new connections among community partners?
Did community organizations spend time contributing without receiving anything useful in return?
The goal is not that every co-design process must create a new program or formal partnership. It is that participation should not function like a temporary extraction of insight.
The design process itself can strengthen the ecosystem around the work. When people see that their experience mattered, trust can grow. When organizations understand one another better, future coordination becomes easier. When local knowledge is captured thoughtfully, the next initiative does not have to begin from zero.
A strong co-design process leaves behind more than a solution. It leaves behind stronger relationships and a better shared understanding of the system.
Better Solutions May Already Be Partially Present
Co-design is sometimes described as if the goal is always to invent something new.
Often, that is not what communities need.
Local organizations may already have informal pathways that work well. Families may already know which people to call. Frontline staff may have developed effective workarounds. Trusted organizations may already be connecting people across systems. A community may have practices that work precisely because they were shaped over time around local conditions.
The design opportunity may be to recognize those strengths rather than replace them.
This is one reason healthcare co-design fits naturally with the idea that Healthcare does Not Stop at the Clinic Door. Once healthcare looks beyond its organizational boundary, it often discovers that capability already exists across the community.
The question then becomes less: What new thing should we introduce?
And more: What is already working here, and how could we strengthen, connect, or make it easier to use?
Sometimes innovation is not invention. Sometimes it is recognition.
A Practical Leadership Check: How Early Does the Community Enter?
Before your next community-facing initiative moves too far into planning, look at the major decisions ahead and ask when people closest to the experience will first have an opportunity to influence them.
Consider the following:
Has the problem already been defined before community voices enter?
Has the solution already been selected?
Which decisions are still genuinely open to change?
What local knowledge could alter our assumptions?
Who understands this experience from a perspective we do not have?
How will people know whether their contribution influenced the final design?
If most of the meaningful decisions are already closed by the time engagement begins, the organization may be gathering feedback rather than co-designing.
There is nothing inherently wrong with feedback. But it should be named honestly.
The deeper opportunity is to identify one or two important decisions where community knowledge can enter earlier.
That may be enough to substantially change the quality of the design.
Regenerative Psychology™ and Shared Design
Regenerative Psychology™ begins with the assumption that people and communities already carry wisdom and capability.
The role of design is not simply to deliver expertise outward. It is to create conditions where different forms of expertise can meet.
Healthcare may understand the clinical need, regulatory environment, operating model, evidence, and organizational constraints.
Communities may understand daily life, trust, culture, history, relationships, and what becomes difficult when a solution enters the real world.
Neither needs to replace the other. The opportunity is to let them inform one another. That changes the posture from: We are designing for you. to: We are bringing different forms of expertise together to design something that can work here.
That is not less leadership. It is leadership working from a fuller picture.
Co-Design Begins Before the Answer Exists
Community engagement matters. Healthcare organizations should continue listening, surveying, convening, asking for feedback, and building advisory relationships.
But if local knowledge is expected to help create better solutions, listening cannot always happen after the biggest decisions have already been made.
Sometimes the most important change is simply moving participation earlier. Before the plan. Before the prototype. Before the presentation explaining what the organization intends to do. Before the answer exists.
For healthcare leaders, two questions can reveal a great deal:
At what point in our process do community voices actually enter?
By the time they arrive, how much is still genuinely open to change?
Those questions help distinguish participation from influence. Because communities should not only be asked whether a solution works for them. They should have meaningful opportunities to help shape what working looks like in the first place.
Before launching the next community-facing initiative, ask: Which decisions are we making before the people closest to the experience are part of the conversation?
That may be the best place to begin redesigning the design process itself.
Title Tag
Meta Description
Excerpt
Comments