Insight · Practice
Roles in a Leadership Tandem: Clarify Accountability, Power and Visibility
Shared accountability does not require identical work. It requires clear role domains, a deliberately shared core and an explicit view of power, visibility and organisational interfaces.
In short:
Shared accountability does not require identical work. It requires clear role domains, a deliberately shared core and an explicit view of power, visibility and organisational interfaces.
Where does my accountability end — and where does our shared accountability begin?
Role architecture
A practical way to structure the question
Clarify the mandate
Start with the shared purpose, not a task list.
Explore →
Lead domains
Make independent authority visible.
Explore →
Design overlap
Share only what genuinely benefits from two perspectives.
Explore →
Surface power
Make informal asymmetries discussable.
Explore →
Review roles
Adapt agreements as the work changes.
Explore →
01 · ROLE LOGIC
Separate mandate, role and task
Many tandems start with a task list: one person takes strategy, the other people; one leads clients, the other operations. That creates initial order, but it does not answer the deeper role question. Tasks change quickly. The shared mandate and accountability need to be more stable than the current to-do split.
The mandate describes the contribution the joint leadership is expected to make to the wider system. Roles describe accountability, authority and relationships. Tasks are concrete activities. When these levels are mixed, the result is either a rigid split or diffuse joint ownership in which both are responsible for everything and no one can act.
A robust role architecture therefore combines clear lead domains with a shared roof. It specifies not only who does the work, but who prepares decisions, who can decide, who can represent the other leader and which issues touch the shared mandate.
Shared accountability does not mean identical work. A tandem can have different role domains and still stand jointly behind the overall mandate.
02 · OVERLAP
Design the productive overlap
Complete separation sounds efficient but can create two neighbouring single-leader roles. Complete overlap sounds collaborative but can create duplication and permanent alignment. Between them is a deliberately designed overlap: the issues where two perspectives genuinely add value.
That overlap should be small enough for both leaders to act independently and large enough for shared accountability to remain real. Typical candidates include strategy, key people, major resource choices, crises and changes to the mandate. The exact boundary depends on context.
The key is that overlap should not be driven by anxiety. If both leaders attend everything because neither trusts representation, the problem is not a healthy shared space; it is a trust or mandate issue.
03 · POWER
Equal titles do not create equal power
Power does not come only from the organisation chart. Access to senior sponsors, budget control, expertise, tenure, networks, working time, personality and public visibility can make a formally equal dyad highly asymmetric. That asymmetry is not automatically harmful. When it remains invisible, however, it becomes difficult to govern.
A tandem should therefore discuss power sources as well as responsibilities. Who receives information first? Who is called spontaneously by important stakeholders? Who can make resource commitments in practice? Whose judgement is treated by the team as final? These questions are uncomfortable, but more precise than simply declaring both leaders ‘equal’.
Power asymmetry becomes particularly sensitive when it is tied to recognition. One person may present strategy and success while the other moderates conflict, secures handovers and keeps operations stable. Without deliberate visibility rules, an informal ranking can emerge.
- Who controls budget, information and access?
- Who is more often treated as the ‘real’ leader?
- Which invisible work keeps the tandem functioning?
- Where should visibility be shared deliberately?
05 · CHANGE
Treat roles as agreements that can be revised
A role architecture must be stable enough to orient people and flexible enough to respond to changing work. New projects, personnel changes or growing expertise can make an earlier split impractical. Renegotiation is therefore not evidence of failure; it is part of leading the system.
A review should ask more than whether both leaders completed their tasks. Does the distribution still fit the shared mandate? Are decisions located where expertise and accountability sit? Has power shifted? Has the shared core become too large or too small?
The possibility that a tandem ends belongs to the same logic. If roles move permanently apart or the shared mandate disappears, a clear redesign can be healthier than preserving a structure that is shared only symbolically.
Document roles as a testable agreement: lead domains, shared core, representation, interfaces, visibility and a review date.
04 · INTERFACES
The team needs a predictable interface
Teams test new structures. They ask the person from whom they expect support or approach the second leader after receiving an unwelcome answer. This is not always manipulation. Often the environment is simply trying to learn how the new system works.
Interfaces therefore belong inside the role architecture. Team members should know which leader leads which domain, when both are involved and how representation works. When the two leaders give different answers, they need a shared correction rather than a quiet competition for interpretive authority.
External stakeholders shape roles as well. If senior management, clients or HR consistently address only one person, formal equality is gradually hollowed out. The organisation has to support the architecture; the tandem cannot compensate indefinitely for structural contradictions around it.
- Clarify the mandate: Start with the shared purpose, not a task list.
- Lead domains: Make independent authority visible.
- Design overlap: Share only what genuinely benefits from two perspectives.
- Surface power: Make informal asymmetries discussable.
- Review roles: Adapt agreements as the work changes.
06 · EVIDENCE
Keep evidence and design choices distinct
Research on shared leadership supports the broader proposition that leadership contributions do not have to be concentrated in one individual. It does not establish one optimal role split for every formal tandem. Task, context and interdependence remain important.
The role and power analysis proposed here is therefore a practice architecture: it makes implicit expectations testable. The research contribution is orientation toward distributed leadership processes and team conditions; the actual allocation of domains, visibility and review rhythms must be treated as a hypothesis and tested in the specific system.
Research indicates: leadership contributions can be distributed. We infer: formal equality alone is insufficient. We recommend: making roles, power sources and interfaces explicit and reviewing them over time.
FAQ
Frequently asked questions
Answers to the most common questions about this topic.
Why is a task list not enough for role clarity?
Tasks change and say little about authority, representation, interfaces or shared accountability. Role design has to make those dimensions visible as well.
How can informal power asymmetry be recognised?
Look at access, budget, information advantage, visibility, networks, working time and whose judgement stakeholders treat as final in practice.
How much role overlap is healthy?
Enough to keep shared accountability real, but not so much that both leaders duplicate every task. The productive overlap depends on the actual interdependence of the role.
Understand first. Then design.
Clarify your role architecture
If titles are equal but accountability or power remains unclear in practice, an explicit role and interface review can be a useful next step.
Next step
Clarify your role architecture
If titles are equal but accountability or power remains unclear in practice, an explicit role and interface review can be a useful next step.
