Chapter III.1 · Structure
Co-Management and Shared Leadership: How to Make Co-CEO Structures Work
Two leaders, complementary strengths, stronger together: the design rarely survives contact with pressure unless decision rights and escalation are explicit. Lessons from Rome to Microsoft.
Key takeaways
- Co-management raises the need for leadership clarity rather than reducing it.
- Most co-leadership tension is structural, not personal: slower decisions, contested accountability and conflicting signals to direct reports.
- The arrangements that work defined decision rights and an escalation path explicitly, before pressure arrived.
- Trust between co-leaders needs deliberate practice, such as arguing each other’s positions.
- The most common failure is assuming shared values make explicit governance unnecessary.
On this page
El Hassane Ben Ahmed has worked inside and alongside co-management structures at different points in his career. Each time, the initial framing was the same: two leaders, complementary capabilities, stronger together. And each time, what actually played out was more complicated than the design suggested.
Good intentions rarely caused the tension, he writes in Chapter III.1 of The Lessons That Stayed. The source was structural. Decisions requiring agreement slowed down. Accountability became contested. Direct reports received conflicting signals.
“Co-management does not reduce the need for leadership. It raises it. The standard of clarity required to make shared authority functional is higher, not lower, than the standard required for individual leadership.”
Why organisations choose shared leadership
Co-management at executive level is increasingly common. Organisations adopt it to handle complexity, to combine complementary expertise, and to share the load of leading at scale. It takes many forms: formal co-CEO structures, joint venture leadership teams, and the growing practice of co-leading major programmes with explicitly shared authority.
The model that worked
What Procter and Gamble understood as business instinct, governance research has since confirmed: the arrangements that work are those where the governance design was explicit before the pressure came.
The governance of shared authority
Robert Monks and Nell Minow argue that accountability is only meaningful when there is a direct, transparent link between authority, responsibility and consequence. Shared leadership puts pressure on every part of that link.
Decision rights are the foundation
Michael Jensen and William Meckling argue that any organisational structure works only when decision rights are aligned with knowledge and incentives. In practice, that means each co-leader should own the decisions where they have the best information and bear the consequences.
The escalation deficit
When two leaders disagree and there is no defined way to resolve it, the disagreement grows. Research by Afzalur Rahim finds that the absence of a defined escalation path strongly predicts conflict escalation. The worst time to design that path is during the conflict it is meant to resolve.
The psychology of shared authority
Structure is necessary but not sufficient. Co-management also depends on trust between the co-leaders: trust in each other’s competence, intentions and reliability.
Amy Edmondson’s concept of psychological safety applies to a pair of co-leaders as much as to a team. If either one feels it is risky to disagree openly with the other, disagreements go underground, and teams start receiving two different versions of the leadership’s intent.
Common failure modes
- Assuming shared values make explicit governance unnecessary. This is the single most common failure. Alignment on strategy does not settle who decides what on a Tuesday afternoon.
- Waiting until stakes are high. Samuel Bacharach and Edward Lawler documented that authority conflicts become much harder to resolve as their stakes rise.
- Sending mixed signals. Direct reports quickly learn which co-leader to ask for which answer, and the organisation splits along that line.
- Never revisiting the design. Circumstances change. A framework that fitted the first year may not fit the third.
A framework for designing co-management
- Map decision rights before you begin. List the major categories of decisions and assign each one: leader A, leader B, or joint. For joint decisions, define what “agreement” means.
- Define the escalation path. Decide in advance what happens when you disagree: a time limit, a tie-breaker, a board member or a neutral adviser.
- Agree on how you communicate. Resolve disagreements in private. Present decisions jointly once made. Decide who speaks on which subjects.
- Practise disagreement deliberately. Borrow the Wright brothers’ habit and argue each other’s positions on important decisions.
- Review the framework regularly. Chris Argyris and Donald Schön argue that lasting effectiveness requires questioning the frameworks themselves, not only correcting errors within them. Schedule that review.
Clarity as the foundation
The Roman consulship lasted five centuries not because it always worked, but because, when it worked, it worked through clarity. From the Republic to the Wright brothers’ workshop in Dayton, from a Cincinnati soap factory to a Microsoft boardroom, the lesson is the same: the co-leadership arrangements that work are almost always those where the hard conversations happened early.
“Clarity, in the end, is not what makes shared leadership comfortable. It’s what makes it sustainable.”
Frequently asked questions
Do co-CEO structures work?
They can, when the governance is designed explicitly: who decides what, how disagreements are escalated, and how accountability is shared. They fail most often when authority is left implicit because the co-leaders assume their shared values will be enough.
What are decision rights?
A clear statement of which person or body has the authority to make which decisions. Research by Michael Jensen and William Meckling shows that structures work when decision rights are aligned with the knowledge and incentives of the people holding them.
What should co-leaders agree on before they start?
A written map of decision rights, a defined escalation path for disagreements, how they will present decisions to their teams, and a regular review of whether the framework still fits.
How do co-leaders avoid sending mixed messages?
By agreeing which of them speaks on which subjects, resolving disagreements privately before communicating, and presenting decisions as joint once they are made.
Sources
This essay is adapted from Chapter III.1 of The Lessons That Stayed by El Hassane Ben Ahmed (2026). Quotations are from the book.
- Monks, R.A.G. and Minow, N. (2011) Corporate Governance
- Jensen, M.C. and Meckling, W.H. (1992) ‘Specific and general knowledge, and organizational structure’
- Rahim, M.A. (2002) ‘Toward a theory of managing organizational conflict’, International Journal of Conflict Management
- Edmondson, A.C. (2019) The Fearless Organization
- Bacharach, S.B. and Lawler, E.J. (1980) Power and Politics in Organizations
- Argyris, C. and Schön, D.A. (1978) Organisational Learning
