Levels of collaboration are three stages of joint work between units or organizations, as defined by Omri Gefen in the Effective Collaboration Architecture (ECA) model: coordination, cooperation and deep collaboration. Each level rests on the previous one, requires a different investment and produces a different value. The higher level is not necessarily the best one, and what matters is that the partners agree which level they are aiming for.
This article is based on the book "The Power of Collaboration: From Ego-System to Eco-System" by Omri Gefen, in which he explains why a precise definition of the level of collaboration matters so much: "Sometimes, disappointment may emanate between interface partners, with one party holding expectations for a high level of partnership while the other party is aiming for a lower one."
What is the difference between the three levels of collaboration?
Coordination deals with information and synchronization. Units or organizations share knowledge, coordinate actions and sometimes standardize processes, but do not carry things out together. A familiar example is the annual work plan day, in which each manager presents their plan to the others. This is information sharing. Nothing more. Coordination has value, and it does not require a large investment or high dependence, but it only makes it possible to deal with familiar and relatively simple challenges.
Even coordination is not as simple as it sounds. Omri Gefen notes that information is power, so it is natural for us to declare transparency while in practice sharing in a limited way, enough to be perceived positively and no more. Below coordination there is an even lower level, co-existence, in which each side is aware of the other's existence and nothing more.
Cooperation deals with joint action around a task, a project or a move defined in time and scope. Here the investment is higher, and so are the dependence and the risk. Omri Gefen puts the difference this way: "Coordination is primarily intended for achieving organizational efficiency, while cooperation is designed to achieve effectiveness." One example he gives is the precise cooperation between the police and the military in the summer of 2005, which included joint planning, full integration of capabilities and joint training.
Deep collaboration rests on the two previous levels and deepens them. Its essence is relevance. Organizations remove walls, create long-term commitments and act together even in their core areas. It is first of all a strategy, and only later tactics, and it depends more than any other level on the mindset of managers and on leadership.
What does the difference between the levels look like in practice?
The report of the commission of inquiry into the events of September 11 captures the gap between the levels in one sentence: "When agencies cooperate, one defines the problem and seeks help with it. When they act jointly, the problem and options for action are defined differently from the start." In deep collaboration, people from different backgrounds analyze the case together and plan the way together.
Omri Gefen also illustrates this with two training managers from two organizations. At the coordination level they share plans and coordinate the use of a shared facility. At the cooperation level they organize a joint managers' conference and split the cost of a speaker from abroad. At the deep collaboration level they identify that the procurement and finance people in both organizations have similar characteristics and complementary capabilities, and they build a joint course together, a large investment that creates value neither of them would have reached alone.
The same logic applies to the interface between units of an organization around the customer. At the first level, information and actions are synchronized. At the second level, joint responses to customers are built through shared actions. And at the third level, a shared view of the customer value chain is built. Each level rests on a different mindset and yields different outputs.
How do you choose the right level of collaboration?
The model makes no claim that the best is at the top of the pyramid. The choice should stem from the value the partners want to create. Sometimes excellent coordination is entirely enough. Sometimes it misses a big opportunity. It is also possible to define one level for certain issues and another level for others, or one level for the short term and another for the long term.
In his work with senior management teams and in complex processes within and between organizations, Omri Gefen meets again and again partners who use the same words and mean different things. A simple conversation about which level they are aiming for saves months of disappointment. We expanded on how the actual level is measured in the article on the ECA model.
How to start in practice
Before defining a new collaboration, or when an existing interface is disappointing, it is worth asking.
Which level of collaboration am I aiming for in this interface, and which level is my partner aiming for? Have we checked?
Is what I call cooperation actually an exchange of information?
Does the value I am seeking require a higher level, or am I asking for more than is really needed?
Am I ready for the investment, dependence and risk that the higher level requires?
Frequently Asked Questions
What are the three levels of collaboration in the ECA model?
Coordination, in which information is shared and actions are synchronized; cooperation, in which parties act together around a defined task; and deep collaboration, in which strategic, long-term value is created together.
Is it always worth aiming for deep collaboration?
No. The level should match the value the partners want to create. Each level has a price in investment, dependence and risk, and sometimes good coordination is enough.
Why do partners become disappointed with each other?
Often because each side expected a different level of collaboration. Explicitly defining the level creates a shared language, trust and precision in the work.
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 want to define the right level of collaboration in your organization's interfaces, you are welcome to learn about Omri Gefen's way of working on the consulting page of the website.