Why Local Knowledge Should Shape Healthcare Design
A healthcare organization identifies a need. The data is clear, the goal is worthwhile, and the team builds a thoughtful solution. Then implementation begins, and the community responds differently than expected.
People do not use the pathway the way planners anticipated. A resource that looked accessible is difficult to reach. A message that seemed clear does not resonate. A trusted partner was left out. An earlier experience in the community changes how the new program is received.
The problem may not be the quality of the idea. The organization may simply have been missing part of the picture.
At Living with SHAPE, we believe strong community health partnerships begin by recognizing that healthcare organizations and communities hold different forms of expertise. Healthcare brings clinical knowledge, operational experience, evidence, data, and resources. Communities bring lived experience, local history, relationships, cultural context, and practical knowledge about what actually works where people live.
Data can tell us what is happening. Local knowledge can often help us understand why.
That knowledge should not be gathered only after a solution has already been designed. It should help shape the design from the beginning.
Every Community Has Knowledge That Doesn’t Live in a Dashboard
Healthcare data can reveal a great deal. It can show utilization patterns, service gaps, outcomes, diagnoses, geographic differences, access trends, and where demand is increasing.
But a dashboard may not explain why a resource is consistently underused even though it appears available. It may not reveal why families trust one organization and avoid another. It may not show how a past program still influences how people interpret a new one.
Communities often know these things. Families may understand which pathways feel realistic and which do not. Local organizations may know where transportation creates a barrier that looks small on a map but significant in everyday life. Community leaders may understand which relationships carry trust. Frontline organizations may hear the language people actually use to describe a problem, which can be very different from the terminology healthcare uses internally.
This is part of what we explored in Community Organizations Are Healthcare Infrastructure. Community organizations do not only provide services. They also carry relationships, history, and knowledge that help the wider system understand how the community actually functions.
Neither form of knowledge is enough on its own. Data may help identify the pattern. Local knowledge may help explain the pattern.
Local Context Changes What Will Work
Healthcare rightly looks for evidence. If something has worked in another health system, another county, or another population, there is value in understanding why. Proven models can save time, reduce risk, and prevent organizations from rebuilding what already exists. But successful design is rarely just a matter of copying the model.
Relationships differ from place to place. Resources differ. Transportation systems differ. History differs. Culture differs. Community organizations differ. Even the language people use to understand the same need may change.
A behavioral health navigation model that works well in one region may need to be organized differently somewhere else because the provider landscape is different. A digital resource may work well where broadband and digital literacy are strong but create another barrier somewhere else. A community partnership may flourish in one place because trusted relationships already exist and struggle in another where institutions have a different history with the community.
The question should not only be: What has worked somewhere else?
It should also be: What does this place require?
That is not an argument against evidence-based practice. It is an argument for applying evidence with context.
Communities Often See the Spaces Between Services
Healthcare organizations usually understand their own services very well. They know what happens inside their clinics, departments, programs, and workflows. They know their eligibility requirements, staffing structures, technology, and responsibilities.
Community partners often see something different. They see what happens between services. They see the family who received a referral but could not figure out whom to call. They see the patient who was technically connected to a resource but could not meet the eligibility requirements. They see which programs look available on a directory but are difficult to access in practice. They see what people do after the formal pathway does not work.
These spaces between organizations can be difficult for any one institution to see. In Healthcare Doesn’t Stop at the Clinic Door, we explored the idea that people experience one continuous life even when the organizations around them operate through separate structures. Local knowledge helps illuminate that continuous journey.
A health system may understand what happens before a referral.
A community organization may understand what happens after it.
A family may understand what happens between the two.
When those perspectives are separated, part of the journey stays invisible.
When they meet, the system becomes easier to understand.
Ask Earlier
Community engagement often happens after much of the direction has already been established.
The need has been defined.
The solution has been selected.
The presentation has been built.
Then people are invited to give feedback.
That feedback can still be valuable, but by that point the range of possible decisions may already be narrow.
A stronger approach asks for local knowledge earlier.
Before deciding what to build, healthcare leaders can ask:
What are you already seeing?
What strengths already exist?
What has been tried before?
What might we be misunderstanding?
Who else understands this issue differently?
What would make this useful in this community?
These are not questions asked simply to demonstrate engagement. They are design questions. They help healthcare organizations understand the environment in which a solution will have to function before that solution becomes difficult to change.
Earlier involvement creates room for local knowledge to influence the problem definition itself, not just the final implementation. That can change everything downstream.
Local Knowledge Is More Than Feedback
There is an important difference between feedback and shared design.
Feedback asks: What do you think about what we created?
Shared design asks: What should we understand before we create it?
The distinction may sound subtle, but it changes the role of the community. In the first model, healthcare defines the problem, creates the response, and asks the community to react.
In the second, healthcare still brings expertise and responsibility, but it recognizes that defining the problem accurately may require perspectives outside the organization.
This does not mean every community-facing decision needs consensus or an endless series of stakeholder meetings. Healthcare leaders still need to make decisions. Clinical safety, regulation, evidence, operational realities, and resource constraints still matter.
The goal is not to transfer every decision outward. The goal is to make better decisions with a fuller picture.
Local knowledge should influence design, not simply react to it.
Different Forms of Expertise Belong in the Same Conversation
The strongest healthcare design does not require choosing between professional expertise and community expertise. It requires bringing them together.
Healthcare professionals may understand clinical practice, evidence, safety, regulation, operations, reimbursement, technology, and implementation constraints.
Communities may understand lived experience, local conditions, trust, relationships, cultural context, history, and the practical realities of navigating services.
Those forms of knowledge answer different questions. Clinical expertise may tell us what intervention is appropriate. Local knowledge may tell us whether people can realistically reach it. Operational expertise may tell us how a process needs to function internally. Community experience may show where that process becomes confusing from the outside.
Data may reveal that a population is not using a service. Local organizations may help explain why. A better design emerges when these perspectives can inform one another rather than compete for authority.
A Practical Leadership Practice: The Local Knowledge Check
Before beginning the next community-facing initiative, pause before the solution takes shape. Start by defining the issue your organization believes it is trying to solve. Then identify the people and organizations that experience that issue from a different position than you do.
Ask three questions.
What do we already understand well? This may include clinical evidence, utilization data, operational realities, funding, or internal process knowledge.
What might we not be able to see from inside our organization? Think about trust, relationships, practical barriers, local history, cultural context, existing community strengths, or what happens after people leave your services.
Who already understands those parts of the problem? That may include families, community health organizations, schools, faith communities, local nonprofits, frontline professionals, or other trusted partners.
Then bring those perspectives into the conversation before the main solution is decided. The goal is not simply collecting more opinions. It is improving the quality of the picture you are designing from.
Regenerative Psychology™ and Community Intelligence
Regenerative Psychology™ begins with the belief that communities already possess wisdom. That changes how expertise enters a community. The starting assumption is not that one organization arrives with the answer while everyone else provides input around the edges. It is that different people and institutions hold different parts of the intelligence needed to understand the system.
The work becomes creating conditions where those forms of knowledge can meet.
That changes the question from: What solution should we bring here?
to: What can we understand together before deciding what should happen next?
This is not a rejection of expertise. It is a broader definition of it. Healthcare may understand the service. Communities often understand the environment that service has to work within. Both matter.
Better Design Begins With a Fuller Picture
Healthcare organizations bring extraordinary expertise to complex problems.
So do communities. The strongest community health partnerships do not require one form of knowledge to replace the other. They require better ways for those forms of knowledge to meet early enough to shape what gets built.
Before launching the next community-facing initiative, ask: What does this community understand about the problem that we cannot see from inside our organization?
Then ask: Are we learning that before or after we design the solution?
That timing matters. Because understanding a community is not something that happens after design. It is part of design.
Comments