Principle
Share leadership around the work, not titles
Leadership can be a process distributed around expertise and need.
When it fits
- When a team has strong specialists but waits for the formal lead to initiate every problem-solving action.
When to avoid it
- Team-learning practices consume time. Use them where there is a real performance or coordination question, and do not substitute process rituals for domain expertise.
Why it matters
Make it normal for members to convene analysis, coordinate a response or lead a review inside their domain, while keeping formal accountabilities visible.
An example
The integration expert convenes a recovery huddle without waiting for the program lead, then returns the cross-workstream decision to the named owner.
Check your result
Leadership behavior is distributed where useful without creating multiple invisible decision owners.
Keep this limit in mind
- Team-learning practices consume time. Use them where there is a real performance or coordination question, and do not substitute process rituals for domain expertise.
Connected ideas
Useful withReview whether team learning changed the next cycle
Evidence and sources
Supports
A meta-analysis of 42 independent samples found a positive relationship between shared leadership and team effectiveness, with stronger relations in more complex work.
Shared leadership complements rather than automatically replaces formal accountability and may work differently across team designs.
A Meta-Analysis of Shared Leadership and Team Effectiveness · Abstract