Before the Handshake, the Dictionary: How Shared Vocabulary Determines Who Gets a Seat at the Coalition Table

At a recent regional convening of community organizations in the Midwest, a representative from a neighborhood food pantry raised her hand during a planning session and asked a simple question: what, exactly, did the facilitator mean by 'capacity building'? The room paused. The facilitator offered a definition. Three other attendees quietly admitted they had been nodding along without understanding the term either.

That moment captures a problem rarely named in partnership literature: vocabulary is power. In coalitions where hospitals, universities, and county agencies sit alongside food pantries, tenant associations, and volunteer-run youth programs, the language of the partnership is usually set by whoever holds the largest budget. Everyone else is expected to keep up.

The Quiet Exclusion of Jargon

The vocabulary of the nonprofit sector has expanded rapidly over the past decade. Terms like 'theory of change,' 'backbone organization,' 'collective impact,' and 'memorandum of understanding' circulate freely in RFPs, grant reports, and coalition charters. None of these terms is inherently obscure. But for a small organization staffed by two people and a rotating cast of volunteers, the translation burden is real.

The consequences are not merely cosmetic. When a grassroots leader does not fully understand what a 'deliverable' is, she may decline to commit to one rather than reveal uncertainty. When an MOU arrives with dense legal phrasing, a small organization may sign it without negotiating terms it cannot meet. Over time, the same groups end up cast as recipients of services rather than co-authors of strategy — not because they lack expertise, but because the meeting was conducted in a dialect they were never taught.

This dynamic has taken on new urgency as federal grant programs tighten reporting expectations. Smaller organizations that once operated on trust and goodwill now face compliance language, data-sharing agreements, and outcome frameworks. The stakes of misunderstanding have risen accordingly.

What a Shared Glossary Actually Does

The remedy is disarmingly simple: before a coalition adopts its charter, workplan, or MOU, the partners should agree on what their words mean. A shared glossary is not a legal document. It is a working agreement — typically two to four pages — that defines the terms the partnership will use, in language every partner has reviewed and approved.

Done well, the process matters as much as the product. Each partner nominates terms they find confusing. Definitions are drafted in plain English, read aloud, and revised until no one at the table is pretending. The final document is adopted by consensus and revisited annually. Smaller partners gain a genuine foothold: they can point to the glossary whenever the conversation drifts into unexplained shorthand.

Larger institutions benefit too. A shared vocabulary reduces rework, prevents disputes over ambiguous commitments, and signals good faith. Several funders now view a signed glossary as evidence of authentic community engagement — a factor that carries weight in federal and philanthropic applications alike.

A Starter Glossary: Twenty Terms in Plain English

The list below offers definitions any coalition can adapt. Each has been reviewed for clarity and stripped of circular phrasing.

1. Deliverable — A specific product or result a partner promises to complete by a set date, such as a report, event, or training session.
2. MOU (Memorandum of Understanding) — A written agreement describing what each partner will do. It may or may not be legally binding; the document should say which.
3. Capacity building — Activities that strengthen an organization's ability to do its work, such as training staff, improving systems, or adding equipment.
4. Coalition — A group of organizations working toward a shared goal while keeping their own independence.
5. Backbone organization — The one organization in a coalition that handles coordination: scheduling meetings, tracking progress, and keeping partners connected.
6. Collective impact — A structured approach in which many organizations solve one problem together using a common plan and shared measurement.
7. Theory of change — A written explanation of how a program's activities are expected to lead to the results it wants.
8. Outcome — A change that happens because of the work, such as more families having stable housing. An 'output' is what the program produces, such as classes taught.
9. Fiscal sponsor — A tax-exempt organization that receives and manages money on behalf of a group that does not have its own tax-exempt status.
10. Grant reporting — The regular written updates a funder requires, describing how money was spent and what was accomplished.
11. Indirect costs — Shared expenses that support the whole organization, like rent, utilities, and insurance, rather than a single program.
12. Data-sharing agreement — A written document stating what information partners may exchange, how it will be protected, and who may see it.
13. Conflict of interest — A situation in which someone's personal or financial ties could improperly influence an organization's decisions.
14. Scope of work — A description of exactly which tasks a partner is responsible for — and, just as important, which tasks it is not.
15. Stakeholder — Any person or group affected by, or able to affect, the work.
16. Memorandum of record — A short written summary of a meeting or decision, kept so partners remember what was agreed.
17. Referral pathway — The agreed-upon process for connecting a person to another organization's services, including who to contact and how quickly.
18. Sustainability plan — A written strategy for continuing a program after its current funding ends.
19. Memorandum of agreement — A binding contract version of an MOU, enforceable in court. Do not sign one without review.
20. Plain language — Writing that the intended reader can understand the first time through.

Adopting the Document: A Practical Sequence

Coalitions ready to formalize a glossary should follow a short, deliberate sequence. First, circulate a blank list and ask every partner to flag terms they want defined. Second, draft definitions in plain language — a useful test is whether a board member's neighbor could paraphrase the definition accurately. Third, hold a working session where definitions are read aloud and amended. Fourth, adopt the document by consensus and attach it to the partnership's charter. Finally, schedule an annual review, adding new terms as federal requirements and program realities evolve.

Two cautions apply. Resist the temptation to outsource the drafting to the largest partner's legal counsel; the glossary's legitimacy depends on co-authorship. And treat the document as a living agreement, not a one-time compliance exercise. A glossary that sits in a shared drive, unread, is no better than the policy manuals it replaces.

Speaking the Same Language, on Purpose

Partnerships are, at their core, acts of translation. Organizations with different histories, budgets, and vocabularies agree to move in the same direction. The coalitions that endure are the ones that make translation an explicit, shared responsibility rather than an invisible burden placed on the smallest partners.

A signed glossary will not fix every imbalance in community collaboration. But it establishes a principle worth defending: no one should have to pretend to understand in order to belong.