Knowledge that stays within reach. Original editorial painting of an imagined public sundial, lit by afternoon sun on a blue-violet wall.
Begin with a question residents need answered, and finish with something they can use after the semester ends.
By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.
Knowledge in the Neighborhood. Original editorial painting of an imagined public sundial, a quiet symbol of learning that remains within reach.
A university project can finish beautifully on campus and remain unfinished in the neighborhood.
The presentation earns praise. The students submit their work. A report sits behind a link that requires a university login. Meanwhile, the people who answered the questions still do not know what the findings mean for their next decision.
That is not necessarily a failure of effort. It is often a failure to agree on what completion should look like.
A community partnership should leave more than a record that a university visited. It should leave a better-understood problem, usable findings and people who know how to work with them. Sometimes the most valuable result is a confident decision to try something. Sometimes it is a careful explanation of why the evidence does not yet justify a change.
Both can be useful. Neither happens automatically because respected institutions have agreed to collaborate.
Let the community help choose the question
The first meeting should not begin with a finished questionnaire.
It should begin with the decision people are struggling to make. What do residents need to understand? What have they already tried? Whose account has been missing? What would a useful answer allow them to do differently?
A proposal to “study participation” is still distant from everyday life. A question such as “Would changing the opening hours make this community learning room usable for people who cannot currently attend?” is closer. It identifies a decision, a group whose experience matters and an opportunity to discover that the obvious solution may be wrong.
Residents might explain that opening hours are only part of the problem. The entrance could be hard to find. The last bus might leave too early. An activity description might make beginners feel unwelcome. These observations should be able to change the study, not simply become quotations in its introduction.
The federal Principles of Community Engagement, third edition, published in 2025, emphasizes community self-determination, diversity, shared capacity and long-term commitment. It also adds an explicit principle of demonstrating trustworthiness. These are practical standards for the first conversation: be clear about the purpose, learn the local history and remain willing to share control.
There is no single person called “the community.” An established organization may be an important partner without representing every resident. Make room for people who do not attend its meetings, people who disagree with its leaders and people who need another language or a different way to participate.
Agree on a short statement of the question and the decision it will inform. If the partners cannot explain that statement without university terminology, spend more time on it before collecting information.
Make learning reciprocal, and budget for it
Universities bring methods, specialist knowledge and opportunities for students to learn. Community partners bring knowledge of place, relationships, institutions and what a proposed intervention feels like in daily life.
Neither contribution should be treated as decoration.
A resident who explains why a survey question is misleading is doing intellectual work. So is a community organizer who notices that recruitment is reaching only the easiest people to contact. Their contribution deserves time, recognition and, where appropriate, payment through arrangements agreed in advance.
The budget should account for community coordination, interpretation, accessible meetings, training and the return of findings. A project that can afford data collection but cannot afford to explain the results has defined its obligations too narrowly.
Be equally specific about reciprocal learning. A local partner might want to learn how to read a basic analysis, repeat a small evaluation or recognize a misleading comparison. University participants might need to learn how local decisions are made, why previous research created distrust or which categories do not fit residents' experience.
Write those learning goals beside the research goals. Then allocate responsibility for them. “Capacity building” becomes credible when someone can name the skill, the practice opportunity and the person who will support it.
Use evidence without making it promise too much
There is research behind taking the partnership itself seriously.
In a 2018 mixed-method study, John Oetzel and colleagues identified 294 federally funded US participatory-research projects. Two hundred principal investigators completed a project questionnaire; 450 investigators and partners completed a further survey. Their model found positive associations linking partnership processes, community involvement, collaborative effectiveness and perceived outcomes.
Seven qualitative case studies complemented the survey, with one presented in the paper. That case involved universities and the NICOS Chinese Health Coalition in San Francisco. Eleven stakeholder interviews, a focus group and other material illuminated the importance of local relationships and culturally appropriate communication. The researchers returned case narratives to partners for checking and interpretation.
The limits matter. The survey was cross-sectional and relied on perceptions. It did not establish that a particular partnership arrangement caused better health. One detailed case cannot establish how frequently its experience occurs elsewhere. The evidence supports careful attention to collaboration; it does not turn every university project into a proven intervention.
For a new partnership, the practical lesson is to examine how people work together as well as what they produce. Ask who shaped the questions, who could challenge an interpretation and whether community partners gained something they can use independently.
Settle research ethics before the first interview
A friendly relationship does not remove research responsibilities. Nor does calling a project a student assignment, consultation or evaluation settle which rules apply.
In the United States, the Common Rule defines research in relation to systematic investigation intended to develop or contribute to generalizable knowledge. Its application depends on the activity and applicable oversight, not merely the label on the proposal. Some activities fall outside that definition; some research qualifies for an exemption; some requires institutional review board review. The current federal regulations also recognize circumstances in which an exemption requires limited IRB review.
Take the proposed activities to the university's responsible research-protection office before recruitment or collection begins. Follow its determination process and obtain the required documentation. Community agreement and an institutional review board, or IRB, serve different purposes. One cannot stand in for the other. Relevant local, tribal or national approvals may also apply.
A concrete institutional example is Washington University in St. Louis. Its published process for community research partners moves from collaboration and study design through an HRPO/IRB application, required agreements and human-subjects education. It tells partners not to begin research activity without approval documentation. This is that university's process, not a universal checklist or a substitute for another institution's requirements.
Plan for this work early enough that an academic deadline does not become pressure to skip it. Confirm who supervises students, who can access records and who responds when a participant raises a concern. If the project changes, check whether the approved arrangements must change too.
Consent should be understandable and genuinely optional
A signature is not the whole conversation.
People need to understand what participation involves, why information is being collected, the relevant risks, who can see it and whom to contact with questions. For research requiring consent, the approved process must explain the person's choices, including withdrawal, without promising more control over already-used information than the project can actually provide.
The Office for Human Research Protections describes informed consent as an ongoing exchange, not simply a completed form. Its guidance emphasizes understandable communication, voluntary choice and the opportunity to ask questions.
Make those principles visible in the setting. Do not ask someone to decide while a service provider is waiting beside them for a favorable answer. Make clear that declining research will not cost access to services or benefits to which they are otherwise entitled. A community leader's support does not amount to consent from everyone that leader knows.
Discuss payment and expenses transparently under the applicable review arrangements. Separate permission to take part from permission to use a photograph, identifiable quotation or recording in public communications. If children or others needing additional protections are involved, obtain specialist guidance before designing recruitment or consent.
Being well known locally can help people feel comfortable. It can also make refusal feel awkward. Good partners notice both possibilities.
Agree what happens to the information
“Both partners will have the data” sounds fair until someone asks what that means.
Does it mean identifiable interview recordings? A protected analysis file? Anonymous totals? Who may make copies? Who handles an access request after the student who collected the information graduates?
Before collection, agree in writing on the information needed, authorized access, secure storage, retention and disposal, permitted future uses and responsibility if something goes wrong. Resolve ownership and licensing where relevant, alongside funder, institutional and legal obligations. Specify how community partners will receive useful results without automatically receiving confidential participant records.
Collect less when less can answer the question. Avoid gathering identity documents or detailed personal histories merely because a form has space for them. Store contact details separately where the approved design permits, and do not use personal devices or shared messaging groups as improvised archives.
Removing names does not necessarily make information safe to publish. A distinctive occupation, street and family circumstance can identify someone in a small community. A map or very small subgroup count can reveal more than its author intended. Review releases for those risks, including excerpts chosen for their emotional power.
Agree how findings will be checked before public release. Community review should help catch misinterpretation, identifying detail and missing context. It should not become a promise to hide unwelcome findings. Set a review timetable, record unresolved disagreement and protect the independence and integrity of the analysis.
An illustrative project: deciding whether later hours would help
Consider an imagined community learning room and a university team. This example is not a Feel Worldwide Foundation project, and the numbers below are illustrative.
Residents want to know whether an evening session would reach adults who cannot use the existing afternoon provision. The partners first confirm the applicable review and consent arrangements. They agree that the result must help the local committee decide whether to fund a limited trial, rather than produce a sweeping claim about the whole neighborhood.
Suppose 64 adults answer a voluntary questionnaire, and 40 prefer an evening option. That is 62.5 percent of respondents. It is not evidence that 62.5 percent of all local adults want evening sessions. The report should describe recruitment, who was missed and why people already interested in the learning room may be more likely to answer.
Twelve follow-up interviews might reveal that an evening opening would help some people but would leave others without transport or suitable care arrangements. Those accounts explain possible barriers. They do not establish how common each barrier is across the neighborhood, and the team should not claim completeness simply because twelve interviews have been conducted.
The useful result could be modest: a short decision brief, a costed trial proposal prepared with the committee, and a reusable way to record attendance without collecting unnecessary personal information. Residents review whether the interpretation fits their experience. The report retains disagreement and uncertainty.
The committee might choose a six-week trial, seek more information or decide the proposed hours would exclude too many people. The university has not failed because the answer is complicated. It has helped if the decision is clearer and the community can explain the reasons for it.
Return findings in a form people can actually use
Decide the return format at the beginning, not during the last week.
A technical report can matter. So can an accessible two-page summary, a translated explanation, a public discussion or an editable tool that works on the community partner's existing equipment. The appropriate format depends on the intended users and the decision they face.
A useful summary should say what was asked, what was done, what was found, what remains uncertain and what options follow. Keep the distinction between evidence and recommendation visible. If the recommendation depends on a budget, a service change or further permission, say so.
Do not make a university login the only door to the result. Provide an agreed, accessible copy that the community partner is permitted to keep and share. Include the methods, definitions and date so that someone reading it later can understand its limits. Discuss credit and authorship early, reflecting actual contributions and applicable publication standards.
Test usefulness with the people expected to use the work. Can they find the answer to their question? Can they explain an important limitation? Can they repeat the small task the project is leaving behind without calling the researcher every time?
These are more revealing tests than whether everyone enjoyed the final presentation.
Make continuity honest
A semester ends. A grant closes. A coordinator changes jobs. None of these events should erase the partnership's practical memory.
Before finishing, name the university contact who remains responsible, the community custodian of the agreed outputs and the funded period of follow-up support. Specify what that support covers. One scheduled interpretation meeting is a real commitment. An undefined promise to “remain available” may not be.
Leave usable files, permissions, instructions and a record of unresolved questions. If there is a tool, identify its maintenance cost and who can update it. If continuing support is unavailable, disclose that before the community becomes dependent on it.
Close the project with a shared review. Which resident-defined question was answered? Who benefited from the learning? What did the partnership ask of people? What can the community now do with less dependence on outsiders? What should a future team avoid repeating?
A university partnership is strongest when the community is not left waiting for the university to return before it can act on what it learned.
Organizations interested in exploring a defined community–university collaboration can submit a partnership inquiry to Feel Worldwide Foundation Inc. Describe the local question, proposed contribution and intended community benefit. An inquiry begins a discussion of scope and capacity; it does not establish a university agreement, research approval or funding commitment. Those wishing to support the Foundation can visit its donation page. This article does not designate donations for a particular research project.
