By Andreas Pettersson, Founder, Leaders ADAPT
For seven years I ran a company that did not fully belong to me. A global manufacturer owned it. A second company had a stake and a technology relationship. My teams sat in Europe, Japan, and the US, and half the people whose decisions shaped my week did not report to me and never would.
The textbooks do not call that a leadership style. It is the daily reality of most executives, and it has a name: the collaborative leadership style, what you use when the org chart gives you responsibility for an outcome and no authority over the people who deliver it.
Quick answer: The collaborative leadership style is an approach in which leaders from different teams, functions, or organizations share responsibility for a decision and its outcome rather than one leader directing the rest. It relies on shared goals, mutual accountability, and trust instead of positional authority. It suits cross-functional projects, partnerships, and alliances, and it fails when no single person is named to make the final call.
What is collaborative leadership?
Collaborative leadership is a leadership style in which the people leading a piece of work share ownership of the decisions and the results across team, functional, or organizational lines, without one leader holding authority over the others.
Herminia Ibarra and Morten Hansen, writing in Harvard Business Review in 2011, described the collaborative leader's core capacity as engaging people and groups outside your formal control and inspiring them to work toward a common goal. That phrase, outside your formal control, is the whole definition. Inside your own team, involving people in decisions is participative leadership. Across the boundary, where nobody reports to anybody, it becomes collaborative.
The style shows up in four places: cross-functional projects where product, sales, and operations each own a piece; partnerships between companies and their stakeholders; joint ventures and corporate-owned subsidiaries; and any leadership team where the CEO wants peers to run the business together rather than through her.
Collaborative versus participative leadership: what is the difference?
The two get confused because both involve more people in decisions. They solve different problems.
| Participative leadership | Collaborative leadership | |
|---|---|---|
| Where it operates | Inside one team, under one leader | Across teams, functions, or organizations |
| Who gives input | The leader's own people | Peers who do not report to each other |
| Who decides | The leader, after input | Shared decision-making: a named decider agreed by the group, or the group by consensus |
| Who owns the outcome | The leader | Shared, with one accountable name |
| What it runs on | The leader's invitation | Trust between equals and a shared goal |
The participative leadership style is a leader's choice about how much input to collect. Collaborative leadership is not a choice. It is the only style available when you have to move people you cannot instruct, which is why most advice about it is thin: it describes the atmosphere and skips the mechanics.
Characteristics of a collaborative leader
Five things I look for in the executives I coach.
- They lead with the why. A decision handed across a boundary without its reasoning reads as a demand. With the reasoning attached, it reads as an invitation. My rule in the chair was to always lead with the why, including when the news was bad.
- They separate the problem from the person. In the culture I ran, the person who raised the red flag and admitted a mistake was theirs was celebrated for speaking up. Collaboration dies the first time a partner gets blamed for surfacing a problem.
- They place people by what they are good at. Some people are starters, some are system thinkers, and a rare few are both. Most are excellent at one part of a process and should be placed there rather than resented for the rest.
- They get the real buy-in, not the easy one.
- They name a decider. Shared leadership does not mean nobody decides. It means the group agrees in advance who does.
A collaborative leadership example: refusing the easy close
An example from my advisory work, with the client described only by role. I was presenting a company-wide change program to its sponsors. Halfway through, the sponsors said they were already sold. The easy move was to close.
I asked instead whether they could sign off alone or needed approval above them. They wanted the CEO's stamp. So rather than take the yes in the room, I set another meeting to present the strategy to the CEO and the directors myself.
The reason is the core of collaborative leadership. If you want leadership to drive a change, the buy-in has to come from the people who will be asked to defend it, not from the people who like it. A rollout sponsored by one function reads to the rest of the organization as that function's project, and people sense the missing alignment instantly and resist.
Getting the real yes cost me an extra meeting. Skipping it would have cost the program.
The same logic runs the rollout itself. Train small groups first, watch for the people who get excited and good fast, the organic champions, and let their early wins build peer credibility before you widen the circle. Collaboration spreads through people who chose it, not through a memo.
The trust collaborative leadership runs on
You cannot instruct peers, so you have to be trusted by them. Trust across a boundary is not a feeling. In The Trust Protocol, a system I wrote for leaders rebuilding trust with teams, partners, and investors, it is a response to five signals, and the rule is unforgiving: four out of five equals zero trust.
| Loop | What the other side is asking | What breaks it | The fix |
|---|---|---|---|
| Transparency | Do I understand why? | Decisions without reasoning | "Because" plus the real reason, every time |
| Reliability | Do you do what you say? | Words and actions drifting apart | Smaller promises, delivered every time |
| Understanding | Do you see my reality? | Requests that ignore my constraints | State their constraints before your ask |
| Safety | Can I tell you the truth? | Punished honesty, shot messengers | Thank disagreement, reward bad news |
| Track record | Do you deliver? | No visible progress | Small wins, communicated |
When a partner goes quiet, a peer function works around you, or a joint decision keeps getting reopened, one of those five loops is broken. Fix the loop. Another workshop on collaboration will not touch it.
Where the collaborative leadership style fails
No named decider. Shared responsibility becomes nobody's responsibility the moment two peers disagree, and the silos close again. The fix is boring: before the work starts, agree who makes the final call on each class of decision and write it down.
Consensus as the operating system. Most senior decisions are close calls, roughly 51-49. A collaborative group waiting for everyone to feel 80-20 will not decide. Fast and 90% right beats slow and 95% right, by more when five organizations are waiting.
Collaboration as a way to avoid accountability. If a leader can say "we decided together" after a failure, some will use the style for that reason alone. Shared ownership needs one accountable name per outcome.
Importing the style whole from another culture. I coach from a Nordic frame of reference, where flat structures and shared decisions are the default, and I treat it as one input among several, not the template. A US company that copies Nordic consensus without Nordic trust gets the slowness and none of the speed. The honest limits are on the Can you copy Nordic leadership? page.
No psychological safety underneath. Collaboration asks people to disagree with peers they will need next month. If honesty is punished anywhere in the system, they will not. The psychological safety in the workplace guide covers how to build the floor first.
How do you keep decisions moving when nobody has authority over everybody?
The sequence I give executives who run cross-functional or multi-company work.
- Write the shared goal in one sentence and get every party to sign it. Vague purpose is where collaboration goes to die.
- Agree the decision rights per topic before the first disagreement: who decides, who is consulted, who is informed.
- Run the trust loops deliberately for the first month. Explain every decision with a because. Make five small promises and keep all five. Ask each partner what you are not seeing about their reality.
- Put a clock on every open question. Input closes on a date. The decider decides on a date.
- Celebrate the discovery of problems, out loud, by name. The partner who says the plan is failing in week two is worth more than the one who reports success in week ten.
How collaborative leadership compares with the other styles
The hub on the types of leadership styles maps the full set. The closest neighbors:
- Servant leadership puts the leader's own team's needs first and develops people through questions. It operates inside a hierarchy. Collaborative leadership operates between hierarchies. The servant leadership style page covers the honest limits of serving.
- Trust-based leadership is the internal version of the same bet: give people ownership and verify outcomes. Collaborative leadership makes that bet with people who were never yours.
Frequently asked questions about the collaborative leadership style
What is the collaborative leadership style?
The collaborative leadership style is an approach in which leaders from different teams, functions, or organizations share responsibility for decisions and outcomes instead of one leader directing the others. It depends on a shared goal, agreed decision rights, mutual accountability, and trust rather than positional authority. Herminia Ibarra and Morten Hansen described its core skill in 2011 as engaging people outside your formal control.
What are the characteristics of a collaborative leader?
Collaborative leaders explain the reasoning behind decisions, treat problems as separate from the people who raise them, place people according to their strengths, secure genuine buy-in from those who will defend a decision, and agree in advance who holds the final call. They communicate constraints openly, keep small promises consistently, and make it safe for peers to disagree without penalty.
What are the disadvantages of collaborative leadership?
The main disadvantages are slower decisions, unclear accountability when responsibility is shared without a named decider, the risk of consensus replacing judgment on close calls, and dependence on trust that can take months to build. It can also be used to avoid personal accountability after a failure. The style works poorly in emergencies and in cultures where honest disagreement is punished.
Can you give examples of collaborative leadership?
Examples include a cross-functional product launch where product, sales, and operations leaders share ownership of the plan under one agreed decider; a joint venture in which two companies' executives run a shared business; a subsidiary CEO coordinating with a parent company and technology partners; and a change program whose sponsor secures sign-off from the CEO and directors rather than relying on one department's approval.
What is the difference between collaborative and participative leadership?
Participative leadership happens inside one team: the leader invites input from direct reports and then makes the decision. Collaborative leadership happens across teams, functions, or organizations where no single leader has authority over the others, so decision rights are agreed among peers and the outcome is shared. Participative is a leader's choice about input; collaborative is the only workable style when the people involved do not report to each other.
How do you build trust for collaborative leadership?
Trust between peers depends on five consistent signals: explaining the reasons behind decisions, doing what you said you would do, acknowledging the other party's constraints before making requests, rewarding honesty even when the news is bad, and showing visible progress on commitments. Leaders build it by making small promises and keeping all of them, asking what they are not seeing, and thanking disagreement.
Shared ownership, one name
The collaborative leadership style works when responsibility is shared and accountability is not. Agree the goal, agree who decides, run the trust loops, and put a date on everything. Everything else in the literature is atmosphere.
One thing to do before your next cross-functional meeting: write the decider's name at the top of the agenda. If you cannot, that meeting is the problem.
Building the trust loops into your week
The five loops above come from The Trust Protocol, which is offered alongside The 5 Minute Leader. The full version includes a three-minute trust diagnostic scored over your last fourteen days, a first-week plan that works one loop per day, and a 30-second script for the very next interaction with a partner who has gone quiet. It is built for leaders whose weeks are already full, which is why every piece fits in five minutes.
The free leadership style quiz shows your real default when a partner pushes back, the leadership assessment adds your type, and The 5 Minute Leader page shows how the protocols behind the collaborative leadership style fit together.
Andreas Pettersson spent seven years as CEO of a technology company owned by a global manufacturer, one of Canon's youngest CEOs, running teams across three continents. He coaches CEOs and founders at Leaders ADAPT.
