Section 11. Collaborative Leadership

Complex community issues often cross organizational, professional, geographic, and institutional boundaries. No single person or organization may have all the information, authority, relationships, resources, or experience needed to address them.

In those situations, collaborative leadership can help people work across those boundaries. It provides structures for sharing information, defining problems, making decisions, coordinating action, and learning together.

Collaboration does not mean that everyone participates in every decision, that all partners begin with equal power, or that formal authority disappears. Effective collaborative leadership makes those realities visible and creates a process through which relevant people can influence the work while responsibilities and decision rights remain clear.

In this section, we will explore what collaborative leadership is, when it is useful, who may exercise it, and how to build and maintain an effective collaborative process.

What is collaborative leadership?

Collaborative leadership is the practice of helping people with different knowledge, roles, resources, responsibilities, or interests work together toward a shared purpose.

Collaborative leadership focuses heavily on the quality of the process: who participates, what information is available, how power and resources are distributed, how decisions are made, how conflict is handled, and how agreed actions are carried out.

It is especially useful when a problem cannot be solved effectively by one individual or organization acting alone.

Collaborative leadership often includes:

• Joint problem definition
• Sharing relevant knowledge and information
• Meaningful participation by people affected by the issue
• Explicit decision processes
• Coordination across roles or organizations
• Shared or distributed leadership where appropriate
• Accountability for agreed responsibilities
• Evaluation and adaptation

A collaborative process should not be used merely to gain support for a decision that has already been made.

At the same time, collaboration does not require that every aspect of an issue be open to negotiation. Some constraints may already be established by law, regulation, funding, governance, safety requirements, professional standards, contractual obligations, or organizational mission.

Those limits should be explained honestly at the beginning so participants understand what they can meaningfully influence.

Two forms of collaborative leadership

Collaborative leadership may take at least two related forms.

• Leadership of a collaborative effort. A person or small leadership group helps a coalition, partnership, network, or other collaborative effort establish and maintain the process through which members work together. The leader or facilitator may coordinate the process without having authority to direct every participating organization.
• Shared or distributed leadership. Leadership functions move among several people according to expertise, role, responsibility, or the needs of the situation. One person may lead a technical issue, another a community-engagement process, and another implementation.

Shared leadership does not eliminate formal accountability. Organizations still need to know who is legally, financially, professionally, or organizationally responsible for particular decisions.

Collaboration does not automatically mean equal power

Partners may enter a collaboration with very different levels of influence.

One organization may control funding. Another may control access to data. A public agency may have regulatory authority. A community organization may hold trusted relationships that institutions do not. Residents may have essential lived knowledge but little formal authority.

Pretending that all participants are already on equal footing can hide those differences.

Collaborative leadership should instead ask:

• Who controls resources?
• Who controls information?
• Who has formal decision authority?
• Who will experience the consequences?
• Who has historically been excluded from decisions?
• What would meaningful influence look like for different participants?

Where possible, collaborative structures can share resources, information, decision authority, and other forms of power more deliberately.

Why practice collaborative leadership?

Collaborative leadership can provide important benefits when the work is genuinely interdependent.

Those benefits are not automatic. They depend on the quality of the collaboration, its resources, the people involved, and whether participants have meaningful influence.

Potential advantages of collaborative leadership

• Greater understanding and commitment. People who participate meaningfully in defining a problem and developing a response may understand the reasoning more fully and be better prepared to carry out their responsibilities.
• Better coordination during implementation. When several organizations or roles must act together, collaborative planning can identify dependencies, barriers, and responsibilities before implementation begins.
• Stronger relationships and trustworthiness. Transparent communication, follow-through, fair processes, and meaningful sharing of responsibility can strengthen relationships over time.
• Better management of competing interests. Collaboration can create a structured way to discuss competition over funding, authority, recognition, responsibilities, or organizational priorities.
• Access to more kinds of knowledge. Participants may bring professional expertise, community knowledge, lived experience, organizational history, technical information, data, and practical knowledge of implementation.
• Better potential for coordinated solutions. Problems that cross organizational boundaries may require changes by several actors. Collaboration can help align those actions.
• Leadership development. Participants can gain experience facilitating, organizing, analyzing information, leading projects, negotiating, and representing their organizations or communities.
• Greater community influence. Collaborative structures can create meaningful pathways for community knowledge and priorities to affect institutional decisions.
• Longer-term collaborative capacity. Partnerships that work effectively may make future coordination easier by creating relationships, procedures, and shared understanding.

