Two modes of network orchestration
This is a shorter version of the newsletter. To get the full version with tips, follow-ups, and introductions of other members, subscribe to our mailing list:
There are two ways of managing (orchestrating) the network:
Dominating mode means that the manager makes decisions unilaterally. It doesn’t mean the manager does all the work, but rather that they define the “rules of the game” (governance principles) and often control the outcomes of collaboration.
Consensus-based mode means that while the manager may facilitate discussions, they have no more authority than any other member to make decisions.
Isn’t consensus-based mode always better?
Perhaps, but it’s not always feasible for large networks. Here’s why:
Harder to Maintain Agreement: As the number of partners grows, it becomes increasingly difficult to reach and sustain agreement among all parties, leading to inefficiency and potential conflict.
Less Clarity and More Free-Riding: With more partners, it becomes harder to identify each partner’s contribution clearly. This can lead to "free-riding," where some partners contribute less but still benefit from the collective work. As trust between partners weakens, informal governance methods, like relying on trust, become less effective.
Is dominating mode more effective for big networks then?
Only if your partners are very similar to each other (e.g., schools of similar size). When partners come from diverse backgrounds, they are less likely to trust a manager in dominating mode (the manager will lose legitimacy). Here’s why:
Orchestrators Lack Specialized Knowledge: When partners have different areas of expertise, the manager may know less than the participants in specific areas, as knowledge is spread across many experts.
Conflicting Objectives: When partners have different goals, any decision the manager makes will likely dissatisfy a significant portion of the group, leading to perceptions of unfairness or bias.
These issues are often addressed by rotating the role of the manager, but this becomes problematic in larger networks (10+ partners).
So, what should we do?
You need to constantly switch between these two modes. You may already be doing this out of necessity, but let’s aim to be more strategic about it.
At the beginning of a partnership, you'll likely need to spend more time in dominating mode, as partners don’t know each other well and rely on formal structures. For example:
The manager sets goals;
The manager assigns tasks;
The manager has partners sign formal contracts outlining their contributions.
As time passes and partners develop a shared vision and trust, you can spend more time in consensus-based mode. Here’s how that might look:
The manager allows members to deviate from set goals and renegotiate them together;
The manager permits members to select their own tasks;
Informal agreements may take place between partners without the manager’s direct involvement.
You will need to first create smaller teams in most cases though.
Are you stuck in one of these modes?
Although you'll spend more time in dominating mode at the beginning, both modes are necessary at every stage of collaboration—the balance just shifts over time:
I recommend integrating regular reflections about your role into your ongoing check-ups. Ideally, you should review progress on all ongoing projects monthly, either alone or with your team. (And if you don’t have such a regular review, here’s your sign to email me for tips!) As you go through each project, ask yourself:
What mode am I in for this project right now? Have I been in this mode for a while? Signs that you may be stuck in a suboptimal role include:
Difficulty reaching agreement;
Repeated discussions of the same issues;
Little or no action after decisions are made, or significant effort is required to ensure compliance;
Partners exhibit widely varying levels of enthusiasm and effort.
If I’m stuck in dominating mode, are there processes I can systematize and delegate to the team? If I’m in consensus-based mode, are there decisions that a single member could make, and can we rotate this role?
For patient readers, here’s a lengthy quote from a paper that describes how this switching process may look:
"In the network connections trajectory, orchestrators used connecting practices; they created andmade the connections between stakeholders visible. To create the initial connections, orchestrators first relied on dominating orchestration: they assigned participants to work packages and initiated encounters during the first face-to-face meetings. When initial connections were made and participants started carrying out the project proposal, orchestrators switched to consensus-based orchestration, because they lacked the formal authority to unilaterally divide the work. So, rather than assigning work to participants, orchestrators collaboratively discussed the tasks and motivated key contributors to take up an active role. When initial results were produced, orchestrators turned to dominating orchestration to have the reach to make these results visible and to connect stakeholders around opportunities to collaborate further. Finally, when the network opacity started to decrease, orchestrators switched back to consensus-based orchestration to ensure progress. They now relied on smaller, emergent teams that sourced experts across the collaboration to work on specific problems. In sum, over time, orchestrators worked to turn initially serendipitous encounters into meaningful connections. In so doing, they attempted to achieve network transparency."
References:
Reypens, C., Lievens, A., & Blazevic, V. (2021). Hybrid orchestration in multi-stakeholder innovation networks: Practices of mobilizing multiple, diverse stakeholders across organizational boundaries. Organization Studies, 42(1), 61-83. The full text is here.