Photo courtesy of Pexels/AI25 Studio
Every association world has at least one version of this relationship: two organizations that share a mission, a name, and sometimes a board table — but perhaps not a clear reporting line. An association and its foundation. A society and its political action committee. A national body and a state affiliate. On paper, the relationship is collaborative. In practice, it's often undocumented, assumption-built, and one hard conversation away from falling apart.
We've facilitated this exact dynamic more than once, in more than one form. The organizations are always different. The underlying pattern is remarkably consistent — and so, we've found, is the path through it.
How the Tension Actually Builds
It rarely starts as a crisis. It starts as an absence.
There's no shared system for tracking the staff time or operational support one organization provides the other. There's no dedicated staff position — no CEO or ED equivalent — for the smaller or newer entity, so its volunteer board ends up managing both strategy and day-to-day operations, a job it was never structured to do. Expectations on both sides run high, but they were never written down, agreed to, or supervised against.
For a while, this works well enough. Then something forces a closer look — a budget review, a strategic planning process, a leadership transition — and the gap becomes visible. One side starts to feel under-supported and under-valued, wondering whether the help they were promised has actually shown up. The other side starts to feel that its time and effort haven't been respected, that requests have become demands, that goodwill has quietly turned into obligation.
Neither party is wrong, exactly. They're each responding to a real experience. But because the relationship was built on assumption rather than agreement, there's no shared reference point to resolve the disagreement — so it doesn't get resolved. It gets retold, from two increasingly separate points of view.
The Breaking Point Is Rarely the Real Problem
In our experience, the moment things visibly rupture — a contested document, a tense meeting, a task force that stops meeting altogether — is almost never the actual source of the conflict. It's the pressure release valve for everything that built up underneath it.
A formal agreement gets drafted to finally put boundaries and expectations in writing. But if that document arrives as something done to one party rather than with them — reviewed by attorneys, presented as a near-final draft, handed across the table instead of built across it — the process itself becomes the next injury. Even a well-intentioned attempt to fix the relationship can deepen the mistrust it was meant to repair.
This is a pattern worth naming on its own: the vehicle for repair has to be as collaborative as the outcome you want. A unilaterally drafted MOU, however fair its terms, tells the other party something about how much their input matters — regardless of what the document actually says.
When talks stall here, it's common for a well-meaning leader to step back from the conversation entirely, hoping to preserve neutrality. Sometimes that's the right call. But it can also leave a communication vacuum exactly when steady, visible leadership is needed most — and both organizations are left telling separate stories about what happened and why, with no shared space to test those stories against each other.
What Facilitation Actually Does in This Situation
A facilitator's job here isn't to referee who's right. It's to build the shared space and shared process that never existed in the first place — and to make sure both parties actually help build it, rather than have it built for them. That work tends to move through four phases.
Phase 1. Listen Before You Convene
Before anyone is asked to sit across the table from one another, individual and confidential conversations with everyone involved — board members, staff, volunteer leaders on both sides — surface what's really going on beneath the positions people have already staked out publicly. This step matters for two reasons. First, it gives people a low-stakes way to say the harder things they wouldn't say in a group setting, especially early on. Second, it lets the facilitator synthesize what's actually true across both sides into one neutral summary of themes, agreements, and points of friction — with individual comments folded in anonymously so no one is identifiable. That summary becomes the group's shared starting point, instead of each side's separate account of events.
Phase 2. Give the Group Structure, Not Just Airtime
Once the parties are back in a room together — often for the first time in months — the instinct is to let people talk it out. That rarely works on its own. Unstructured venting tends to reopen wounds rather than close them, and it lets the loudest voice or the most entrenched position dominate the room.
This is where structured facilitation methodologies earn their keep. Two, used together, tend to be especially effective for this kind of relational repair:
Together, these approaches let a group hold real emotion and real disagreement — because pretending those aren't present rarely works — while still moving methodically toward something durable, rather than circling the same grievances session after session.
Phase 3. Co-Create the Fix, Don't Hand One Down
Whatever agreement, framework, or document eventually resolves the conflict has to be built jointly — not revised by one side and delivered to the other, no matter how reasonable the revisions are. This is the step most organizations are tempted to rush, because a co-created process is slower than a unilateral one. It's also the step that determines whether the outcome actually holds.
In practice, this phase usually produces more than one deliverable: a jointly built agreement governing the relationship going forward, a lightweight and mutually agreed way to track and value the support one side provides the other, and a clear structure for how staff support is requested, assigned, and reported — so that operational decisions don't keep landing on a volunteer board's desk by default.
Phase 4. Don't Walk Away the Moment It's Signed
An agreement drafted in a facilitated process still has to survive contact with real life — the next budget season, the next leadership transition, the next disagreement about who owns what. Relationships that were repaired once but never checked on tend to drift back toward old patterns, quietly and gradually, until the same tension resurfaces a year or two later.
Scheduled check-ins over the following year — short, low-lift sessions with the key leaders on both sides — catch small strains early, before they escalate into the kind of breakdown that required outside help the first time. The goal of this phase isn't ongoing dependency on a facilitator; it's making sure the organizations have internalized the norms and habits well enough to sustain them on their own, with a light-touch safety net in place while that muscle memory forms.
The Pattern Behind the Pattern
Strip away the specifics — the document, the industry, the org chart — and what's usually driving this kind of conflict is the same thing: two groups making reasonable decisions in the absence of a shared framework, and then experiencing each other's decisions as unreasonable.
The fix isn't finding out who was right. It's building the framework that should have existed from the start — a documented, mutually agreed understanding of expectations, roles, and communication norms — and building it in a way that both parties can point to and say, genuinely, "we made this together."
If your organization has a version of this relationship — a foundation, an affiliate, a partner entity where the lines of accountability have quietly blurred over time — the moment to build that shared framework is before the tension boils over, not after. But if you're already past that point, the path back is well-worn. It just requires walking it together.