Potential difficulties

Collaborative leadership also creates costs and risks.

• It requires time. Meaningful participation, information sharing, discussion, and coordination take time that should be planned rather than treated as free.
• Participation can create burdens. Community members and organizational partners may be contributing meeting time, preparation, transportation, caregiving costs, lost work time, or professional expertise.
• Power differences can distort participation. People with more money, status, staff, technical vocabulary, or formal authority may dominate even when everyone is technically allowed to speak.
• Accountability can become unclear. Groups may spend substantial time discussing a decision without knowing who ultimately has authority to make it or responsibility to implement it.
• Conflict is inevitable. Partners may disagree about priorities, values, evidence, resources, responsibilities, or acceptable risk.
• Participation can become symbolic. Inviting people into a process without giving their input any realistic chance of influencing decisions can damage trust.
• Representation can be incomplete. The people who attend meetings may not represent everyone affected by the issue.
• Confidentiality may limit what can be shared. Personnel, health, legal, participant, research, or security information may require restrictions.
• Collaboration fatigue can develop. People may participate in multiple coalitions and committees while seeing little movement toward action.

Collaborative leadership should therefore be used deliberately rather than treated as the correct process for every problem.

When is collaborative leadership appropriate?

Collaborative leadership is particularly useful when the issue is complex, responsibilities are distributed, and successful action depends on several people or organizations.

Consider a collaborative approach:

• When the necessary conditions exist. Participants need enough time, information, resources, authority, and support for meaningful collaboration.
• When a problem crosses organizational or professional boundaries. No single organization may control all the resources, relationships, or decisions necessary to address it.
• When several groups hold important knowledge or interests. Different perspectives may be necessary to understand both the problem and the consequences of possible solutions.
• When earlier approaches have not produced adequate results. Collaborative analysis may reveal barriers or options that isolated efforts did not identify.
• When implementation depends on several actors. Collaborative planning can clarify who will do what and how work will be coordinated.
• When meaningful participation and shared power are themselves important goals. A community initiative that seeks to expand people's influence should use a process consistent with that goal.

Collaborative decision-making may be less appropriate when:

• Immediate safety requires rapid action by a clearly responsible person
• Law or policy has already established the required action
• Confidential information prevents broad participation
• A narrow technical decision can be made more responsibly by qualified specialists
• Participants are being asked for input that cannot actually affect the result
• The cost of a large collaborative process would be disproportionate to the decision

Even in these situations, collaboration may still be useful before or after the immediate decision. Emergency planning, for example, may be collaborative even when the actual emergency response requires clear command authority.

Who are collaborative leaders?

Collaborative leaders may be formal leaders, community members, staff members, consultants, facilitators, public officials, organizational representatives, or other participants.

Some collaborations use one coordinator or facilitator. Others use co-chairs, steering groups, rotating facilitators, or shared leadership structures.

Useful characteristics and skills include:

Credibility and trustworthiness

Collaborative leaders do not need to be trusted by every participant before the work begins.

They do need to behave in ways that support trustworthiness:

• Following through on commitments
• Applying the agreed process fairly
• Communicating clearly
• Acknowledging uncertainty
• Protecting appropriate confidentiality
• Disclosing relevant conflicts of interest

Being an outside facilitator does not automatically make someone neutral or unbiased. Relevant interests, relationships, funding sources, or previous involvement should be disclosed.

Respectful engagement across differences

Collaborative leaders should be able to work respectfully with people who differ in role, profession, culture, language, organizational authority, lived experience, or perspective.

This involves cultural humility and willingness to learn rather than assuming that a facilitator can become fully knowledgeable about every group involved.

Facilitation skills

Useful facilitation skills include:

• Managing disagreement constructively
• Creating multiple ways for people to contribute
• Summarizing and reframing ideas accurately
• Understanding group processes and power dynamics
• Clarifying decision rules
• Recognizing when a discussion needs additional evidence or expertise
• Maintaining focus without shutting down legitimate dissent
• Supporting accessible participation

