How to Improve Cross-Functional Collaboration in Nonprofit Projects
Most nonprofit teams want the same thing: to advance the mission.
The challenge is that different departments often see that mission through very different lenses.
A community engagement team may focus on trust, relationships, and authentic participation. A fundraising team may focus on donor expectations, campaign deadlines, and compelling stories. An operations team may want a faster, simpler process, while the IT team is thinking about security, system limitations, and long-term support.
None of these perspectives is necessarily wrong.
The friction begins when teams assume that their own priorities are obvious, while the concerns of another department feel like unnecessary resistance.
Cross-functional collaboration does not improve simply because people are placed in the same meeting. It requires shared goals, clear roles, realistic expectations, and a process for making decisions when priorities compete.
Why Cross-Functional Collaboration Is Difficult
Departments are usually designed around different responsibilities.
Fundraising is accountable for revenue. Programs are accountable for service delivery. Finance is accountable for stewardship and compliance. Communications is accountable for messaging and reputation. IT is accountable for security, reliability, and system performance. Operations is accountable for keeping the organization running efficiently.
Those responsibilities shape how each team evaluates a request.
For example, a fundraising team may ask a community engagement team to identify a participant who can speak at an upcoming donor event.
The request may seem simple to fundraising. The team needs a strong story, the event date is approaching, and the speaker could help donors understand the organization’s impact.
The community engagement team may see additional concerns:
Has the participant had enough time to consider the request?
Could the experience feel exploitative?
Is the person being asked to share sensitive information?
Will transportation, childcare, accessibility, or compensation be provided?
Does the story accurately represent the community?
What happens to the relationship after the event?
The disagreement is not necessarily about whether storytelling matters. It may be about what responsible participation requires.
The same dynamic can happen between IT and operations.
Operations may want a new form, workflow, automation, or software tool because the current process is slow and frustrating.
IT may push back because:
The proposed tool does not meet security standards.
It duplicates a system the organization already owns.
Staff will need technical support after launch.
The request affects data integrations.
The process has not been fully defined.
The long-term cost is higher than it first appears.
Operations may hear, “IT does not want to help.”
IT may hear, “Operations wants to implement something without considering the consequences.”
Both teams may be responding to legitimate organizational risks.
Start With the Shared Outcome
Cross-functional conversations often begin with a proposed solution.
“We need a new system.”
“We need this participant at the event.”
“We need a campaign landing page.”
“We need finance to approve this purchase.”
“We need communications to promote this program.”
Starting with the solution can make the conversation feel like a negotiation over someone else’s request.
A better starting point is the shared outcome.
Instead of saying:
We need IT to approve this new tool.
The operations team might say:
Staff are spending several hours each week entering the same information into multiple systems. We need to reduce duplicate work while protecting organizational data and ensuring the process can be supported over time.
That framing creates room for both teams to contribute.
Operations brings knowledge of the workflow and employee experience. IT brings knowledge of systems, security, integration, and support. The goal is not to win approval for a preferred tool. The goal is to solve the underlying problem.
Similarly, fundraising and community engagement can begin with a shared outcome:
We want donors to understand the impact of the work while ensuring that community members are represented respectfully and have meaningful control over their participation.
A shared outcome does not eliminate disagreement. It gives teams a common standard against which to evaluate their options.
Make Departmental Priorities Visible
Many conflicts continue because teams do not fully understand what the other department is accountable for.
A project leader can make those priorities visible early.
For a joint initiative, ask each department to identify:
What outcome it is responsible for
What risks it must manage
What deadlines or external commitments affect its work
What information it needs from other teams
What constraints cannot be ignored
What flexibility it has
This exercise can reveal why a request that seems straightforward to one team feels complicated to another.
For example, fundraising may be working toward a fixed event date tied to a major sponsorship. Community engagement may need more lead time to build trust and obtain informed consent.
The solution may not be to declare one priority more important. It may be to create a standing process for identifying potential speakers earlier, developing participation guidelines, and establishing appropriate support.
Collaboration improves when people can see the full set of conditions surrounding a decision.
Define Roles Before the Work Becomes Urgent
Cross-functional projects often become tense when everyone is involved, but no one knows who has authority.
A communications team may believe it owns the final message. A program leader may believe subject-matter accuracy should take priority. An executive sponsor may expect to approve the final version. A funder may have its own requirements.
Without defined roles, every review can reopen the same questions.
Teams should clarify:
Who is responsible for completing the work
Who has final decision authority
Who must be consulted
Who needs to be informed
Which decisions require executive escalation
Which decisions can be made by the working team
This does not have to become a complicated governance exercise. Even a simple role chart can prevent delays and repeated conflict.
It is particularly important to distinguish between providing input and making the final decision.
A person may have valuable expertise without having authority over the entire outcome. Likewise, a decision-maker should understand when technical, legal, financial, or community expertise must shape the decision.
Translate Concerns Into Requirements
Teams often express concerns in ways that sound like rejection.
IT may say, “We cannot support that.”
Finance may say, “There is no budget.”
Community engagement may say, “This approach will not work.”
Operations may say, “The current process is unacceptable.”
These statements can stop the conversation.
A project manager or facilitator can help translate concerns into requirements.
For example:
“IT cannot support that tool” may mean the solution must use single sign-on, meet specific security standards, integrate with existing systems, and have a defined support owner.
“Community engagement is not comfortable with the request” may mean participants need more notice, a clear consent process, compensation, transportation support, and the option to review how their story will be used.
“Finance cannot approve the purchase” may mean the funding source is restricted, the request falls outside the budget cycle, or leadership must approve the tradeoff.
Once concerns are converted into requirements, the group can evaluate alternatives.
The question changes from “Why are they blocking us?” to “How can we meet these conditions?”
Address Conflicting Timelines Explicitly
Departments often work on different clocks.
Fundraising may have a donor deadline. Finance may be closing the month. Programs may be entering peak service season. Communications may already have a full editorial calendar. IT may be managing several active implementations.
Cross-functional frustration grows when one department’s emergency becomes another department’s unplanned work.
Project teams should identify timing constraints before setting deadlines.
Useful questions include:
Is the deadline fixed or preferred?
What external commitment is driving it?
What work must happen before another team can begin?
Which periods are especially busy for each department?
What would need to be deprioritized to meet the proposed date?
Can the work be delivered in phases?
What is the minimum viable outcome?
This creates a more honest conversation about capacity.
A deadline is not realistic simply because it appears on a project plan. It is realistic when the people responsible for the work understand it, have the required inputs, and have enough capacity to complete it.
Create One Place for Decisions and Commitments
Cross-functional projects become difficult when information is scattered across emails, meetings, chat messages, and individual notes.
One department may believe a decision was made. Another may believe the issue is still open. People may remember different versions of the same commitment.
A shared project space should clearly show:
The current objective
Key decisions
Assigned responsibilities
Deadlines
Open questions
Risks and dependencies
Changes to scope
Meeting notes and next steps
The tool matters less than consistent use.
A simple, reliable source of truth reduces confusion and makes accountability less personal. Instead of asking, “Why did your team not do this?” the group can return to the documented assignment, decision, or dependency.
Do Not Use Meetings as a Substitute for Ownership
Cross-functional projects often produce too many meetings because no one feels confident that work will move forward without them.
However, adding more meetings does not fix unclear ownership.
A useful collaboration rhythm might include:
Short working sessions for complex issues
Written status updates for routine progress
Decision meetings only when authority is needed
Individual follow-ups for specific assignments
Executive escalation only for unresolved tradeoffs
Every meeting should answer at least one of these questions:
What decision must be made?
What problem must be solved?
What work must be coordinated?
What information must be gathered?
When the purpose is unclear, the meeting is likely to create more discussion than progress.
Build Relationships Before Conflict Happens
Teams collaborate more effectively when their first interaction is not an urgent request.
Departments that frequently depend on one another should develop regular ways to understand each other’s work.
For example, fundraising and program teams might meet periodically to discuss:
Upcoming campaigns and grant opportunities
Program milestones
Appropriate stories and data
Community-consent practices
Reporting needs
Seasonal workload
IT and operations might review:
Upcoming process changes
Technology pain points
Existing system capabilities
Security requirements
Potential automations
Support and training needs
These conversations allow teams to identify opportunities and risks before a deadline forces a rushed decision.
Trust is easier to build during planning than during escalation.
Name the Tradeoffs
Some cross-functional disagreements cannot be solved without a tradeoff.
A team may have to choose between speed and customization. A more engaging donor story may require additional time and support. A highly secure process may be less convenient. A lower-cost solution may require more manual work.
Collaboration does not mean pretending that every priority can be fully satisfied.
It means making tradeoffs deliberately.
A useful decision statement might be:
We are choosing the existing platform rather than purchasing a new tool because it meets the immediate need, reduces security risk, and can be implemented this quarter. The process will require more manual reporting, which we will reassess after six months.
Or:
We are moving the participant story to a later campaign so the community engagement team has enough time to support informed and voluntary participation.
Documenting the tradeoff helps teams understand why the decision was made and what limitations remain.
Escalate Decisions, Not Frustration
Executive leaders should not have to resolve every disagreement.
However, escalation is appropriate when the working team cannot resolve a conflict involving organizational priorities, risk, funding, or capacity.
The escalation should clearly state:
The decision needed
The available options
The advantages and risks of each option
The recommendation
The consequences of delaying the decision
This is more productive than escalating a complaint about another department.
Instead of saying:
IT keeps blocking the project.
The team might say:
The current solution can launch in September but does not meet the preferred integration standard. A compliant alternative would launch in January and cost an additional amount. Leadership needs to decide whether speed or long-term integration is the higher priority.
That gives leaders a real decision to make.
Measure Collaboration by Results, Not Harmony
Successful collaboration does not always feel comfortable.
Teams may disagree strongly and still work well together. In fact, respectful disagreement can improve a project by revealing risks, assumptions, and perspectives that one department would otherwise miss.
The goal is not complete harmony.
The goal is for teams to:
Surface concerns early
Understand one another’s responsibilities
Make decisions efficiently
Follow through on commitments
Resolve conflicts without damaging relationships
Produce a stronger organizational outcome
A project with no disagreement may simply be a project where people do not feel safe or motivated enough to raise concerns.
Project Management Creates the Structure for Collaboration
Cross-functional collaboration depends on relationships, but relationships alone are not enough.
Teams also need:
A shared objective
Defined roles
Agreed-upon decision authority
Realistic timelines
Documented requirements
Transparent tradeoffs
Visible assignments
A clear escalation process
Project management provides that structure.
It helps departments move beyond competing requests and toward a shared understanding of the problem, the work, and the decisions required.
At Okavane, we help nonprofit teams lead complex, cross-functional initiatives involving programs, fundraising, community engagement, operations, technology, communications, finance, and executive leadership.
Our role is not to eliminate every disagreement. It is to create the clarity, coordination, and accountability that allow different perspectives to strengthen the work rather than stall it.
When teams share the mission but struggle to work across departmental lines, stronger project management can help turn friction into informed decisions and coordinated action. Feel free to contact us to discuss how we can support your team.