Principle

Share leadership around the work, not titles

Leadership can be a process distributed around expertise and need.

About 1 min read

Before you use it

Use when
  • When a team has strong specialists but waits for the formal lead to initiate every problem-solving action.

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.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

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.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingShare leadership around the work, not titles

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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details