Ability to see the larger system

Collaborative leaders need to understand not only what happens in a meeting but also the relationships, institutions, incentives, authority, history, resources, and external conditions shaping the issue.

Ability to connect people and resources

Collaborative leaders often help identify missing participants, expertise, funding, data, partnerships, or other resources that the group needs.

Commitment to developing other leaders

Collaborative leadership should not make one facilitator indispensable.

Give other participants opportunities to:

• Facilitate meetings
• Lead projects
• Present findings
• Coordinate subgroups
• Represent the collaboration
• Learn relevant technical or organizational skills

Commitment to both process and results

Collaborative leadership requires attention to how decisions are made and whether the collaboration is accomplishing useful work.

A process can be inclusive and respectful yet still fail if no decisions are made or responsibilities are never implemented.

How do you practice collaborative leadership?

Clarify the purpose, mandate, and boundaries

Before inviting people into a collaborative process, clarify:

• What issue the collaboration is addressing
• Why collaboration is needed
• What authority the collaboration has
• Which decisions are open for discussion
• Which requirements are already fixed
• What success would look like
• How long the collaboration is expected to continue

Don't invite people to make a decision that another body has already made.

Identify relevant participants and power relationships

Consider who:

• Is affected by the issue
• Has relevant lived or community knowledge
• Has technical or professional expertise
• Controls resources
• Has decision authority
• Will implement the work
• Has historically been excluded
• May bear unintended consequences

No stakeholder list will remain perfect forever. Revisit participation as the issue changes.

Don't assume that one representative speaks for an entire community, profession, agency, or organization.

Make participation realistic

Participation requires resources.

Consider:

• Scheduling
• Transportation
• Childcare or other caregiving responsibilities
• Language access
• Accessible meeting spaces and technology
• Remote participation
• Compensation for substantial community expertise where appropriate
• Preparation materials
• Technology access

A process is not meaningfully inclusive if only people with flexible schedules, professional salaries, transportation, or institutional support can participate consistently.

Establish governance and decision rules

Clarify who:

• Sets agendas
• Facilitates
• Provides information
• Makes recommendations
• Makes final decisions
• Implements decisions
• Monitors progress

Also establish the decision method.

Possibilities include:

• Consensus
• Consent
• Majority or supermajority vote
• An accountable decision-maker acting after consultation
• Delegation to a subgroup or subject-matter expert

Consensus is one option, not the definition of collaboration.

Establish explicit working agreements

Useful agreements may address:

• Respectful communication
• Meeting preparation
• Attendance
• Confidentiality
• Information sharing
• Conflicts of interest
• Decision-making
• Accessibility
• Disagreement and conflict
• Documentation
• Responsibilities between meetings

Important expectations should generally be explicit rather than relying on unwritten norms that new or less powerful members may not know.

Create psychological safety

Collaborative participants need to be able to raise questions, admit uncertainty, challenge assumptions, report mistakes, and disagree with more powerful participants without unnecessary humiliation or retaliation.

Leaders can support this by:

• Responding constructively to difficult information
• Asking for concerns before closing discussion
• Acknowledging their own uncertainty
• Not treating disagreement as disloyalty
• Making escalation routes clear when a concern involves the facilitator or another powerful member

Psychological safety does not eliminate standards of conduct or accountability.

Create multiple ways for people to contribute

Don't judge participation only by how often someone speaks in a meeting.

Depending on the group, input may come through:

• Discussion
• Written comments
• Surveys
• Small-group work
• Community meetings
• Interviews
• Advisory groups
• Digital collaboration tools

Pay attention to whose information is not reaching the process and why.

Support useful relationships

Relationships matter, particularly when partners have a history of competition or mistrust.

Trust develops through more than social contact. Participants watch whether others:

• Keep commitments
• Share information appropriately
• Respect confidentiality
• Give credit fairly
• Follow agreed procedures
• Share resources as promised
• Respond when problems are raised

Address conflict rather than hiding it

Disagreement may involve:

• Values
• Evidence
• Funding
• Authority
• Organizational interests
• Community priorities
• Workload
• Strategy

First identify the nature of the disagreement.

