Co-Leadership Architecture
Shared Leadership in Practice: How Two People Lead Together
In everyday work, shared leadership is not defined by a job title. It is defined by handovers, decisions, representation, visibility and whether the surrounding organisation knows how to work with the tandem.
In brief: In everyday work, shared leadership is not defined by a job title. It is defined by handovers, decisions, representation, visibility and whether the surrounding organisation knows how to work with the tandem.
How do two leaders become one coherent and actionable leadership system?
What matters here
Beyond the Lone-Leader Myth
This element is translated into the concrete context of “Shared Leadership in Practice: How Two People Lead Together” and linked to diagnosis, decision and a practical next step.
When Two Leaders Add Value
This element is translated into the concrete context of “Shared Leadership in Practice: How Two People Lead Together” and linked to diagnosis, decision and a practical next step.
Create a Shared Mandate
This element is translated into the concrete context of “Shared Leadership in Practice: How Two People Lead Together” and linked to diagnosis, decision and a practical next step.
Mental model
A practical way to structure the question
Shared mandate
Starting point
Explore →
Role domains
Test
Explore →
Decision rights
Design
Explore →
Operating rhythm
Stress-test
Explore →
Shared accountability
Learn
Explore →
Building block 03
Create a Shared Mandate
“We are jointly responsible” sounds clear until the first difficult decision arrives. A shared mandate has to explain why the dyad exists, what result it owns, what tensions it is expected to hold, and where its authority begins and ends. Without that clarity, each leader can build a plausible but different picture of success. The pair then appears aligned while actually optimising for different priorities.
A useful architecture distinguishes mandate, role and task. The mandate defines the contribution the shared leadership system is expected to make to the wider organisation. The role describes responsibility, authority and key relationships. Tasks are the concrete activities that can change and move between people. Splitting tasks without a shared mandate produces two neighbouring jobs; a grand purpose without rights and roles produces shared responsibility without the power to act.
Building block 06
Build an Operating System
The operating system should evolve. New tandems often need more overlap and more explicit coordination. As trust and shared context grow, the amount of synchronous work can decrease. A mature tandem is not one that talks constantly; it is one that can remain coherent while allowing each person enough autonomy to create real additional capacity.
A co-leadership operating system is made of routines, not intentions. The pair needs a small set of reliable practices for synchronisation, information flow, stakeholder management and review. If both leaders must attend everything in order to stay aligned, the system is inefficient. If they rarely overlap, the shared picture decays. The operating system defines what must be synchronised and what can safely diverge.
- Which assumption in this part of “Shared Leadership in Practice: How Two People Lead Together” needs to be tested explicitly?
- Which agreement should become different or clearer afterwards?
- What would show in daily work that the agreement is holding?
Practice lens
From the idea to practical application
Shared mandate
Write the mandate so that either leader can explain the same priorities independently. “We jointly lead the function” is not enough; the pair needs a shared account of what it is responsible for and which trade-offs it is authorised to resolve.
Role domains
Define domains as combinations of accountability, authority and interfaces rather than task lists. This allows one person to lead without removing the other from overall accountability, while still giving the team a predictable first point of contact.
Decision rights
Assign recurring decisions to modes: autonomous, consultative or genuinely joint. A useful rule lets a real case be classified quickly; a long matrix that still requires negotiation on every decision has not created clarity.
Operating rhythm
Synchronise where dependencies require it. Short routines for decisions, risks and handovers often outperform constant joint attendance. The purpose of rhythm is to preserve a shared system without processing every piece of information twice.
Shared accountability
Shared accountability becomes visible when something goes wrong. Different lead domains should not become an excuse to retreat into “your area” and “my area”. The pair can distribute authority and still stand jointly behind the architecture it agreed.
FAQ
Frequently asked questions
Answers to the most common questions about this topic.
What is the difference between splitting tasks and sharing accountability?
Tasks can be divided. Shared accountability additionally means both leaders stand behind a common mandate and selected outcomes, without doing every activity together.
How can a tandem avoid duplicated work?
Use lead domains, explicit handovers and a deliberately limited shared core. Joint time should be reserved for work where two perspectives genuinely add value.
Do both leaders need to present the same opinion externally?
Not during internal deliberation. Once a legitimate decision has been made, however, stakeholders need clarity about what applies and who carries implementation responsibility.
Amrit Rescheneder · Reviewed: 23 August 2026 · Methodology & evidence standard
Understand first. Then design.
Explore tandem models
If you do not want to force your situation into a standard model, we start with the concrete leadership question and decide from there what the next useful step is.
Next step
Explore tandem models
If you do not want to force your situation into a standard model, we start with the concrete leadership question and decide from there what the next useful step is.