Checklist
Make expertise visible so leadership can move
Distributed leadership requires an accessible map of expertise.
Before you use it
- Use when
- When a team repeatedly routes questions to the manager because members do not know who knows what.
Keep this limit in mind
- Autonomy must be bounded by competence, risk, compliance and recoverability. High-consequence decisions may need explicit approval gates.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Checklist
- List critical domains.
- Name primary and backup expertise.
- Update after major learning or ownership changes.
- Route questions to the closest expertise first.
Why it matters
Maintain a lightweight map of domains, current owners and backup expertise. Update it from actual work rather than titles.
An example
The team knows who owns BP relationships, credit data, DRF filters and cutover validation instead of asking one lead everything.
Check your result
Questions move to relevant expertise without the manager becoming a universal queue.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMake expertise visible so leadership can move
From this idea
This idea is useful withReturn credit with the ownership
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaRotate ownership where complexity benefits from shared leadership
Evidence and sources
A meta-analysis of 65 independent studies found team cognition positively related to team behavioral process, motivational states and performance, with moderation by task and team characteristics.
Shared cognition is not identical to unanimous opinion; teams may need differentiated expertise as well as common understanding.
The Cognitive Underpinnings of Effective Teamwork: A Meta-Analysis · Abstract
Edition and review
Version 0.1.0
No review details are supplied for this edition.