Some conflicts can be handled through facilitated discussion, negotiation, mediation, or clarification of roles. Others may require a formal decision, complaint process, legal review, investigation, or a decision to end part of the collaboration.

Collaboration does not require every disagreement to disappear.

Bring relevant evidence and knowledge into the process

Collaborative decision-making can draw on:

• Community and lived knowledge
• Research
• Program data
• Professional expertise
• Organizational experience
• Policy and legal information
• Evaluation findings
• Pilot projects

Make clear what is known, what remains uncertain, and where different forms of knowledge point in different directions.

Delegate without losing accountability

Not every issue needs to return to the full group for detailed approval.

The collaboration may delegate work to:

• Staff
• Committees
• Working groups
• Technical experts
• Community advisory groups

Clarify the scope of that authority and what must return to the larger group.

Move from discussion to action

Collaboration should eventually produce decisions, actions, learning, or another agreed result.

When discussion has reached the point where a decision can responsibly be made:

• Restate the decision to be made
• Identify unresolved questions
• Confirm the decision rule
• Record the decision
• Assign responsibilities
• Establish timelines
• Determine how progress will be monitored

Begin with appropriately scoped work

Early projects can help partners learn how they work together and reveal problems in communication, decision-making, or implementation.

Choose work that is meaningful and realistic with the available time and resources rather than manufacturing an easy project merely to claim success.

Provide the resources collaboration requires

Collaborative processes may need:

• Coordination staff
• Facilitation
• Meeting space or technology
• Translation or interpretation
• Accessibility services
• Data or research support
• Community-participant compensation
• Evaluation
• Communications support

An initiative that continually depends on unpaid labor from the same people may not be sustainable.

Protect the integrity of the process

A collaborative process should not be used to create the appearance of participation while decisions are made elsewhere.

Be clear about:

• What remains open for decision
• What has already been decided
• Which participant has which authority
• What information cannot be shared
• What legal, financial, safety, or professional requirements apply

Process integrity also means protecting people from retaliation for participating in good faith and ensuring that major changes to the process are explained.

Consider the interests of the whole without erasing differences

Collaborative leaders often help participants move beyond narrow organizational interests.

At the same time, appeals to "the common good" should not erase:

• Minority interests
• Rights
• Unequal burdens
• Historical inequities
• Legitimate organizational responsibilities

Ask not only what produces the largest overall benefit but also who bears the costs of the proposed action.

Know the leadership context

Every collaboration operates in a particular context.

Important factors include:

The community and environment

• Current circumstances. What is happening now, and why has the issue become important?
• History. What previous efforts, relationships, harms, successes, or broken commitments affect the current work?
• Relationships. How do participating organizations and communities relate to one another?
• Different community perspectives. Which groups view the issue differently, and whose perspectives are least represented?
• Power and resources. Who controls funding, information, institutions, property, regulation, or other resources relevant to the issue?

The nature of the problem

Some problems are relatively well defined. An organization may know what is wrong and need appropriate technical expertise to fix it.

Other problems have a clear goal but require changes in behavior, relationships, policy, organizational practice, or community participation in addition to technical expertise.

Still other problems are genuinely complex. People may disagree about what the underlying problem is, what caused it, what an acceptable outcome would be, and which intervention is most likely to help.

The less certain the definition and solution, the more important it may be to bring together different forms of knowledge and learn through action and evaluation.

Anticipate barriers to collaboration

Common barriers include:

• Lack of experience working collaboratively
• Historical mistrust
• Competition for funding or recognition
• Unequal authority
• Unclear roles
• Inadequate staffing
• Weak community relationships
• Insufficient funding
• Inaccessible meetings or communication
• Conflicting organizational incentives
• Different expectations about what the collaboration can accomplish

Match the response to the actual barrier.

If participants lack experience with collaborative work, provide orientation and facilitation. If power is concentrated, change governance or resource-sharing arrangements rather than simply asking less powerful participants to speak more confidently. If partners compete for funding, discuss the underlying incentives directly.

Maintain momentum realistically

Collaborative work often moves more slowly than participants expect.

Help people see:

• What has been accomplished
• Which decisions remain unresolved
• What barriers are slowing progress
• What the next steps are

Recognition of progress can support motivation, but the collaborative leader should not feel responsible for continually creating enthusiasm.

