Co-Leadership Architecture
Shared Leadership in Practice: Four Examples
Examples are useful when they do more than celebrate success. What matters is the starting situation, the architecture, the critical moment, the repair and what others can learn from it.
In brief: Examples are useful when they do more than celebrate success. What matters is the starting situation, the architecture, the critical moment, the repair and what others can learn from it.
What can realistic cases teach without turning individual examples into a universal formula?
What matters here
Use a Work Sample, Not Only Interviews
This element is translated into the concrete context of “Shared Leadership in Practice: Four Examples” and linked to diagnosis, decision and a practical next step.
Use the First 90 Days as Activation
This element is translated into the concrete context of “Shared Leadership in Practice: Four Examples” and linked to diagnosis, decision and a practical next step.
Conflict, Repair and Continuity
This element is translated into the concrete context of “Shared Leadership in Practice: Four Examples” and linked to diagnosis, decision and a practical next step.
Practice lens
From the idea to practical application
Starting situation
Begin each case with the problem before the solution. What task, dependency or constraint made a different leadership architecture worth considering? Without that context, readers cannot judge whether the same design would travel to their setting.
Architecture choice
Show the concrete design choice: shared role, lead domains, time model or decision rule. The useful part of a case is not the label “shared leadership” but how accountability and authority were arranged.
Tension
Include friction. Which expectation collided, which decision slowed down or which stakeholder bypassed the model? Tension reveals the assumption that the original design failed to handle.
Adjustment
Describe the change made in response to the observed problem — perhaps narrowing a joint decision space, formalising a handover or involving a sponsor differently. This makes learning visible rather than smoothing the case into a success story.
Learning
Avoid lessons such as “communication matters”. State the mechanism that might transfer and the context boundary that may prevent transfer. Examples then become thinking tools rather than evidence that one model always works.
Mental model
A practical way to structure the question
Starting situation
Starting point
Explore →
Architecture choice
Test
Explore →
Tension
Design
Explore →
Adjustment
Stress-test
Explore →
Learning
Learn
Explore →
FAQ
Frequently asked questions
Answers to the most common questions about this topic.
What can practice examples legitimately teach us?
They can illustrate mechanisms, trade-offs and typical tensions. They do not prove that the same model will produce the same result in another organisation.
What should you compare across cases?
Look at task, mandate, power distribution, decision logic, organisational support and the problem the model was intended to solve.
Why should useful examples include difficulties as well as successes?
Because credibility comes from showing how tensions were recognised, rules were adapted and impact was reviewed — not from presenting shared leadership as friction-free.
Understand first. Then design.
Discuss your own situation
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
Discuss your own situation
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.