You funded a coalition. You got a committee

The aspiration is completely reasonable: a dozen grantees working on the same issue, so why not one collective campaign bigger than anything any of them could run alone? For the funder who convened it, and the organizations that signed on in good faith, the reality is a familiar disappointment of civil society collaboration: the campaign underdelivers, launches late, or quietly never launches at all. To the outside world, it never sounds like a movement — just a dozen organizations talking near each other about vaguely related things.

The bitter part is that everyone worked hard and meant it. The failure isn't effort, talent, or commitment. It's the model.

​

The campaign-by-a-coalition model fails by design — better intentions won't fix it

Hand a campaign to a coalition as a collective, and three design flaws activate every time. First, responsibility without accountability: when every partner owns the campaign, no one does — there is no single throat to choke when quality slips or deadlines pass. Second, planning by committee: consensus produces the lowest common denominator, a message everyone can tolerate yet no one will champion, delivered on a timeline that respects every partner's calendar and no audience's attention. Third, an expertise gap that coalitions politely ignore: the room is full of issue expertise and thin on persuasion craft. Partners fluent in the movement's own language struggle to reach lay people, and because the communication muscle is unevenly distributed, even an agreed message comes out at wildly uneven quality and reach.

​

The instinctive fix — coordinate harder, meet more, appoint a liaison — is the objection worth retiring. More coordination cannot repair a structural flaw; it just adds meetings. Meanwhile, the public conversation doesn't pause while the coalition gets organized. The space left empty gets filled by whoever will speak into it, including the voices working against everything you're funding.

​

Our model: one central kitchen, many front-end restaurants

We redesigned the model around one principle: production is centralized, distribution stays distributed. C4C operates as the coalition's central kitchen — one expert team accountable for the core narrative, the shared messaging framework, and the creative assets, built to professional standards and on schedule. Each partner is a front-end restaurant: serving that core through its own brand, channels, and relationship with its own diners. Same kitchen, different menus.

​

Notice how this addresses each design flaw rather than workarounds. Accountability: one kitchen owns quality and deadlines — the funder finally has a single point of responsibility. Planning: one strategy, aimed by evidence — through our sister research organization, Bahana, we measure where the public actually stands, so the campaign is built for the audience that exists rather than the one the coalition hopes for. Expertise: partners no longer need in-house persuasion craft, because the kitchen supplies it, which quietly lifts the weakest communicator in the coalition to the standard of the strongest. And the fear that centralization means uniformity gets answered in the design itself: the kitchen fixes only what must be common — core narrative, non-negotiable messages, shared language — while every partner keeps its own voice and audiences. Unified campaign messaging doesn't mean identical campaigns; it means the public hears many organizations and comes away with one clear understanding.

​

One more design requirement: the kitchen cannot be one of the restaurants. A member organization producing for the coalition will always be, fairly or not, suspected of steering the message toward its own interests. A neutral outside team carries no such tax. That neutrality — plus the lab behind us — is why this multi-stakeholder communication strategy holds where the old model collapses.

​

To see how we've helped coalitions stop campaigning like committees and start landing like one force, explore our portfolio below.

Our works: