by Dr. Kevin Dean, President & CEO, Tennessee Nonprofit Network
At some point, every organization has faced the challenge of a forced collaboration with another nonprofit. It arrives, not as a gentle suggestion whispered on a spring breeze, but as a decree, etched in stone, often handed down from on high by external forces with an unshakeable belief in the magical, glitter-farting efficacy of synergy. Or, perhaps, it emanates from within, a bright idea from a well-meaning board member who just finished a self-help book on “collective genius,” or an overly enthusiastic CEO who just returned from a conference touting the latest buzzword: “cross-sectoral partnerships for maximum, mind-bending impact!” And while we would all like to think that every collaboration will be magical, often they are an absolute trainwreck.
Can I be brutally honest? The most notorious culprits in this collaborative conscription are often the funders. Oh, noble philanthropy, with your deep pockets, your even deeper desire to see your dollars stretched to their absolute, collaborative limit, and your sometimes questionable grasp of on-the-ground realities. You demand that two, three, or even seven nonprofits, each with its own mission, its own peculiar culture (one might call it charmingly eccentric, another might just call it a glorified hoarding problem), and its own deeply ingrained quirks, link arms and skip merrily into the sunset of shared goals. Whether it makes an ounce of practical sense to anyone actually doing the gritty, often-thankless work is, at times, a secondary consideration. The pronouncement lands, heavy and undeniable: “We will fund this only if you collaborate.” It’s the philanthropic equivalent of being told, “You will play nicely with others, even if ‘others’ are the kid who eats glue or that one kid that runs around pinching everyone, or you will not play at all.”
Now, occasionally, these forced unions blossom into something genuinely beautiful. A harmonious blending of resources, a shared understanding that transcends individual agendas, and a palpable improvement in the lives of those served. These are the unicorns of the nonprofit world held up as paragons of what could be, usually by people who’ve never actually managed one. They’re like Bigfoot sightings – everyone’s heard of them, but has anyone really seen one up close, thriving, and not just desperately trying to escape?
More often, however, these forced collaborations morph into something far more… combustible. We’re talking less “symphony of service” and more “Fyre Fest on a shoestring budget, but instead of sandy beaches, you get a leaky basement and all the ‘influencers’ are just exhausted social workers.” Remember the images of disillusioned attendees, half-built tents, and single slices of cheese on bread? Imagine that, but instead of trying to find Rihanna, you’re trying to figure out why your “partner” organization keeps scheduling meetings during your peak program hours, and their idea of “shared data” is a blurry photo of a handwritten ledger. It’s underfunded programs, mismatched expectations, and the silent, seething resentment of overworked staff trying to make sense of a collaboration that, to them, feels less like a partnership and more like a poorly organized hostage negotiation where everyone’s holding a clipboard instead of a gun.
The reasons for these collaborative car crashes are as varied as the personalities involved. Sometimes it’s a fundamental misalignment of goals, where one organization is aiming for Mars (with a grant for “interstellar youth engagement”) while the other is still trying to master the art of convincing local squirrels not to chew through the power lines (a surprisingly common nonprofit challenge). Other times, it’s a profound lack of clarity on roles and responsibilities, leading to a perpetual game of “Whose job is it anyway? No, really, I’ve asked like five times.” And then, of course, there’s the evergreen villain: ego. The deeply entrenched belief that “our way is the best way, and also, we invented the best way, and anyone who disagrees is clearly misguided.” It’s a quiet hum of superiority that can drown out any genuine attempt at shared decision-making, replaced by the grating sound of one organization consistently trying to subtly (or not so subtly) absorb the other. Whatever the precise cocktail of well-meaning incompetence and misplaced optimism, forced collaborations rarely, if ever, serve anyone well. They often drain precious resources, deflate morale faster than a balloon at a porcupine convention, and ultimately, fail the very communities they ostensibly set out to assist, leaving everyone involved wondering if they could have just done more good by simply staying in their own lanes and not actively making things worse.
The wry humor of it all lies in the absurdity. We are, after all, in the business of helping people. And yet, sometimes, the very mechanisms designed to enhance that help end up hindering it, all in the name of a concept – collaboration – that, when genuinely embraced, is undeniably powerful. When it’s not embraced, it’s just a lot of awkward forced smiles and passive-aggressive email chains.
So, the million-dollar question, or perhaps the multi-million-dollar question if you’re talking to a major foundation with an “innovation fund” for synergistic solutions, is this: How do we get to a place where nonprofits naturally collaborate, where the desire to work together springs organically from a shared understanding of need and opportunity, rather than from the strong, often heavy-handed, insistence of philanthropy, which sometimes feels less like support and more like a benevolent dictator with a spreadsheet? And, equally important, when does it truly make sense to collaborate, and when is it a fool’s errand best avoided, perhaps with a dramatic eye-roll and a strategically timed “urgent” phone call?
The Collaborative Compass: When to Say “I Do” (and When to Say “Oh, Hell No”)
First, let’s address the fundamental truth: not all partnerships are created equal, and not all problems are best solved by a committee of well-intentioned but fundamentally disparate organizations. Collaboration, at its best, is a strategic tool, like a very precise, very expensive wrench. At its worst, it’s trying to hammer a screw with a banana.
When it makes sense to collaborate:
- Shared Vision, Shared Problem: This is the bedrock. If two or more organizations genuinely identify the same problem and envision a similar desired outcome, a collaborative approach can amplify impact. Think of it as two rivers converging to form a mighty, salmon-rich stream, rather than two puddles trying to merge into a single, slightly larger, muddy puddle that mostly just evaporates.
- Complementary Strengths (or, “You’re good at that, I’m good at this, let’s not step on each other’s toes”): Does one organization excel at direct service delivery while another has unparalleled expertise in policy advocacy (and, crucially, doesn’t try to “help” with direct service)? Do you both serve the same population but address different facets of their needs, like one provides food and the other provides interpretive dance therapy (hey, it could work!)? This is fertile ground for collaboration. It’s about recognizing that 1+1 can indeed equal 3 (or 4, or 5, if you’ve had enough coffee), especially when you’re combining unique, yet complementary, assets without trying to micromanage each other’s brilliance.
- Resource Optimization (or, “We’re all broke, let’s share the paperclips”): When resources (financial, human, or intellectual) are scarce, pooling them can be a pragmatic necessity. Sharing administrative functions, co-locating (if you can stand the noise of your partner’s perpetually ringing phone), or jointly pursuing funding can free up capacity for core programming. It’s like a potluck, but instead of questionable casserole, you get to share a really good grant writer.
- Systemic Change (or, “This problem is so big, we need a small army, not just me and my intern”): Tackling complex, systemic issues often requires a multifaceted approach that no single organization can achieve alone. Think of issues like homelessness, educational inequity, or public health crises. These demand a symphony of efforts, not a kazoo solo performed by a slightly bewildered CEO.
- Learning and Innovation (and avoiding re-inventing the wheel, poorly): Collaboration can be a powerful engine for shared learning and innovation. Exchanging best practices, co-creating new solutions, and collectively adapting to challenges can lead to more effective and sustainable approaches. Plus, it’s far less embarrassing to fail spectacularly as a group than to do it all by yourself.
When to fear a collaboration (warning signs and red flags, possibly waving frantically in a hurricane):
- The Funding Mandate (and nothing else, not even a shared affinity for terrible office coffee): If the primary, or sole, impetus for collaboration is a funder’s demand, and there’s no organic desire or strategic alignment otherwise, proceed with extreme caution. This is often where the Fyre Fests begin, only instead of a luxury resort, you’re looking at a poorly attended stakeholder meeting in a drab conference room.
- Vague Goals and Undefined Roles (or, “So, are we doing… things?”): If, after several meetings, you’re still unclear about the precise objectives of the collaboration or who is responsible for what, you’re sailing into choppy, shark-infested waters with a leaky boat and no map. A lack of clarity is the fog that leads to shipwreck, and probably a very awkward post-mortem meeting.
- Unequal Power Dynamics (and one organization clearly thinks they’re Beyoncé and you’re just a backup dancer): One organization consistently dominating discussions, making unilateral decisions, or viewing others as mere subcontractors is a recipe for disaster, resentment, and probably some very passive-aggressive meeting minutes. True collaboration requires mutual respect and a relatively balanced playing field, not a game of king of the hill.
- History of Distrust or Competition (or, “Oh, they’re involved? I remember when they stole our grant writer’s stapler”): If there’s a long-standing history of animosity, competition, or even just a general lack of regard between the potential partners, forcing them together is like trying to mix oil and water while simultaneously trying to teach cats to play poker. It might look okay for a moment, but it will always separate, and someone will end up with a very oily, confused cat.
- Ego in the Room (and Refusing to Leave, probably talking loudly on its cell phone): When individuals or organizations prioritize their own brand, credit, or “our way is superior” mantra over the collective good of the community served, the collaboration is doomed. This is arguably the most insidious and difficult obstacle to overcome, mostly because ego tends to wear very thick armor.
- Lack of Dedicated Resources (and the assumption that collaboration just magically happens, like photosynthesis): Collaboration takes time, effort, and often, specific financial resources. If no one is allocated time or budget to manage the collaboration effectively, it will inevitably become an afterthought, then a burden, and finally, a dusty, forgotten line item in someone’s “lessons learned” report.
- Mission Drift Concerns (or, “Wait, are we still helping people, or are we just… doing whatever they want?”): If collaborating requires one or more organizations to significantly deviate from their core mission or values, it’s a non-starter. A collaborative effort should enhance, not dilute, your fundamental purpose, unless your fundamental purpose was “avoid collaboration at all costs,” in which case, you’re doing great.
The Collaborative Blueprint: Pieces That Need to Be in Place (Unless You Enjoy Chaos)
So, you’ve decided the stars (and the strategic rationale, and maybe a very compelling argument from your board) are aligned for a collaboration. Excellent! Now, let’s talk about the practical architecture required to build something sturdy, something that won’t collapse faster than a Jenga tower in an earthquake.
- Memorandum of Understanding (MOU) or Formal Agreement (aka, “The Legal Love Letter”): This isn’t sexy, unless your idea of sexy involves meticulously detailed clauses, but it’s absolutely critical. Think of it as the pre-nuptial agreement for your collaborative marriage, except without the awkward family drama (usually). It should clearly delineate:
- Purpose and Scope: What exactly are you trying to achieve together? What are the boundaries of this collaboration? (e.g., “We are collaborating on youth mental health, not on who gets the last slice of office pizza.”)
- Roles and Responsibilities: Who is doing what? Who is leading which aspect? Be as granular as possible, right down to who’s bringing the snacks for meetings.
- Decision-Making Process: How will decisions be made? By consensus? Majority vote? Who has the final say on what? (And who has the final say on who has the final say?)
- Communication Protocols: How often will you meet? What platforms will you use? How will information be shared? (Hint: “telepathy” is not an acceptable answer.)
- Resource Contributions: What financial, human, or in-kind resources is each organization bringing to the table? (Be specific; “good vibes” do not count as an in-kind contribution.)
- Intellectual Property: Who owns any shared products or knowledge created? Because nothing says “collaboration gone wrong” like a copyright dispute over a particularly effective brochure.
- Conflict Resolution: How will disagreements be handled? Because, inevitably, they will arise, often over something surprisingly mundane, like the font choice on a shared document.
- Exit Strategy: What happens if the collaboration needs to end? How will assets be divided? How will clients be transitioned? This is often overlooked but vital, especially if you want to avoid a messy, public divorce.
- Aligned Vision and Goals (and not just “doing good stuff”): This goes beyond just a shared problem. It means you both see the desired future state in a similar way and agree on the specific, measurable, achievable, relevant, and time-bound (SMART) goals that will get you there. This requires genuine dialogue, not just a superficial nod to commonality that sounds suspiciously like “blah, blah, synergy, blah.”
- Shared Responsibilities and Workload Equity (because no one likes a freeloader): Collaboration implies a shared burden, not just shared benefits. Each partner must genuinely contribute and feel that the workload is distributed fairly, recognizing that “fairly” doesn’t always mean “equally” but rather “proportionately to capacity and contribution.” No one wants to be the one doing all the heavy lifting while the other partner is busy perfecting their “thought leadership” tweets.
- Putting Ego to the Side in Service to the Community Served (the impossible dream, sometimes): This is perhaps the most challenging, yet most essential, ingredient. True collaboration demands humility, which, let’s face it, is not always abundant in the nonprofit sector (we’re all very passionate, which sometimes looks a lot like stubbornness). It requires leaders and staff to genuinely prioritize the needs of the community over organizational branding, individual recognition, or ingrained ways of operating. It means asking, “What is best for the people we serve?” and being willing to adapt your own approach in light of that answer, even if it means admitting your way isn’t the only way. This means celebrating collective wins, not just individual ones, and being gracious when another partner takes the lead or receives recognition (even if you secretly think your contribution was slightly more impactful).
- Clear and Consistent Communication (the antidote to passive-aggressive whispers): Misunderstandings breed resentment faster than rabbits breed. Regular, transparent, and open communication channels are non-negotiable. This isn’t just about formal meetings; it’s about informal check-ins, quick clarifications, and a willingness to address issues proactively, before they fester into full-blown organizational feuds over who gets the better parking spot.
- Trust and Mutual Respect (like glitter, hard to build, easy to lose): These are built over time, through consistent positive interactions and shared successes. But they are foundational. If there’s an underlying current of suspicion or disrespect, the collaborative house will quickly crumble, probably in a shower of passive-aggressive emails.
- Dedicated Leadership and Staff Buy-in (or, “This isn’t just another thing on my already overflowing plate, right?”): Collaboration can’t be an add-on; it needs dedicated time, attention, and leadership. If the executive director isn’t fully committed (beyond just saying “synergy” three times in every meeting), and if the staff implementing the work aren’t on board, it’s destined to be a top-down mandate that fizzles out at the operational level, leaving everyone confused and even more stressed.
Feedback for Philanthropy: Fostering Genuine Collaboration, Not Forced Marriages
To their credit, funders genuinely want to maximize their impact. The desire to see nonprofits work together often stems from a belief that synergy will unlock greater efficiency and effectiveness. However, the execution often misses the mark, sometimes spectacularly. Here’s how philanthropy can be a better facilitator of collaboration, rather than a demanding orchestrator who insists on everyone dancing to their oddly specific rhythm:
- Fund Collaboration, Don’t Mandate It (think dating service, not arranged marriage): Instead of making collaboration a condition of funding, offer it as an opportunity for enhanced funding or as a separate, tantalizing funding stream for collaborative initiatives. Create incentives for organic partnerships that actually make sense, rather than penalizing those who aren’t (yet) ready or for whom collaboration simply doesn’t fit their unique mission. Think of it like this: you can suggest two people might be great together, but you can’t force them to go on a second date, let alone get married and share a checking account.
- Listen to the Field (because the people doing the work actually know things): Before dictating partnerships, ask nonprofits on the ground what collaborations they see as genuinely beneficial. Who are they already working with informally? What are the existing gaps that could be filled by a strategic alliance? The best collaborations often emerge from shared understanding of community needs, not a funder’s spreadsheet that looks impressive but has no connection to reality.
- Support the “Soft Costs” of Collaboration (because magic doesn’t pay the bills): Collaboration isn’t free. It requires time for meetings, relationship building, shared planning, and communication. Funders should explicitly offer funding for these often-overlooked “process costs,” not just the programmatic outcomes. This includes staff time (to, you know, actually do the collaboration work), facilitator fees (because sometimes you need a professional referee), shared administrative support, and even, dare I say it, a budget for occasional celebratory lunches to foster team cohesion and prevent staff from secretly resenting each other over lukewarm coffee.
- Be Patient and Flexible (Rome wasn’t built in a day, and neither are successful partnerships): Genuine collaboration takes time to blossom, like a very slow-growing, slightly prickly plant. Funders need to offer multi-year, flexible funding that allows partnerships to evolve, adapt, and learn from mistakes (because there will be mistakes, probably involving a shared Google Doc and someone accidentally deleting everything). A one-year grant with strict collaborative deliverables is a recipe for a superficial, rushed, and ultimately ineffective partnership that collapses under its own weight.
- Focus on Outcomes, Not Just Inputs (we care about what happens, not just who is in the room): Instead of demanding how nonprofits collaborate (e.g., “you must partner with X and Y and wear matching t-shirts”), focus on the desired community outcomes. Let the nonprofits determine the most effective strategies, including whether or not collaboration is the right tool for that particular outcome. Trust them; they’re the ones actually doing the work, not just funding the PowerPoints about it.
- Provide Capacity Building for Collaboration (because nobody is born knowing how to write an MOU): Many nonprofits lack the skills and experience in effective partnership management, conflict resolution, or formalizing agreements. Funders could offer or fund training, coaching, or even external facilitators to help build these crucial capacities. Think of it as providing “collaboration therapy.”
- Champion Trust and Risk-Taking (and don’t punish for trying): Acknowledge that not all collaborations will be resounding successes, and that’s okay. Create an environment where nonprofits feel safe to experiment, learn from failures (because lessons learned from spectacular failures are often the most valuable), and even gracefully exit a partnership if it’s not working, without fear of losing future funding. Reward honest assessment, not just rosy, exaggerated success stories.
- Lead by Example (practice what you preach, philanthropy!): If philanthropy truly believes in collaboration, then foundations themselves should demonstrate collaborative practices. Sharing data, co-funding initiatives, aligning their own strategies, and maybe even co-hosting a really good potluck can send a powerful message and model the very behavior they wish to see.
In the grand theatrical production of the nonprofit world, collaboration can be the dazzling ensemble performance or the discordant mess of actors tripping over each other, forgetting their lines, and subtly trying to steal each other’s props. When it’s forced, it often feels like a poorly rehearsed school play where no one remembers their lines and the stage props keep falling over (and then someone blames the other school involved). But when it’s organic, driven by a shared purpose and fueled by genuine respect, it can be a magnificent ballet of synchronized efforts, each movement contributing to a larger, more impactful whole, potentially even with a satisfying, drama-free curtain call.
The key, then, is to move beyond the decree and towards the genuine invitation. To shift from “You will collaborate, or else!” to “Let’s explore how we can collaborate to achieve something truly remarkable for our communities, and maybe share some genuinely good coffee while we’re at it.” And in that shift lies the potential for real, sustainable, and genuinely wryly humorous, success. After all, if we can laugh at the collaborative chaos, perhaps we can learn to create something far more harmonious, and far less like a “do over” of Fyre Fest.