Organizational structure change to strengthen collaboration is adjusting the structure, the connecting units and the leadership roles so that they encourage joint work between units instead of separating them. Omri Gefen notes that this is sometimes the most effective lever, but even when the whole structure cannot be changed, structural solutions can be built within the existing framework. Cisco is an example of an organization that adjusts its structure continuously.
This article is based on the book "The Power of Collaboration: From Ego-System to Eco-System" by Omri Gefen, in which he writes: "Sometimes structural change is the most effective leverage", and immediately adds that interesting solutions can be formed within the existing framework too.
What can the Cisco case teach about organizational structure change?
Until 2001 Cisco's structure was organized by customer types, and later it changed to a technology-focused structure. The main concern was internal centralization and growing distance from customers. The solution was to set up a central marketing organization that connected the technology groups with the customer-oriented sales units, and supported the integration of products and technologies.
In addition, senior managers were appointed as "champions" of strategic customers, including CEO John Chambers, who was defined as Ford's champion. In 2004 the company went a step further and created cross-organizational leadership groups that brought the "voice of the customer" into critical processes. Omri Gefen describes Cisco as an organization in constant evolution of collaborative solutions, adapting to a changing arena.
How do you change structure without changing the whole structure?
It is not always possible to change the organizational structure. Omri Gefen gives an example from a process at Maccabi Healthcare Services, in which a hackathon was held to develop collaborative solutions from the field. The group selected came up with the "houses": six houses, each including sub-units from several districts. They worked to advance shared professional objectives, and the structure was defined in advance as temporary, in order to remove the walls that had formed between the five districts.
Another example comes from a leading organization in the defense industry whose challenges reached a level that no single division could address alone. A forum of research and development leaders was established. The R&D Vice President described the starting point: "Joint research and development between divisions has been an obscene word for years. Throughout the years this muscle was nonexistent. It’s like taking a bone from your own flesh and putting it elsewhere." The process emphasized trust and transparency. Participants mapped all core technologies, created knowledge communities, and later set up central laboratories with joint work plans and new solutions for customers.
What can structure not do on its own?
A new structure without a suitable culture may produce the same problems in a different form. Omri Gefen notes that a matrix structure, for example, is meant to address the separation between silos, but sometimes creates dual management, power struggles and ambiguity. Implementing it successfully requires a collaborative culture and a high ability among managers to hold dialogue and build agreements. We expanded on developing these capabilities among managers in the article on management development.
In his work with senior management teams and in complex processes within and between organizations, Omri Gefen sees that structural change succeeds when it is combined with trust, a shared language and personal connections. In the defense industry example, the business models were built alongside personal connections. Not instead of them. Structure opens a door. People still have to walk through it.
How to start in practice
Before drawing a new organizational chart, it is worth asking.
Which wall in the current structure costs us the most, and between whom does it stand?
Do we have a connecting structure, such as a forum, a champion or a temporary team, that can start taking it down right now?
Which "bones from my own flesh" am I unwilling to move, and why?
And do we have the trust, the language and the managers that will allow the new structure to really work?
Frequently Asked Questions
Is organizational structure change enough to strengthen collaboration?
No. Omri Gefen notes that it can be the most effective lever, but it must be combined with a collaborative culture, trust and a shared language.
What did Cisco do to strengthen collaboration?
It set up a central marketing organization connecting the technology groups and the sales units, appointed senior managers as customer champions, and created cross-organizational leadership groups.
Can structure be changed without a full reorganization?
Yes. Temporary structures, cross-division forums and connecting structures can be created within the existing framework, like the "houses" at Maccabi Healthcare Services.
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 a structural change to strengthen collaboration between units are welcome to learn about Omri Gefen's way of working on the consulting page of the website.