Collaboration & Trust |
Transforming Leadership

The CCO (Chief Collaboration Officer) role is a senior management role that leads the collaboration and relevance of the organization, internally and with other organizations. Omri Gefen estimates that within a few years such a function will exist in every organization, and that it will become a profession and a discipline in its own right. In his view, for the role to truly change the organization, it must be a separate role, connected to strategy and reporting directly to the head of the organization.

This article is based on the book "The Power of Collaboration: From Ego-System to Eco-System" by Omri Gefen, in which he devotes an entire chapter to what he calls the profession of the future, and sets out the first condition for its success: "If the issue of collaboration is to be taken seriously, a senior manager should be appointed for the job."

What is a CCO and why is such a role needed?

Omri Gefen describes a reality in which many professions are about to disappear and a new profession is likely to emerge: the manager of collaboration and opportunities. The letter C can also stand for community or for chance management, and all of them relate directly to collaboration, inside and outside the organization. He recommends avoiding titles such as "senior collaborator" and choosing "VP of collaboration", "partnership leader" or simply CCO, like the familiar CEO and CFO.

The reason for the role is simple. Reality demands that the whole field of collaboration and partnerships be professionalized. In many systems managers already do part of the work, and are expected to improve collaboration with their colleagues. But someone who sees the whole picture and leads professional processes in the field is still missing. Managers themselves do not always have the time and resources to devote themselves to this.

Whoever is appointed to the role should be an expert in the field, able to focus on the subject with a systemic view and an understanding of the eco-system. Not another project manager coordinating between units, but someone who sees the organization as part of a wider system and understands that its relevance depends on the connections it creates.

What does the CCO role include?

According to Omri Gefen, the role includes a wide range of responsibilities. Orderly and professional construction of interfaces and collaborations within the organization and with other systems. Professional and preventive treatment of problematic interfaces and releasing stuck nodes. Embedding a shared language and a collaborative organizational culture, along with orderly methodologies and measurement. Conflict management, accompanying managers in managing interfaces and crises, and accompanying external negotiation processes.

Alongside this, the role looks ahead. The CCO identifies strategic opportunities for collaboration and partnerships in order to strengthen the organization's relevance, helps decide whether to enter a partnership, manages communities and sharing networks, and connects the organization to a network of similar role holders in other organizations.

Omri Gefen asks the reader to imagine this network: "Imagine a group of senior government officials who use one language and one unified work model." When barriers arise between ministries, they are the ones who sit together, release the blockages and improve work processes. In his words, such a vision would transform the field, and the power of the network created is a goal in itself.

Why not add the role to an existing manager?

This question comes up in almost every organization. The natural candidate is the human resources manager, who should have many of the required capabilities: understanding of processes, interpersonal skills and evaluation tools. Other candidates are the Chief Information Officer, who should have a broad view of interfaces, or the Chief Operating Officer.

Omri Gefen answers clearly: "Integrating this function with an existing role will not allow for adaptive change." At best, collaboration will receive a secondary place relative to the role holder's main focus. He points out that this was true in other fields as well. Today it is clear to us that the operations manager is not responsible for quality assurance, and that a CEO does not run human resources personally. The same clarity, he estimates, will come to the CCO role. And in very large organizations there will be a whole team.

How do you train a CCO?

Even if in the coming years the role is combined with other roles, it will require dedicated training. Omri Gefen details what it includes: professional models of collaboration, community management, tools of integrative negotiation and mediation, managing dialogue processes and consensus building, using social networks, running discussions and meetings, and a deep understanding of innovation and opportunity management. He estimates that in the future CCO training will become an academic track at universities.

Omri Gefen adds that this body of knowledge will expand and deepen over the years, and that decision makers will gradually understand that this is a profession and a discipline in its own right. This is exactly the process other fields went through: a clear definition, differentiation in tools and training, and clear positioning in the system.

Defining the role can also restore relevance to existing roles that were built on old-world conceptions. Omri Gefen gives the example of the inspector at the Ministry of Education. The very title reflects an old mindset. The right definition, he says, is "collaboration leaders": people who connect schools, formal and informal education, education and community, and the system and parents.

In his work with senior management teams and in complex processes within and between organizations, Omri Gefen meets the same gap again and again: everyone agrees collaboration is important, but no one is really responsible for it. The CCO role is the structural answer to this gap. It is close in spirit to the "Glue and Oil" consultant we described in the article on organizational consulting, but as a permanent senior role inside the organization.

How to start in practice

Before appointing a CCO, or deciding there is no need, it is worth pausing to ask.

Who in my organization is responsible today for the quality of interfaces between units? Is the answer "everyone", meaning no one?

How many stuck nodes do we have that no one is authorized to release?

Am I trying to add collaboration to an existing role to save money, and what is the price of that?

Who in the organization is already doing this work informally, and perhaps needs to be given a title, authority and tools?

And which collaboration opportunity, inside or outside the organization, are we missing right now simply because no one's job is to identify it?

Frequently Asked Questions

What is a CCO?

A CCO (Chief Collaboration Officer) is a senior collaboration manager who leads the organization's collaborations, internally and with other organizations. Omri Gefen sees it as the profession of the future in this field.

To whom should the CCO report?

Directly to the head of the organization. According to Omri Gefen, for the role to be effective it must be senior and connected to strategy.

Can the human resources manager fill the CCO role?

They have many of the required capabilities, but Omri Gefen warns that combining the function with an existing role will not allow a paradigm shift, and collaboration will receive a secondary place.

What training does a CCO need?

Models of collaboration, integrative negotiation and mediation, managing dialogue and consensus building, managing communities and networks, and managing innovation and opportunities.

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).

Organizations considering defining a collaboration manager role are welcome to learn about Omri Gefen's way of working on the consulting page of the website.

Leave a Reply

Your email address will not be published. Required fields are marked *