In 2001, W.L. Gore (the company behind Gore-Tex) had over 6,000 employees, no traditional managers, and had appeared on Fortune’s “Best Companies to Work For” list every single year since the list started. Their model was built on what founder Bill Gore called a “lattice organization,” where leadership wasn’t a title but a behavior. Anyone could lead a project. Authority came from earning the respect of colleagues, not from being appointed.
That sounds idealistic. But W.L. Gore has now been profitable for over 60 consecutive years. The model works because it matches leadership to the person with the most relevant expertise for each situation, rather than defaulting to whoever holds the highest title.
That’s the core of shared leadership: distributing decision-making across a team instead of concentrating it in one role.
What Shared Leadership Actually Looks Like
Shared leadership isn’t a vague philosophy about “teamwork.” It’s a structural decision about where authority sits.
In a traditional hierarchy, decisions flow up. A team member identifies a problem, brings it to their manager, the manager evaluates options, makes the call, and pushes the decision back down. The bottleneck is obvious: every decision depends on one person’s bandwidth and judgment.
In a shared leadership model, the person closest to the problem makes the decision. The manager’s role shifts from gatekeeper to enabler. They set the boundaries (budget, timeline, quality standards), then get out of the way.
Multiple meta-analyses in the Journal of Applied Psychology have found that shared leadership predicts team performance over and above traditional vertical leadership. The effect is strongest in teams doing complex, knowledge-intensive work, where no single leader can hold all the context needed for good decisions. And the demand for collaborative skills keeps growing: HBR’s 2025 analysis found that employers have tripled job postings requiring collaboration and influence skills since 2007.
If you’re exploring leadership models, collaborative leadership sits in a related space. The difference is that collaborative leadership emphasizes input from everyone while the designated leader still makes the final call. Shared leadership takes it further by rotating who actually holds decision-making authority.
5 Reasons Shared Leadership Works for Managers
This might seem counterintuitive. Why would a manager benefit from giving away power? Because “power” in management is a misleading frame. What actually matters is outcomes.
1. Decisions get made faster (and better)
When every decision routes through a single manager, that manager becomes the constraint on the team’s speed. Shared leadership removes that bottleneck.
Spotify built their entire engineering organization around this principle. Their “squad model” gives small, cross-functional teams full ownership over a feature area. Product decisions happen inside the squad, not in a chain of approval meetings. The squad’s product owner sets priorities, but technical decisions belong to the engineers doing the work.
The result isn’t chaos. Spotify ships product updates continuously. Each squad moves at its own pace without waiting for centralized approval.
2. Your team develops faster
One of the most persistent complaints from high-performers is that they don’t get enough opportunity to lead. Shared leadership creates those opportunities by design, not as a special favor.
When team members regularly make real decisions (ones with consequences, not just input that a manager might ignore), they develop leadership skills faster than any training program could produce. They learn to weigh trade-offs and live with imperfect choices. That’s leadership development on the job, every week, without a workshop.
3. You stop being the single point of failure
If your team can’t function when you’re on vacation, that’s not loyalty. That’s a structural problem. Shared leadership distributes the knowledge and decision-making capacity that would otherwise live solely in the manager’s head.
Buurtzorg, a Dutch home healthcare organization, provides a striking example. Their 15,000+ nurses operate in self-managed teams of 10-12, with no team managers at all. Each team handles its own scheduling, hiring, and patient care decisions. The organization has just 50 administrative staff for the entire company. When one nurse is absent, the team adapts without missing a beat because no single person holds all the context.
4. Conflict becomes productive instead of political
In traditional hierarchies, conflict often becomes about access to the manager’s ear. Who can convince the boss? In shared leadership, conflict resolves closer to where it originates because the people involved have actual authority to work it out.
This doesn’t mean conflict disappears. It means it shifts from political maneuvering (“let’s escalate this to the manager and let them decide”) to substantive debate (“we disagree about the right approach, so let’s work through the trade-offs together”). That’s a fundamentally healthier dynamic. Organizational behavior research consistently shows that task-focused conflict in teams with distributed authority leads to better outcomes than in teams where conflict just gets escalated.
5. You get to focus on what only you can do
Most managers spend a disproportionate amount of time on decisions that someone else on their team could make just as well (or better). Shared leadership reclaims that time.
When your team handles day-to-day decisions, you can focus on cross-team collaboration, strategic planning, stakeholder management, and developing the team’s collective capabilities. Those are the activities that actually require a manager’s position and perspective. Everything else is better handled by the person closest to the work.
The Real Downsides (and When to Be Cautious)
Shared leadership isn’t a universal solution. Knowing where it breaks is just as important as knowing where it works.
Speed in crisis. When the building is on fire (literally or metaphorically), you need one clear decision-maker. Shared leadership thrives in complex, ongoing work. It struggles in emergencies that demand immediate, centralized authority. The military uses distributed command in the field but centralized command for strategic decisions. The same principle applies to your team.
Uneven skill levels. Shared leadership assumes team members have enough expertise to make good decisions in their domain. A team of mostly junior members without enough experience to evaluate trade-offs will struggle with distributed authority. You need to build capability before distributing power.
Accountability is the most common failure mode. When “everyone leads,” no one feels personally responsible for outcomes. W.L. Gore handles this by assigning “commitments” to specific people, so authority is shared but accountability is always named. Without that clarity, shared leadership drifts into shared avoidance.
A related problem is social loafing. Shared leadership can enable free-riding when team members aren’t equally invested. If two people carry the decision-making load while three others coast, the model breaks down quietly.
How to Practice Shared Leadership With Your Team
Moving from traditional management to shared leadership doesn’t happen in a single announcement. It’s a gradual shift that requires deliberate practice.
Start with low-stakes decisions
Don’t begin by sharing authority over your team’s biggest project. Start with decisions where the cost of a wrong call is low: how to structure a retrospective, which tool to use for a specific task, how to handle an internal process improvement.
This lets team members build decision-making confidence while you build trust in the model.
Define the boundaries clearly
Shared leadership fails when the boundaries are ambiguous. Be explicit about what’s in scope and what’s not.
A useful framework: “You own the decision on anything within [these parameters]. If it goes beyond [these constraints], bring it to me.” The parameters might be budget thresholds, timelines, or impact on other teams. The point is that delegation of authority only works when the authority’s limits are clear to everyone.
Match authority to expertise
The person leading any given initiative should be the person with the most relevant knowledge, not the most seniority. This is what makes shared leadership fundamentally different from simply rotating a “team lead” title.
On a product team, the designer might lead user research decisions, the engineer might lead technical architecture decisions, and the product manager might lead prioritization decisions. Authority follows expertise, not hierarchy.
Build feedback loops
Shared leadership without feedback is just abdication. You need regular check-ins where the team reflects on decisions made, what worked, what didn’t, and what they’d do differently.
This isn’t micromanagement. It’s learning infrastructure. The feedback loops help the team calibrate their judgment over time and help you identify when someone needs more support or when a boundary needs adjusting.
Name accountability explicitly
For every decision or initiative, one person should be clearly accountable for the outcome. Shared leadership distributes the act of leading, but it doesn’t mean responsibility is diffused into a collective fog.
Use a simple structure: “Who owns this?” If nobody can answer that question in under five seconds, the shared leadership model has a hole that needs patching.
A Coaching Observation
One pattern that shows up consistently in coaching conversations about shared leadership: managers intellectually agree that distributing authority makes sense, but they struggle to let go of decisions they’ve always owned. The pull to “just handle it myself” is strong, especially when you know you could make the call faster than explaining the context to someone else.
That pull is the exact habit that shared leadership requires you to override. Every time you make a decision your team member could have made, you’re optimizing for today’s speed at the cost of tomorrow’s capability. The short-term feels efficient. The long-term cost is a team that never learns to operate without you.
If you find yourself consistently taking back decisions you’ve shared, that’s a signal worth examining. Try working through it with Merlin, who can help you identify which decisions you’re holding onto and why, and build a realistic plan for releasing them one at a time.
Moving Forward
Shared leadership won’t fix a team that has deeper trust issues, unclear goals, or the wrong people. But for a team that has the raw capability and needs more room to use it, distributing leadership can be the structural change that unlocks the next level of performance.
Start small. Pick one category of decisions to hand off this week. Define the boundaries. Let your team make the call. Watch what happens. Adjust. Repeat.
You’re still leading. You’re just building a team where everyone else does too.
FAQs
What is the difference between shared leadership and delegating tasks?
Delegation gives someone a task while the manager retains decision-making authority. Shared leadership goes further by distributing actual decision-making power. A delegated task might be “redesign this onboarding flow.” Shared leadership would mean the team member decides whether to redesign the onboarding flow in the first place, owns the strategy behind it, and calls the final shot on the approach. The distinction matters because delegation still concentrates authority in one person.
Does shared leadership mean no one is in charge?
No. Shared leadership doesn’t eliminate hierarchy or accountability. Someone still owns the outcomes. The shift is that leadership functions (making decisions, setting direction, solving problems) rotate based on who has the most relevant expertise for a given situation. W.L. Gore still has a CEO. Spotify squads still have product owners. The structure exists, but authority moves to where the knowledge lives.
When should you avoid shared leadership?
Shared leadership works poorly in crisis situations that demand fast, centralized decisions (think emergency response or critical system outages). It also struggles with teams of mostly junior members who lack the experience to make informed decisions independently. And it breaks down when team members don’t trust each other enough to share authority honestly. If your team has unresolved interpersonal conflict, fix that before distributing leadership.
How do you measure whether shared leadership is working?
Watch decision velocity (are decisions happening faster or slower?), engagement (are more people contributing in meetings, or are the same two voices still dominating?), and retention (shared leadership done well tends to reduce turnover because people feel more ownership over their work). If decision-making slows to a crawl or conflict increases without resolution, pull back and diagnose what’s breaking.