Sustainable participation depends more on meaningful purpose, fair workload, adequate resources, trustworthy relationships, and visible progress than on one person's ability to remain upbeat.

Be adaptable about methods and firm about core responsibilities

Be willing to:

• Try new approaches
• Change course when evidence or circumstances change
• Stop doing what is not working
• Expand participation when important perspectives are missing
• Revise structures that have become unnecessarily complicated

At the same time, do not compromise legal duties, safety, nondiscrimination, accessibility, confidentiality, ethical requirements, or the integrity of agreed decision processes simply to maintain harmony.

Practice humility and role discipline

Collaborative leaders can contribute their own ideas. They do not have to pretend to have no opinions.

They should be clear about which role they are playing:

• Facilitator
• Organizational representative
• Subject-matter expert
• Decision-maker
• Community member

When acting as a facilitator, do not manipulate the process to produce your preferred result.

When you also have decision authority or organizational responsibilities, state those boundaries openly.

Respect decisions made through legitimate agreed processes, while recognizing that law, safety, fiduciary responsibility, professional standards, ethics, or formal authority may sometimes require you to object, escalate, decline participation, or take another action.

Share leadership

Encourage other people to take responsibility where appropriate.

Leadership may shift according to:

• Expertise
• Community relationships
• Project responsibility
• Implementation role
• Facilitation skills

Shared leadership can strengthen capacity and prevent the collaboration from becoming dependent on one coordinator.

Document agreements and decisions

Collaborative work can become confusing when participants remember decisions differently.

Document appropriate information such as:

• Membership
• Governance
• Decision rules
• Funding commitments
• Responsibilities
• Major decisions
• Action items
• Timelines
• Data-sharing agreements

Determine what records are public, shared only among partners, or confidential.

Protect data and confidential information

Collaborations may share data about participants, employees, patients, students, community members, programs, or organizations.

Before sharing information, clarify:

• What may be shared
• Why it is needed
• Who may access it
• Who owns or controls the data
• Where it will be stored
• How findings may be published or presented
• What happens when the collaboration ends

Evaluate both the work and the collaboration

Evaluate whether the collaboration is accomplishing its goals and whether the process itself is functioning well.

Questions might include:

• Are we achieving the intended outcomes?
• Are responsibilities being carried out?
• Is relevant information being shared?
• Do participants understand how decisions are made?
• Whose perspectives are missing?
• Are some partners carrying much more of the workload or cost?
• Do community participants experience meaningful influence?
• Are commitments being honored?
• Are conflicts being handled effectively?
• Are the resources devoted to collaboration justified by the results?

Use what you learn to revise the collaboration rather than assuming that the process is working simply because meetings continue to occur.

Plan for transition or closure

Collaborations may end because their objective is completed, funding ends, circumstances change, or partners decide that another structure would work better.

Before ending:

• Complete or transfer unfinished responsibilities
• Clarify ownership of records and data
• Communicate with affected partners and communities
• Document lessons learned
• Resolve remaining financial or contractual commitments
• Decide which relationships or activities should continue

In Summary

Collaborative leadership helps people and organizations work together on issues that cross boundaries of authority, expertise, resources, or experience.

It places particular emphasis on meaningful participation, shared information, appropriate sharing of power, clear decision processes, coordination, and joint action.

Collaboration does not mean that everyone participates in every decision, that all partners begin with equal power, or that formal authority disappears. Strong collaborative leadership acknowledges those realities and creates structures through which relevant people can influence the work while responsibilities remain clear.

Collaborative approaches are especially useful for complex and interdependent problems in which no single organization can act effectively alone. They are less useful when participation cannot influence the decision, immediate action is required, or responsibility rests clearly with a particular role.

Effective collaborative leaders help clarify purpose and authority, bring relevant participants into the process, address power differences, make participation accessible, establish decision rules, facilitate disagreement, protect psychological safety, connect discussion to implementation, and develop leadership in others.

Finally, collaboration should be evaluated rather than assumed to be beneficial. Look at both the results and the process: whether goals are being achieved, whether commitments are being honored, whether power and workload are distributed fairly, whether community knowledge is influencing decisions, and whether the collaboration remains worth the time and resources it requires.