Most meaningful work in modern organisations requires people from different teams to collaborate effectively. Product needs engineering. Marketing needs data. Operations needs design. And yet, cross-functional work is where some of the most common management failures occur. Timelines slip, ownership blurs, communication breaks down, and what started as an exciting initiative quietly becomes a source of frustration for everyone involved. The problem is rarely a lack of talent or goodwill. It is a lack of structure, clarity, and shared accountability.
Cross-functional collaboration does not fail because people refuse to work together. It fails because nobody defined what working together actually looks like.
Why cross-functional work is hard
Each team in an organisation has its own priorities, its own language, and its own definition of success. For more on this, see our guide on managing stakeholder expectations. When you bring people together from different functions, these differences create friction. What feels like urgency to one team may feel like a nice-to-have to another. What counts as done for engineering may not meet the bar for design. These misalignments are not personal. They are structural.
There is also the problem of competing loyalties. The meeting notes feature in Manager Toolkit supports this. People on cross-functional projects still report to their functional manager, who has their own objectives and expectations. Without explicit alignment between managers, team members end up caught between competing demands, unsure which commitment takes precedence when time runs short.
- Different incentivesEach team is measured on different outcomes. Engineering cares about technical quality, marketing cares about reach, and sales cares about revenue. Unless the shared project has its own success metrics, each team optimises for their own goals.
- Communication gapsTeams use different tools, different meeting rhythms, and different communication styles. What is obvious context within one team is invisible to another. Information gets lost between handoffs and assumptions go unchecked.
- Unclear ownershipThe most dangerous phrase in cross-functional work is "someone will handle that." When ownership is not explicitly assigned, tasks fall through the cracks. Everyone assumes someone else is responsible.
- Power dynamicsNot all teams have equal influence. The team with the most senior sponsor or the closest link to revenue often dominates decision-making, even when other perspectives are equally valid. This creates resentment and disengagement.
Setting it up for success
The most important phase of any cross-functional initiative is the setup. Time invested here saves exponentially more time downstream. Our article on meeting notes explores this further. Before any work begins, the involved managers and leads need to align on scope, timelines, ownership, and what success looks like. These conversations can feel tedious, but skipping them is the single biggest predictor of failure.
Write things down. Verbal agreements between managers are forgotten or reinterpreted within days. A simple one-page brief that captures the shared goal, each team's responsibilities, key milestones, and the decision-making process gives everyone a reference point when confusion inevitably arises.
Project alignment brief
One page. Shared goal, each team's role, and one accountable owner.
- Define one ownerEvery cross-functional project needs a single person who is accountable for the overall outcome. This is not about hierarchy. It is about having someone whose job it is to spot gaps, chase progress, and make calls when the group cannot agree.
- Agree on scope earlyGet explicit agreement on what is included and what is not. Scope creep is the silent killer of cross-functional work. When the boundaries are clear from the start, it is much easier to push back on additions later.
- Align the managersBefore the team starts work, the involved managers need to agree on how much time their people can dedicate. If one manager expects twenty percent and another expects eighty, the project is set up to fail before it begins.
- Establish communicationDecide upfront where updates will be shared, how often the group will meet, and what the escalation path is when things stall. Do not leave these to evolve organically. They rarely do.
- Set shared milestonesCreate checkpoints that all teams commit to together. Individual team deadlines are not enough. Shared milestones create mutual accountability and make it obvious when one part of the work is falling behind.
Running the work
Once the work is underway, the manager's role shifts to facilitating coordination and removing obstacles. This does not mean micromanaging every interaction. It means ensuring that communication flows, blockers are surfaced quickly, and the team stays aligned on what matters most this week.
Pay particular attention to the handoff points between teams. This is where most cross-functional work breaks down. When one team finishes their piece and passes it to the next, there are often unspoken assumptions about quality, format, or completeness that only become apparent when the receiving team hits a problem.
Cross-team communication cadence
Frequent, brief check-ins catch misalignment before it becomes costly.
- Short feedback loopsMeet frequently and briefly rather than infrequently and at length. A fifteen-minute weekly sync across teams catches misalignment early. Waiting for a monthly review means discovering problems too late to fix cheaply.
- Track actions centrallyUse a single, shared actions list that everyone can see. When tasks are scattered across different team boards, accountability becomes invisible. A central view ensures nothing slips between the gaps.
- Surface tension earlyDisagreements between teams are normal and healthy. What is unhealthy is letting them fester. Create a safe space for raising concerns and address them directly rather than hoping they resolve themselves.
- Celebrate togetherRecognise milestones as a combined group, not just within individual teams. Shared celebrations build a sense of collective identity and reinforce that this is one project with one goal, not several teams doing separate work.
Closing the loop
One of the most overlooked aspects of cross-functional work is what happens after the project ends. Teams disband, people return to their regular work, and the lessons learned evaporate. This is a wasted opportunity. Every cross-functional project teaches you something about how your organisation collaborates, and capturing those insights makes the next initiative smoother.
Run a brief retrospective with all the involved teams. Focus on what worked, what did not, and what you would change next time. Document the outcomes and share them broadly. This closes the loop for the people who contributed and creates institutional knowledge that benefits everyone.
- Run a joint retroBring all teams together for an honest debrief. Ask what surprised them, what frustrated them, and what they would repeat. Cross-functional retros surface insights that single-team retrospectives miss.
- Document decisionsRecord the key decisions that were made and why. When a similar project comes along in six months, this context is invaluable. Without it, the next team will repeat the same debates from scratch.
- Share outcomes widelyCommunicate the results to the broader organisation. People who contributed deserve to see the impact of their work. People who were not involved benefit from understanding what the collaboration produced.
- Thank people properlySend specific, personal recognition to individuals who went above and beyond. Copy their managers. Cross-functional contributions are often invisible in performance reviews, and your acknowledgement ensures they are not overlooked.
Frequently asked questions
Keep cross-functional work on track
Track shared actions across teams so nothing falls through the cracks between handoffs.