Cross-functional projects rarely fail inside a team. Each department does roughly what it agreed to do. The project still slips, and the post-mortem produces the usual finding: a communication problem.
That finding is almost always too vague to act on. Execution between functions fails at a small number of identifiable points, and each one has a different fix. Naming the specific break point is what turns a recurring frustration into something a leader can actually address.
Why the failure is structural, not attitudinal
Inside a function, people share a manager, a set of priorities and a vocabulary. Ambiguity gets resolved in a corridor. Across functions none of that holds. Two teams can each behave reasonably, in line with their own priorities, and still produce a failure neither of them caused.
This is why goodwill interventions disappoint. The teams were not hostile. They were operating from different information, under different pressures, with no shared owner of the space between them. Team culture work has its own value, but it does not fix a handoff that nobody owns.
The Handoff Map: five places execution breaks
Work through these in order when a cross-functional piece of work is slipping. In most cases one of the five is clearly the culprit.
| Break point | What it looks like | The underlying cause | What resolves it |
| 1. The unstated assumption | Each team delivers what it understood; the pieces do not fit. | Both sides assumed a shared definition that was never spoken aloud. | Write the definition down at kick-off and have the other function correct it, rather than approve it. |
| 2. The unowned gap | Work that sits between two remits, which both assume the other holds. | The scope was divided by function rather than by end-to-end outcome. | Name an owner for the space between, not just for each side of it. |
| 3. The silent re-prioritisation | One team quietly deprioritises after a change in its own targets. | Nobody is obliged to tell the other function when local priorities shift. | An explicit rule that a change in priority is announced, not discovered. |
| 4. The escalation delay | A known problem surfaces weeks after it was first visible. | Raising it means naming another function’s shortfall, which nobody wants to do. | Normalise early flagging as a service to the other team, and reward the person who does it. |
| 5. The false agreement | Everybody leaves the meeting nodding; two teams act differently. | Agreement was assumed from the absence of objection. | Close every cross-functional meeting by having each function state what it will now do. |
Break points four and five account for the majority of cases we see. Both are interpersonal rather than procedural, which is precisely why process redesign so often fails to fix them.
Diagnosing which one you have
Ask each function separately what they believed the other had committed to. If the two answers differ, you have break point one or five. If they match but the work still did not happen, you have two or three. If both sides knew about the problem well before it was raised, you have four.
This takes about twenty minutes and is considerably more useful than a retrospective where both functions are in the room and neither wants to go first.
What street smart leaders do differently at the boundary
Managers who execute well across functions share three behaviours, and none of them requires formal authority over the other team.
- They find out what the other function is measured on. A request that seems obstructive usually makes sense once you know what target the other side is protecting.
- They make the first concession visible. Giving something up early establishes that the relationship is not purely extractive, and it is repaid disproportionately later.
- They raise problems as shared rather than assigned. ‘We have a gap between our two pieces’ produces a different response from ‘your team has not delivered’, even when the facts are identical.
The common thread is influence exercised without line authority, which is the defining condition of matrixed work. Influence without authority is the capability underneath all three behaviours, and it is trainable.
The cost of leaving this alone
Organisations tend to absorb handoff failures rather than address them, because each individual instance is small. The accumulation is not. The pattern is recognisable.
- Timelines quietly lengthen as each function builds private buffer against the others.
- Coordination roles multiply, adding cost without adding capability.
- The best people avoid cross-functional work, because it damages their delivery record for reasons outside their control.
That third consequence is the expensive one. When capable people learn to decline the work that spans functions, the organisation loses its capacity to do anything that does not fit inside a single department.
Where to start if several break points apply
Start with break point five, the false agreement, because it is the cheapest to fix and the change is immediate. Closing every cross-functional meeting by having each function state its own next action costs two minutes and removes a whole class of failure.
Then address break point four. That one is cultural rather than procedural and takes longer, because it requires that flagging a problem early is genuinely met with thanks rather than defensiveness. Structured practice in raising difficult issues shortens it considerably.
Where This Fits in RISEUP’s Training Approach
RISEUP’s Street Smart Leadership Training treats cross-functional execution as a judgement problem rather than a process one, which is why the work is done on participants’ live projects. Where the need is broader team capability rather than delivery between functions, collaboration training programmes and team-based formats are the better starting point.
FAQs
Why do cross-functional projects fail so often?
Because they fail at the handoffs rather than inside the teams. Each function usually delivers against its own understanding, and the work falls through the gaps between remits that nobody explicitly owns.
What is a handoff failure?
A breakdown at the point where work passes between functions. The five common forms are unstated assumptions, unowned gaps, silent re-prioritisation, delayed escalation and false agreement in meetings.
How do I fix cross-functional execution without authority over the other team?
Find out what the other function is measured on, concede something visibly early, and frame problems as shared rather than assigned. These work through influence rather than reporting lines, which is the normal condition in matrixed structures.
Is this a process problem or a people problem?
Both, but the two most common break points – delayed escalation and false agreement – are interpersonal. That is why redesigning the process frequently fails to fix a recurring handoff problem.
What is the quickest improvement we can make?
Close every cross-functional meeting by having each function state what it will do next, in its own words. It takes two minutes and removes the false-agreement failure, which is among the most common causes of slippage.
Stop Losing Delivery at the Boundaries Between Teams
If your cross-functional work keeps slipping and the retrospectives keep producing the same vague finding, the break point can be identified precisely. Talk to RISEUP about working the Handoff Map against a live programme in your organisation.
A trailblazer in humanising leadership and building high-resilience teams. As a former United Nations Peacekeeper, he leverages his high-stakes experience to redefine leadership dynamics. With a career distinguished by numerous accolades, Joseph now helps organizations thrive through a human-centric approach, enhancing performance, productivity, and workplace culture.
