Collective impact is a working model in which organizations from several sectors, government, business and civil society, tackle a complex social problem together that none of them can solve alone. The partners agree on how the problem is defined, on goals and on how progress is measured, and each one continues to operate independently within a shared plan. In Israel the model works when there is trust, a clear structure and an integrating body, and it gets stuck when each side guards its own territory.
This article is based on the book "The Power of Collaboration: From Ego-System to Eco-System" by Omri Gefen, in which he describes the model's founding principle: "As part of the model, the players continue to operate independently, as long as they are coordinated and synchronized within the framework of the joint program and assignment. The aim is synergy rather than uniformity."
What Collective Impact Is, and Where It Came From
The model was developed in the United States in 2011, as a continuation of the consensus building work that had been practiced alongside mediation in the decades before it. Its working assumption is simple: complex social problems are not solved by each organization acting separately, even when each of them does excellent work. What's needed is joint action by all the relevant stakeholders, from every sector.
The basis for that kind of action includes agreement on the nature of the problem, a shared vision and platform, a binding definition of goals and actions, and clarity about what is measured and how. One of the more interesting terms in the model is the "backbone organization", a body whose role is to integrate the effort and make sure communication between the partners is direct and continuous. It doesn't manage the partners. It holds the frame.
The Gap Between Sectors: Where It All Begins
To understand why collective impact is so hard to implement, it helps to look at what each sector brings to the table. Government brings regulation, budgets, expertise and access to other ministries, along with slowness, bureaucracy and political considerations. The business sector brings resources, execution capabilities and influence, alongside an interest in profitability, even if an indirect one. The third sector brings passion, a connection to the field and public legitimacy, but also dependence on philanthropy and a narrow focus. Each has a different language, a different pace and a different logic of action. The perceptual conflict is built into the core of the connection, and it directly affects the level of trust.
Omri Gefen describes this tension as the "value paradox". The very diversity between organizations, in resources, expertise and culture, is the source of the high value of working together. And that same diversity is exactly what makes it so hard to agree on goals and processes, let alone carry them out. The response he proposes is in-depth dialogue about understanding the differences, with clarity about what lies in the common denominator and what doesn't, alongside structured collaboration managed by an external, neutral professional.
Most cross-sector partnerships stop at coordination. Passing information, synchronizing, sometimes a little more. A real partnership, in which the players share goals and commitment, is still rare.
What the Field in Israel Shows
Michal Cohen, former Director General of the Ministry of Education and later CEO of the Rashi Foundation, has seen this interface from both sides of the table. Explaining why the Ministry of Education struggled to work with the third sector, she says: "When you are clear about your identity, you have no problem accepting others. Those who are self-confident know how to create cooperations." And on choosing an external facilitator to integrate the process, she adds that it "conveys a message that no one wishes to take control over the discourse. This is one of the keys to success."
The challenge also lives inside the sectors themselves. Inbal Dor Karbel, CEO of the Elem association, says openly: "The sector in itself does not know how to cooperate well enough. We could have created much greater value in policy design, impact, as well as value for the associations, had we worked more in unison." Competition for donations, public attention and credit is stronger in the social field than most people assume.
A study that compared a successful partnership between foundations and government with one that failed found that the difference wasn't in intentions. Both involved tangled relationships and mutual suspicion. What made the difference was identifying mutual added value, a clear definition of the problem, communication mechanisms, mutual legitimacy and a gradual structuring process that also addressed the essence of the partnership itself. A lack of structure, and treating the partnership as a technical and financial transaction, led to failure.
How to Actually Start
Before I invite partners to the table, it's worth asking myself a few questions. Can the problem I'm trying to solve really be solved inside my own organization, or do I keep trying alone out of habit? Who else touches this problem, and what do they see that I don't? Am I willing to define a shared goal and be measured by it, even when the credit won't be mine alone? Do I come to the table secure in my own identity, or afraid that someone will take my place? And who can hold the frame, so that none of the partners feels someone is taking over?
These questions don't replace a structured process. They are the point where it begins.
Frequently Asked Questions
What's the difference between collective impact and ordinary cooperation between organizations?
In ordinary cooperation, each organization advances its own goals and sometimes coordinates with others. In collective impact, the partners agree in advance on how the problem is defined, on shared goals and on metrics, and act in sync within one plan while each keeps its independence.
What does the backbone organization do?
It integrates the effort, maintains continuous communication between the partners and protects the shared frame. It doesn't decide for the partners and doesn't replace them.
Why do most cross-sector partnerships fail?
Usually because of a gap between project goals and the interests of the people involved, hidden agendas, mistrust and the absence of a clear structure. When one side is much stronger than the others, the partnership tends to become instrumental and less effective.
Does government have to be a partner?
Not always, but for most complex social problems it holds the regulation and the budgets, and final responsibility for citizens lies with it. Success depends heavily on the ability of its representatives to see themselves as partners who share opportunity, risk, responsibility and resources.
About the Author
Omri Gefen is a leading organizational consultant to CEOs and senior management teams. He founded Gevim Group and served as its CEO for more than two decades. He specializes in complex processes within and between organizations, including interfaces between the business, public, security and social sectors. His areas of expertise are collaboration, trust, negotiation, mediation and consensus building. He heads negotiation training in the Lahav Executive Program at Tel Aviv University, previously taught at Reichman University and Ben-Gurion University, and developed the Effective Collaboration Architecture (ECA) model. Omri Gefen is the author of "The Power of Collaboration: From Ego-System to Eco-System" (Routledge).
If you are leading, or considering leading, a cross-sector partnership and want to build it right from the start, you're welcome to book an introductory conversation through the consulting page on the website.